io.github.infraveilhq/agent-guard
Infraveil Agent Guard
Is the Infraveil Agent Guard MCP server down? Yes. It has given no valid answer since 2026-10-16: not found.
Gate an AI agent's destructive actions behind human approval, with a tamper-evident log.
not found down since 2026-10-16 · probed 2026-11-15 · unchanged since 2026-10-30
error: No solution found when resolving dependencies cause: Because infraveil-guard was not found in the package registry and you require infraveil-guard==0.1
- Run it
- uvx infraveil-guard@0.1.1 (stdio, probed in a container with the network off)
- Host
- pypi.org
- Repository
- https://github.com/infraveilhq/infraveil-guard
- Website
- https://infraveil.com
- Registry
- active, updated 2026-06-22 · registry entry
Compare this server with others.
More servers
Other registry entries on pypi.org, the ones next to this name; all of them.
- Industrial-AIOps io.github.industrial-aiops/iaiops · crashed on start
- Industrial-AIOps Energy io.github.industrial-aiops/iaiops-energy · alive
- VulnFeed io.github.infai-tech/vulnfeed · not found
- io.github.infobloxopen/dns-aid · crashed on start
- Infraveil Control Plane io.github.infraveilhq/control-plane · not found
- DefectDojo io.github.inspicere/mcp-defectdojo · crashed on start
- Knowledge Fabric io.github.invarcore/knowledge-fabric · crashed on start
- io.github.invigil/invigil · needs args
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
- No valid answer since 2026-10-16, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.