Skip to content
SeenRelay logo

SeenRelay MCP server

Which MCP servers are SeenRelay's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-22

← Back to SeenRelay

Whose server it is
  • Addresshttps://seenrelay.com/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on seenrelay.com when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

When we asked itchecked 2026-10-28
  • Stateanswerschecked 2026-10-28
  • Tools2
  • Server calls itselfseenrelay
  • Server version0.3.10
  • Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 93 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: measure which AI agent tool calls repeat unchanged; reuse paid web search results while the monitored event is unchanged.
  • Checked on 6 of the 7 days it takes to judge reliability.

Once connected

  • For "reuse paid web search results while the monitored event is unchanged", the likely first call is check_fact.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 6, the first on 2026-10-28
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring6 of the 7 daily checks it takes to print a share
  • Median first answer87 ms
  • Space in an agent's context≈ 1,903 tokensthe definitions of all its tools (2), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results2 of 2 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · measure which AI agent tool calls repeat unchanged
  • can do · reuse paid web search results while the monitored event is unchanged
  • not sure · refresh a paid briefing when the monitored event changes

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-28
  • check_fact

    Avoid a duplicate expensive read-only tool call before repeating source-backed validation, especially across an agent fleet. Use for repeated paid web search, metered scraping, browser/extraction, rate-limited APIs, duplicate API…

  • observe_fact

    After independently performing a fresh paid search, scrape, browser extraction, API read or other source-backed validation, deposit the observed result for later CHECKs. Returns accepted=true when a new observation is stored or…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://seenrelay.com/mcp as a custom connector in the settings.

OpenAPI spec

5 paths, read 2026-10-22. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.