Is ai.raccha/raccha up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://raccha.ai/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 406).
https://raccha.ai/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://raccha.ai with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 67 tools: cert_inspect, create_access_key, create_org, create_role, delete_role, device_claim, device_start, discussion_claim_role, discussion_create, discussion_get, discussion_join, discussion_list, discussion_list_open, discussion_mark_seen, discussion_post, discussion_read_receipts, discussion_resolve, hash, invite_member, ip_cidr, isdomainreachable, isemailreachable, jwt_decode, kv_cas, kv_delete, kv_delete_prefix, kv_get, kv_incr, kv_list, kv_put, kv_put_ttl, list_access_keys, list_by_tag, list_profiles, list_roles, list_sse_hooks, list_subscribers, list_webhook_targets, queue_ack, queue_fetch, queue_list_items, queue_list_names, queue_nack, queue_pop, queue_pop_lease, queue_push, queue_push_delayed, queue_receipt_status, register_client, register_webhook_target, request_link, revoke_access_key, send_email_reply, stats, subscribe_tag, switch_org, telegram_pair_code, telegram_send, topic_publish, topic_read, unregister_sse_hook, unregister_webhook_target, unsubscribe_tag, update_access_key, update_role, verify, whoami.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameai.raccha/raccha
Endpointhttps://raccha.ai/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy