raccha.ai
REMOTE · RACCHA.AI · SCANNED SEP 20
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
Available components
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 Security51
- 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 59 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7509 tokens (~127/item across 59 items; 59 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management62
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 41 breaking changes, 0 auth/transport breaks, 5 additions. See how to fix → Fail
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 7 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_role" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 60 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the raccha.ai MCP server?
raccha.ai is a hosted endpoint at https://raccha.ai/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 · raccha.ai
claude mcp add --transport http ai-raccha-raccha 'https://raccha.ai/mcp'
{
"mcpServers": {
"ai-raccha-raccha": {
"url": "https://raccha.ai/mcp"
}
}
} {
"servers": {
"ai-raccha-raccha": {
"type": "http",
"url": "https://raccha.ai/mcp"
}
}
} [mcp_servers.ai-raccha-raccha] url = "https://raccha.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-raccha-raccha": {
"type": "remote",
"url": "https://raccha.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-raccha-raccha --url 'https://raccha.ai/mcp' --transport streamable-http
mcp_servers:
ai-raccha-raccha:
url: "https://raccha.ai/mcp" {
"McpServers": {
"ai-raccha-raccha": {
"Transport": "http",
"Url": "https://raccha.ai/mcp"
}
}
} assistant mcp add ai-raccha-raccha -t streamable-http -u 'https://raccha.ai/mcp'
{
"mcpServers": {
"ai-raccha-raccha": {
"type": "http",
"url": "https://raccha.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 61 to 64.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 54 to 57.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 51.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 41.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 31 to 34.
- 3 Sept 26 0
- Server version: 3.1.2 → 3.2.0 functional
- 2 Sept 26 −4
- Stability: 0.57 → fail ▼ security
- A breaking change shipped without a version bump: still 3.1.2 ▼ security
- Tool “discussion_create” rewrote its description, which is the text the model reads security
- Tool “discussion_get” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “create_access_key” changed the type of “owner_key”: string → string|null ▼ functional
- “create_role” changed the type of “owner_key”: string → string|null ▼ functional
- “delete_role” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_claim_role” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_create” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_get” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_join” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_list” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_list_open” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_post” changed the type of “owner_key”: string → string|null ▼ functional
- “discussion_resolve” changed the type of “owner_key”: string → string|null ▼ functional
- “invite_member” changed the type of “owner_key”: string → string|null ▼ functional
- “isdomainreachable” changed the type of “owner_key”: string → string|null ▼ functional
- “isemailreachable” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_delete” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_delete_prefix” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_get” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_incr” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_list” changed the type of “owner_key”: string → string|null ▼ functional
- “kv_put” changed the type of “owner_key”: string → string|null ▼ functional
- “list_access_keys” changed the type of “owner_key”: string → string|null ▼ functional
- “list_profiles” changed the type of “owner_key”: string → string|null ▼ functional
- “list_roles” changed the type of “owner_key”: string → string|null ▼ functional
- “queue_ack” changed the type of “owner_key”: string → string|null ▼ functional
- “queue_nack” changed the type of “owner_key”: string → string|null ▼ functional
- “queue_pop” changed the type of “owner_key”: string → string|null ▼ functional
- “queue_pop_lease” changed the type of “owner_key”: string → string|null ▼ functional
- “queue_push” changed the type of “owner_key”: string → string|null ▼ functional
- “revoke_access_key” changed the type of “owner_key”: string → string|null ▼ functional
- “send_email_reply” changed the type of “owner_key”: string → string|null ▼ functional
- “stats” changed the type of “owner_key”: string → string|null ▼ functional
- “switch_org” changed the type of “owner_key”: string → string|null ▼ functional
- “telegram_pair_code” changed the type of “owner_key”: string → string|null ▼ functional
- “telegram_send” changed the type of “owner_key”: string → string|null ▼ functional
- “topic_read” changed the type of “owner_key”: string → string|null ▼ functional
- “update_access_key” changed the type of “owner_key”: string → string|null ▼ functional
- “update_role” changed the type of “owner_key”: string → string|null ▼ functional
- “whoami” changed the type of “owner_key”: string → string|null ▼ functional
- Tool “delete_role” dropped its output schema ▼ functional
- Tool “invite_member” dropped its output schema ▼ functional
- Tool “update_access_key” dropped its output schema ▼ functional
- Tool “update_role” dropped its output schema ▼ functional
- Tool “whoami” dropped its output schema ▼ functional
- Tool coverage: 47% → 61% ▲ functional
- Schema quality: good → excellent functional
- New tool “create_org” functional
- New tool “list_by_tag” functional
- New tool “list_subscribers” functional
- New tool “queue_fetch” functional
- New tool “queue_list_items” functional
- New tool “queue_list_names” functional
- New tool “subscribe_tag” functional
- New tool “unsubscribe_tag” functional
- “discussion_create” added an optional parameter “tags” cosmetic
- “discussion_get” added an optional parameter “tag” cosmetic
- “invite_member” reworded the description of “owner_key” cosmetic
- “create_access_key” reworded the description of “owner_key” cosmetic
- “create_role” reworded the description of “owner_key” cosmetic
- “delete_role” reworded the description of “owner_key” cosmetic
- “discussion_claim_role” reworded the description of “owner_key” cosmetic
- “discussion_create” reworded the description of “owner_key” cosmetic
- “kv_put” reworded the description of “owner_key” cosmetic
- “discussion_get” reworded the description of “owner_key” cosmetic
- “discussion_join” reworded the description of “owner_key” cosmetic
- “discussion_list” reworded the description of “owner_key” cosmetic
- “discussion_list_open” reworded the description of “owner_key” cosmetic
- “discussion_post” reworded the description of “owner_key” cosmetic
- “discussion_resolve” reworded the description of “owner_key” cosmetic
- “isdomainreachable” reworded the description of “owner_key” cosmetic
- “isemailreachable” reworded the description of “owner_key” cosmetic
- “kv_delete” reworded the description of “owner_key” cosmetic
- “kv_delete_prefix” reworded the description of “owner_key” cosmetic
- “kv_get” reworded the description of “owner_key” cosmetic
- “kv_incr” reworded the description of “owner_key” cosmetic
- “kv_list” reworded the description of “owner_key” cosmetic
- “list_access_keys” reworded the description of “owner_key” cosmetic
- “list_profiles” reworded the description of “owner_key” cosmetic
- “list_roles” reworded the description of “owner_key” cosmetic
- “queue_ack” reworded the description of “owner_key” cosmetic
- “queue_nack” reworded the description of “owner_key” cosmetic
- “queue_pop” reworded the description of “owner_key” cosmetic
- “queue_pop_lease” reworded the description of “owner_key” cosmetic
- “queue_push” reworded the description of “owner_key” cosmetic
- “revoke_access_key” reworded the description of “owner_key” cosmetic
- “send_email_reply” reworded the description of “owner_key” cosmetic
- “stats” reworded the description of “owner_key” cosmetic
- “switch_org” reworded the description of “owner_key” cosmetic
- “telegram_pair_code” reworded the description of “owner_key” cosmetic
- “telegram_send” reworded the description of “owner_key” cosmetic
- “topic_read” reworded the description of “owner_key” cosmetic
- “update_access_key” reworded the description of “owner_key” cosmetic
- “update_role” reworded the description of “owner_key” cosmetic
- “whoami” reworded the description of “owner_key” cosmetic
- “create_access_key” made “owner_key” optional cosmetic
- “create_role” made “owner_key” optional cosmetic
- “delete_role” made “owner_key” optional cosmetic
- “discussion_claim_role” made “owner_key” optional cosmetic
- “discussion_create” made “owner_key” optional cosmetic
- “discussion_get” made “owner_key” optional cosmetic
- “discussion_join” made “owner_key” optional cosmetic
- “discussion_list” made “owner_key” optional cosmetic
- “discussion_list_open” made “owner_key” optional cosmetic
- “discussion_post” made “owner_key” optional cosmetic
- “discussion_resolve” made “owner_key” optional cosmetic
- “invite_member” made “owner_key” optional cosmetic
- “isdomainreachable” made “owner_key” optional cosmetic
- “isemailreachable” made “owner_key” optional cosmetic
- “kv_delete” made “owner_key” optional cosmetic
- “kv_delete_prefix” made “owner_key” optional cosmetic
- “kv_get” made “owner_key” optional cosmetic
- “kv_incr” made “owner_key” optional cosmetic
- “kv_list” made “owner_key” optional cosmetic
- “kv_put” made “owner_key” optional cosmetic
- “list_access_keys” made “owner_key” optional cosmetic
- “list_profiles” made “owner_key” optional cosmetic
- “list_roles” made “owner_key” optional cosmetic
- “queue_ack” made “owner_key” optional cosmetic
- “queue_nack” made “owner_key” optional cosmetic
- “queue_pop” made “owner_key” optional cosmetic
- “queue_pop_lease” made “owner_key” optional cosmetic
- “queue_push” made “owner_key” optional cosmetic
- “revoke_access_key” made “owner_key” optional cosmetic
- “send_email_reply” made “owner_key” optional cosmetic
- “stats” made “owner_key” optional cosmetic
- “switch_org” made “owner_key” optional cosmetic
- “telegram_pair_code” made “owner_key” optional cosmetic
- “telegram_send” made “owner_key” optional cosmetic
- “topic_read” made “owner_key” optional cosmetic
- “update_access_key” made “owner_key” optional cosmetic
- “update_role” made “owner_key” optional cosmetic
- “whoami” made “owner_key” optional cosmetic
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://raccha.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=raccha.ai | CN=YE2,O=Let's Encrypt,C=US | 1 Sept 2026 | 30 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 637a1448db515762c200e3ebd1e53f255ae |
| SANs: *.raccha.ai, raccha.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of raccha.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| raccha.ai. | 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; connect-src 'self' https://raccha.ai https://*.raccha.ai; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://raccha.ai/mcp | Verified | 200 | |
| http (plaintext) | http://raccha.ai/mcp | Inconclusive | 406 |
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 →
telegram_pair_code ~109
Mint a short-lived one-time pairing code. DM it (or /start <code>) to the raccha.ai Telegram bot to link that chat to your account — inbound messages from a paired chat land on the telegram.inbound queue in your namespace.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_key | string|null | – | Owner key for the org this pairing code will link a Telegram chat to. Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
No output schema declared.
No examples provided.
telegram_send ~162
Send a text message to a Telegram chat_id that has already been paired to your account (via telegram_pair_code). Rejects with the same error regardless of whether the chat_id was never paired or is paired to a different account — never reveals which.
| Name | Type | Req | Description |
|---|---|---|---|
| chat_id | integer | yes | The Telegram chat_id to send to. Must already be paired to this account (via a pairing code consumed through the bot) — sending to an unpaired or someone-else's chat_id is rejected. |
| owner_key | string|null | – | Owner key for the org that owns the paired Telegram chat. Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
| text | string | yes | – |
No output schema declared.
No examples provided.
topic_publish ~34
Publish a JSON event to a topic. Returns {ok: true, cursor}. Multiple readers can tail the same topic by cursor.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
topic_read ~109
Read events from a topic since a cursor. Omit cursor (or pass 0) to read from the start. Returns {events: [{cursor, event}], next_cursor}.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | integer|null | – | – |
| limit | integer|null | – | – |
| name | string | yes | – |
| owner_key | string|null | – | Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
unsubscribe_tag ~166
Unsubscribe the caller's account from a tag. Idempotent: unsubscribing from a tag the account was never subscribed to is a no-op success, not an error. Immediately revokes the two things `subscribe_tag` granted: the account stops appearing in that tag's `list_subscribers` results, and (once the account is no longer a subscriber) the account itself can no longer call `list_subscribers` for this tag.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_key | string|null | – | Owner key or access key credential. Optional — if omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header (an access_key must still be passed expl… |
| tag | string | yes | – |
No output schema declared.
No examples provided.
update_access_key ~179
Reassign an access_key's role_ids (whole-combination replace, bundle-26), mailbox_label, and/or expiry. Omitted fields are left unchanged. Requires an admin owner_key.
| Name | Type | Req | Description |
|---|---|---|---|
| expiry | string|null | – | New RFC3339 expiry, or omit to leave unchanged. |
| id | string | yes | The access_key's id (not the raw ak_... key material). |
| mailbox_label | string|null | – | New mailbox_label, or omit to leave unchanged. |
| owner_key | string|null | – | Owner key. Must belong to an admin member. Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
| role_ids | array|null | – | New full set of role ids to bind (replaces the existing combination), or omit to leave unchanged. |
No output schema declared.
No examples provided.
update_role ~127
Update a role's name and/or scope_expressions. Omitted fields are left unchanged (not cleared). Requires an admin owner_key.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The role's id. |
| name | string|null | – | New name, or omit to leave unchanged. |
| owner_key | string|null | – | Owner key. Must belong to an admin member. Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
| scope_expressions | array|null | – | New scope_expressions, or omit to leave unchanged. |
No output schema declared.
No examples provided.
verify ~62
Verify a magic-link token and receive one owner_key per organization this email belongs to. Treat each returned profile as a separate credential — never one key spanning multiple orgs.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | The token from the end of a magic-link URL (?token=...). |
No output schema declared.
No examples provided.
whoami ~64
Who does the server think you are, right now, for this owner_key.
| Name | Type | Req | Description |
|---|---|---|---|
| owner_key | string|null | – | Owner key to check. Optional. If omitted, defaults to the owner_key resolved from the connection's `Authorization: Bearer <owner_key>` header. |
No output schema declared.
No examples provided.
What is the raccha.ai MCP server?
raccha.ai is an MCP server listed in the public MCP registry as ai.raccha/raccha. MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access. This page covers its hosted endpoint (https://raccha.ai/mcp).
Is the raccha.ai MCP server safe to use?
raccha.ai scores 68 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 raccha.ai MCP server expose?
raccha.ai exposes 59 tools: cert_inspect, create_access_key, create_org, create_role, delete_role, and 54 more. Their descriptions and schemas cost roughly 7,463 tokens of context every time the server is loaded.
Does the raccha.ai MCP server require authentication?
No. We connected to raccha.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the raccha.ai MCP server still maintained?
raccha.ai is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.