io.hibira/mcp-approval-gate
Approval gate for databases
Is the Approval gate for databases MCP server down? It gave no valid answer in the probe of 2026-11-14: not found. One failed probe is not an outage.
Wraps a database MCP server: reads pass, writes wait for a supervisor to approve them.
not found no valid answer since 2026-11-14 · probed 2026-11-15 · unchanged since 2026-11-14
command not found: node
- Run it
- npx -y @hibira-io/mcp-approval-gate@0.4.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/hibira-io/mcp-approval-gate
- Website
- https://github.com/hibira-io/mcp-approval-gate
- Registry
- active, updated 2026-11-13 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- EasyEDA MCP io.github.zzvllvzz/easyeda-mcp · alive
- Global Chat — x402 MCP Agent Discovery (LangGraph, CrewAI, Eliza, A2A) io.global-chat/mcp-server · alive
- io.gmapsscraper/mcp · alive
- GVNR by Instruxi io.gvnr/enforcer-governor · alive
- Identity Forge io.identityforge/mcp · alive
- io.intencion/mcp · not found
- IronWallet io.ironwallet/mcp-server · alive
- io.jikida/mcp · alive
Servers that mention approval.
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- AgenticBooks ai.agenticbooks/books · needs auth
- ai.argushq/enforcement-database · no DNS
- Authoryze ai.authoryze/authoryze · needs auth
- Elicitly Pro ai.elicitly/pro · needs auth
- Entervista ai.entervista/entervista · alive
- Nexez Agentic Commerce ai.nexez/commerce · alive
- ai.penholder/penholder · not MCP
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-14. 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 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.