MCP.Market

SeenRelay MCP server

online · 100% uptime
by ovladon·io.github.ovladon/seenrelay·v0.3.10

Avoid redundant expensive validation. CHECK recent evidence; OBSERVE fresh independent results.

A91/100grade A
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed SeenRelay yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SeenRelay tools (2)

write = sends, deletes, buys or posts
  • check_factFree

    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 validation or multi-step validation when the caller already has a known value. Returns SAME_OBSERVED, CHANGED_OBSERVED, CONTESTED, STALE or UNKNOWN. Only SAME_OBSERVED can be considered for caller-policy-gated reuse; every other status requires normal authoritative validation before OBSERVE. SeenRelay never browses or verifies externally.

  • observe_factFree

    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 deduplicated=true for a recognized retry/recent duplicate. Never OBSERVE hearsay. Optional Ed25519 proof establishes key possession and continuity, not truth or real-world independence.

Public scan report

scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 604ms20/20
  • Tool poisoning2 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How SeenRelay compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,243 servers
Tools
2
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
269 ms
faster than 56% of 30,027 servers

What its tools let an agent do: 2 read

Install SeenRelay in Claude Code, Cursor or VS Code

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

What the publisher says

From the SeenRelay repository's README, as published. We do not edit it. Read it on GitHub

SeenRelay

Find out whether your agent fleet is wasting time or provider spend on repeated read-only validation — before enabling reuse.

SeenRelay starts with a free shadow audit. Run the workload you already have while every authoritative validation stays enabled. Measure exact recurrence, stronger local/source/provider-native controls, safety equivalence and prospective economics. Keep SeenRelay only where the result is USE; accept DO NOT USE or INSUFFICIENT EVIDENCE everywhere else.

Currently free · no account · no SeenRelay API key required.

SeenRelay itself requires no account or API key. A third-party client, directory, gateway, or assistant may require its own account to use that third-party service; that is not a SeenRelay access requirement. The canonical direct MCP endpoint is https://seenrelay.com/mcp.

Fastest start: give the audit to your coding agent

npx skills add https://seenrelay.com --skill seenrelay --yes

Then ask it:

Run a SeenRelay shadow audit on this project. Find repeated expensive read-only validations, preserve every authoritative call, measure stronger local/source/provider-native controls first, do not enable reuse, and return USE / DO NOT USE / INSUFFICIENT EVIDENCE for each measured workload.

Or use the developer paths below. Full audit method: docs/SHADOW_AUDIT.md.

<!-- BEGIN GENERATED:PUBLIC-FACTS --> Install: npm install seenrelay · pip install seenrelay · client v0.2.14 · currently free · no account/API key. <!-- END GENERATED:PUBLIC-FACTS -->

Free shadow audit: measure without changing application behavior

Ambient wraps an existing MCP-style client in local shadow mode. The authoritative call still runs; SeenRelay measures exact repetition and produces a local report.

JavaScript / TypeScript:

npm install seenrelay
import { ambientMcpClient } from 'seenrelay/ambient';

const client = ambientMcpClient(rawMcpClient);
// use client.callTool(...) normally
console.log(client.seenRelayAmbient.getReport());

Python:

pip install seenrelay
from seenrelay_ambient import ambient_mcp_client

client = ambient_mcp_client(raw_mcp_client)
# await client.call_tool(...) normally
print(client.get_report())

Run the existing workload and inspect the report before enabling any bounded reuse. Shared CHECK remains optional and off by default in Zero-State.

SeenRelay is a provider-independent reuse layer for repeated read-only validation. It has exactly two hosted domain operations: CHECK and OBSERVE, and reports recent observations rather than universal truth.

Current JavaScript/TypeScript and Python clients include multi-signal shared-evidence assurance helpers, deterministic Fact Coordinate Kit v1 and provider-independent Zero-State. Python Zero-State supports explicit read-only in-flight/local reuse, caller-owned private L1 and source-native conditional validation before authoritative fallback. The classic Python API and Python Ambient adapters remain shadow-first by default. Shared evidence is explicit caller policy, does not prove truth or independent real-world actors, and MCP/OpenAPI coordinates are local repetition keys unless a stable source-native locator supports a shared fact descriptor. Provider-specific adapters are optional.

What it can avoid

Even with no shared observation:

  • simultaneous identical eligible calls can be coalesced in-process;
  • completed read-only results can be reused only inside an explicit caller-defined freshness window;
  • optional encrypted caller-owned L1 storage can reuse values across workers or restarts;
  • ETag / Last-Modified can support source-native conditional confirmation without a shared CHECK;
  • shared CHECK is optional in Zero-State and is not placed on the hot path merely because SeenRelay is installed;
  • after a genuinely fresh independent validation, OBSERVE can add evidence that may help later callers.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

SeenRelay: common questions

Is SeenRelay MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the SeenRelay safety report
How do I install SeenRelay?
It runs remotely at seenrelay.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does SeenRelay need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is SeenRelay maintained?
The last commit was 7 days ago (2026-10-29). The latest release is v0.3.10.
Is SeenRelay up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does SeenRelay compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,243 servers); tools 2 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.