Security & Testing

raccha.ai

Manages roles, access keys, and device authentication for secure access control.

1 endpoint26 known toolsFirst detected August 16, 2026Last detected August 16, 2026

ENDPOINT 1

https://raccha.ai/mcp

No auth detected

MCP server metadata

Name: rmcp
Version: 3.1.2

Capabilities

tools

Server instructions

raccha.ai: request_link + verify for magic-link auth (returns one owner_key per org — keep each as a separate profile), kv_put/kv_get for namespace-scoped storage, queue_push/queue_pop for namespace-scoped FIFO queues, stats for org counts, telegram_pair_code/telegram_send for the Telegram bot (pairing mints a code you DM to the bot; send only works to chat_ids already paired to your account). jwt_decode, hash, cert_inspect, and ip_cidr are stateless utility tools — no auth, no owner_key required. The website (raccha.ai) is config/stats only — use these tools for all data access.

Known tools 26

cert_inspect

Parse a PEM-encoded X.

Inferred read-only

create_access_key

Create a scoped, revocable access_key bound to a role.

Potential side effects

create_role

Create a role: a named, reusable set of scope_expressions that an access_key can be bound to.

Potential side effects

delete_role

Delete a role.

Potential side effects

device_claim

Poll for the result of a device_start flow.

Inferred read-only

device_start

Start a device-code sign-in (RFC 8628 shape).

Inferred read-only

hash

Compute a hash digest of an input string.

Inferred read-only

invite_member

Invite an email to join your account.

Potential side effects

ip_cidr

IPv4/IPv6 CIDR math.

Inferred read-only

jwt_decode

Decode a JWT's header and payload (base64url + JSON, no crypto).

Inferred read-only

kv_get

Fetch a JSON value by key from your namespace.

Inferred read-only

kv_put

Store a JSON value under a key in your namespace.

Inferred read-only

list_access_keys

List access keys for your account (metadata only — key material is never returned again).

Inferred read-only

list_roles

List roles defined for your account.

Inferred read-only

queue_pop

Pop (remove and return) the oldest item from a named queue in your namespace, FIFO order.

Potential side effects

queue_push

Push a JSON value onto the tail of a named queue in your namespace.

Inferred read-only

register_client

Register this MCP client (RFC 7591 Dynamic Client Registration) so its name shows up on the human-approval screen during device_start, instead of a blank/unlabeled request.

Inferred read-only

request_link

Request a magic sign-in link for an email.

Potential side effects

revoke_access_key

Revoke an access_key by its id (not the raw ak_.

Inferred read-only

stats

Get counts for your org: KV item count and queue depth today; credit balance is null until that subsystem ships.

Inferred read-only

telegram_pair_code

Mint a short-lived one-time pairing code.

Inferred read-only

telegram_send

Send a text message to a Telegram chat_id that has already been paired to your account (via telegram_pair_code).

Potential side effects

update_access_key

Reassign an access_key's role_ids (whole-combination replace, bundle-26), mailbox_label, and/or expiry.

Inferred read-only

update_role

Update a role's name and/or scope_expressions.

Potential side effects

verify

Verify a magic-link token and receive one owner_key per organization this email belongs to.

Potential side effects

whoami

Who does the server think you are, right now, for this owner_key.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.rmcp]
url = "https://raccha.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "rmcp": {
      "type": "http",
      "url": "https://raccha.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: rmcp
Remote MCP URL: https://raccha.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "rmcp": {
      "url": "https://raccha.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "rmcp": {
      "type": "http",
      "url": "https://raccha.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "rmcp",
  "transport": "streamable-http",
  "url": "https://raccha.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for raccha.ai was fetched 2026-08-21T13:12:38.380Z.

Trust status Trusted

raccha.ai is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.