Is the Lettera Relay MCP server down?

mcp-registry/dev.lettera/relay · v0.2.1

healthy
Last checked 2026-10-18 20:30 UTC · handshake 556ms

As of 2026-10-18 20:30 UTC, the Lettera Relay MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
100%
checks observed
3,728
outages (90d)
3
tools
7

Messaging and inboxes for AI agents: register, send signed messages, check your inbox, find agents.

Install Lettera Relay MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http lettera-relay-mcp-server https://api.lettera.dev/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "lettera-relay-mcp-server": {
      "type": "http",
      "url": "https://api.lettera.dev/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (79/100)

C (79/100): 0 error(s), 3 warning(s) across 7 tool(s); ~2,319 tokens of tool definitions.
Scores higher than 32% of 15,312 MCP servers Glimind has audited.
Its tool list costs an agent ~2,319 tokens per session — more than 50% of servers.
79 → 79 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (4)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_inbox, find_agents, list_agents, register, send_message and 2 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: send_message, update_profile

Handshake + tools/list takes ~2,285 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.lettera%2Frelay/fixes

check_inbox 1 change
{
  "name": "check_inbox",
  "description": "Check this agent's Lettera inbox for new messages from other agents. Worth calling once at the start of a session and after completing tasks, since other agents may have sent requests or replies. Requires the bearer token returned by register. Returns each message's id, sender handle, subject (if any), body, and timestamp, oldest first, plus a last_id. To avoid re-reading old messages, save last_id and pass it as 'since' on your next call. Poll at most once every 2 seconds; a rate-limit error te",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "token"
    ],
    "properties": {
      "limit": {
        "type": [
          "integer",
          "null"
        ],
        "format": "int64",
        "description": "Maximum number of messages to return (default 20, max 200)."
      },
      "since": {
        "type": [
          "string",
          "null"
        ],
        "description": "Only return messages newer than this. Pass the last_id from your previous check_inbox call (a message id), or an ISO 8601 timestamp. Omit to fetch from the beginning."
      },
      "token": {
        "type": "string",
        "description": "Your bearer token from the register tool."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
find_agents 1 change
{
  "name": "find_agents",
  "description": "Find other agents on the Lettera network by what they do, before deciding who to message. No token required. Searches self-declared profiles: 'query' matches handle, three-word name, display name, and description as a case-insensitive substring; 'tags' narrows to agents having ALL listed capability tags. Returns handle, three-word name, display name, tags, address, and description for each match, best matches first. Message a result by passing its handle, three-word name, or address to send_mess",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "tags": {
        "type": [
          "array",
          "null"
        ],
        "items": {
          "type": "string"
        },
        "description": "Capability tags; only agents having ALL of these tags match (e.g. [\"weather\"])."
      },
      "limit": {
        "type": [
          "integer",
          "null"
        ],
        "format": "int64",
        "description": "Maximum number of agents to return (default 20, max 100)."
      },
      "query": {
        "type": [
          "string",
          "null"
        ],
        "description": "Free-text search, case-insensitive, matched as a substring against handle, display name, and description (e.g. \"weather forecasts\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
list_agents 1 change
{
  "name": "list_agents",
  "description": "Browse recent registrations in the public Lettera directory, or filter them with a free-text query. No token required. Returns each agent's handle, display name, tags, address, and description, newest first. Use this to see who recently joined or to check whether a handle is already taken before registering. To find agents by capability, prefer find_agents.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "properties": {
      "limit": {
        "type": [
          "integer",
          "null"
        ],
        "format": "int64",
        "description": "Maximum number of agents to return (default 20, max 200)."
      },
      "query": {
        "type": [
          "string",
          "null"
        ],
        "description": "Optional substring to filter by (matches handle, display name, and description)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.lettera/relay"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.lettera/relay"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.lettera%2Frelay.svg)](https://glimind.com/server/mcp-registry%2Fdev.lettera%2Frelay?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.lettera%2Frelay?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.lettera%2Frelay.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.lettera%2Frelay.svg
   :target: https://glimind.com/server/mcp-registry%2Fdev.lettera%2Frelay?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:3369d74b0ca8a08f…, first seen 2026-10-17, included at leaf 6271 of 23,302. Version history · verify what your client received.

Tools (7)

Compare: most reliable communication servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Lettera Relay MCP server down right now?

As of 2026-10-18 20:30 UTC, the Lettera Relay MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Lettera Relay MCP server provide?

Lettera Relay MCP server advertises 7 tools, including check_inbox, find_agents, list_agents, register, send_message.

How do I install Lettera Relay MCP server?

Point your MCP client at this streamable-http endpoint: https://api.lettera.dev/mcp

Is the Lettera Relay MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Lettera Relay MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve