com.oroboros-design.angel/agent-guard
Angel Agent Guard: pre-purchase check + prompt-injection scan
Is the Angel Agent Guard MCP server down? It gave no valid answer in the probe of 2026-11-15: crashed on start. One failed probe is not an outage.
Check a shop, checkout or payment link, paid API or token before paying; prompt-injection scan.
crashed on start no valid answer since 2026-11-15 · probed 2026-11-15
MCP error -32000: Connection closed privateKey needs the optional dependency viem: npm i viem
- Run it
- npx -y angel-agent-guard@0.2.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/daoudandiaye98-alt/angel-agent-guard
- Website
- https://angel.oroboros-design.com/docs/prompt-injection-defense/
- Registry
- active, updated 2026-11-14 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- com.oneshotpacks/oneshot-mcp · crashed on start
- Open & Async com.open-and-async/mcp · alive
- Opzyai Security Check com.opzyai/mcp · alive
- orisha-data com.orisha-data/orisha-data-mcp · alive
- com.pagerankcafe/mcp-server · alive
- com.pandanpc/mcp-server · crashed on start
- Pariflow Agent com.pariflow/agent · needs network
- Rebuild Dossier com.parkerfawcett/rebuild-dossier · alive
Servers that mention guard.
- ai.getvda/traced-claude-format-guard · newer protocol
- Overwing ai.overwing/mcp · alive
- ai.responsibleailabs/rail-score · no DNS
- ai.sellermate/amazon-ads · needs auth
- ThinkNEO Control Plane ai.thinkneo/control-plane · no DNS
- Panel Review ai.truverif/panel-review · needs auth
- STEADYWRK Agentic Readiness Probe, Store Guard and Dispatch app.steadywrk/mcp-dispatch · alive
- app.zenable/zenable · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The package did not start as an MCP server at its probe on 2026-11-15. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.