Approval Rules
REMOTE · APPROVE.CLOUDFORBOTS.COM
Auto-approve small agent actions under your rules; approval cards for the rest.
Available components
Last scanned (36 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 468 tokens (~78/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
- Tool “usage_and_upgrade” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://approve.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=approve.cloudforbots.com | CN=YR1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | RSA 2048 | SHA256-RSA | 57c0dbd653fc209a721b17e4ba08d4775e8 |
| SANs: approve.cloudforbots.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of approve.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://approve.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://approve.cloudforbots.com/mcp | HTTPS enforced | 308 | https://approve.cloudforbots.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_action ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | object | yes | The action your agent wants to take. |
No output schema declared.
No examples provided.
get_decision ~50
Check whether the user approved or rejected an approval card (by card_id and card_token). Only act when status is approved.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | – |
| card_token | string | yes | – |
No output schema declared.
No examples provided.
get_rules ~23
Show the rules in effect for your key (or the default starter rules).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_rules ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| rules | array | yes | – |
No output schema declared.
No examples provided.
usage_and_upgrade ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~52
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Approval Rules MCP server?
Approval Rules is a hosted endpoint at https://approve.cloudforbots.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · approve.cloudforbots.com
claude mcp add --transport http com-botrecipe-approve 'https://approve.cloudforbots.com/mcp'
What is the Approval Rules MCP server?
Approval Rules is an MCP server listed in the public MCP registry as com.botrecipe/approve. Auto-approve small agent actions under your rules; approval cards for the rest. This page covers its hosted endpoint (https://approve.cloudforbots.com/mcp).
Is the Approval Rules MCP server safe to use?
Approval Rules scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Approval Rules MCP server expose?
Approval Rules exposes 6 tools: check_action, get_decision, set_rules, get_rules, weekly_report, usage_and_upgrade. Their descriptions and schemas cost roughly 367 tokens of context every time the server is loaded.
Does the Approval Rules MCP server require authentication?
No. We connected to Approval Rules without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Approval Rules MCP server still maintained?
Approval Rules is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.