mcpbeat Sign in

Approval Rules MCP Server

not responding

Approval Rules is listed as active in the registry but did not answer our last check. It exposes 6 tools.

Auto-approve small agent actions under your rules; approval cards for the rest.

Uptime history 22 hours of history · worst hour 50%
22 hours agonow
97.5%
Uptime 24h
78 of 80 checks
6
Tools
read from the server
261 ms
Response time
average over 24h
open, no key
Access
streamable-http

Approval Rules does not always answer

Over the last week it answered 97.5% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add approve --transport http https://approve.cloudforbots.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "approve": {
      "url": "https://approve.cloudforbots.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.approve]
url = "https://approve.cloudforbots.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "approve": {
      "url": "https://approve.cloudforbots.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "approve": {
      "url": "https://approve.cloudforbots.com/mcp"
    }
  }
}

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rules
get_rules
Show the rules in effect for your key (or the default starter rules).
set_rules
Save the user's rules (needs an API key so they stay yours). Each rule: {name, when:{type:[...], max_usd, min_usd, reversible, target_ends_with:[...]}, verdict:"auto"|"ask"|"deny"}. First matching rule wins; anything unmatched needs approval. Call once without confirm to preview, then with confirm=true.
action
check_action
Before a consequential action, ask whether the user's rules auto-approve it. Returns auto_approve, needs_approval (with a plain-English approval card and a link the user can tap) or deny. Free plan is watch-only: it reports what it WOULD decide and logs it for the weekly report, but nothing counts as approved, so ask your user as you normally would.
decision
get_decision
Check whether the user approved or rejected an approval card (by card_id and card_token). Only act when status is approved.
usage
usage_and_upgrade
Show today's usage for your key or IP and the $49/month All Access upgrade link (cloudforbots.com/offer). Free tier: 200 calls/day. Not metered.
weekly
weekly_report
Draft a plain-English report of the last 7 days: actions checked, how many your rules would auto-approve, how many needed you, top kinds of asks, and rule suggestions. Read-only; sends nothing.

Endpoints

URLTransportStateLatencyChecked
https://approve.cloudforbots.com/mcp streamable-http answering 28 ms 2 min ago

Alternatives to Approval Rules

same job, measured the same way
withHuman
by withhuman

Set up human approval for your AI agents' tool calls.

answering
veto
by aiveto

Turn OpenAPI services into tools an agent can call under your rules.

local only
Ontonym
by ontonym

Give your agents your team's real data — read the shared graph, propose actions your team approves.

22 tools answering
X-EGO
by x-ego

Human approval for irreversible AI agent actions, bound to the exact tool call by a passkey tap

4 tools answering
iotPush
by iotpush

Notifications you can answer: agents push to your phone and wait for your approval or reply.

answering
Lotor
by githubscum

A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.

37 installs/wk local only
G
Glyt
by glyt

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

6 tools answering
feedback-memory
by ssap-pa

Remembers why you approved, edited or rejected your agent's drafts; recalls the closest corrections

local only

Approval Rules — questions

Answers built from our own checks of this server.

What can Approval Rules do?
It exposes 6 tools, read directly from the server on our last check. Among them: check_action, get_decision, get_rules, set_rules, usage_and_upgrade, weekly_report. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Approval Rules working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 78 of 80 checks got a reply (97.5%), average response time 261 ms. The bar chart above shows every period we have measured.
The registry lists Approval Rules as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Approval Rules?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Approval Rules need an API key?
No. Approval Rules completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Approval Rules?
It answers our handshake in 261 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.