SeenRelay MCP server
io.github.ovladon/seenrelayovladonstreamable-httpv0.3.10Scanned
Avoid redundant expensive validation. CHECK recent evidence; OBSERVE fresh independent results.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SeenRelay MCP server can do
The SeenRelay MCP server is published by the GitHub account ovladon. It has 2 tools. It can create or change data (2 tools: check_fact and observe_fact), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (observe_fact).
The fixed checks matched 2 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 0.3.10.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
check_factAvoid a duplicate expensive read-only tool call before repeating source-backed validation, especially across an agent fleet.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The input schema at properties.fact.properties.source.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.fact.properties.source.description: "Stable credential-free absolute HTTP(S) source URL. Track..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
observe_factAfter independently performing a fresh paid search, scrape, browser extraction, API read or other source-backed validation, deposit the observed result for later CHECKs.Reads text others write1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe description's first sentence says "scrape": it reads web pages, which anyone can write.
Findings
- Info
The input schema at properties.fact.properties.source.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.fact.properties.source.description: "Stable credential-free absolute HTTP(S) source URL. Track..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:09 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://seenrelay.com/mcp: tools/list returned 2 tools to an anonymous client, including check_fact (write), observe_fact (write)
Findings
Matches of fixed checks, with the text they matched.
- Infocheck_fact
The input schema at properties.fact.properties.source.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.fact.properties.source.description: "Stable credential-free absolute HTTP(S) source URL. Track..."
- Infoobserve_fact
The input schema at properties.fact.properties.source.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.fact.properties.source.description: "Stable credential-free absolute HTTP(S) source URL. Track..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:check_factChanges thingsdescription
- Changed:observe_factChanges thingsdescription
Install
Pinned to version 0.3.10. Values in angle brackets are yours to fill in.
claude mcp add --transport http seenrelay https://seenrelay.com/mcpclaude mcp add --transport http seenrelay https://seenrelay.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__seenrelay__check_fact",
"mcp__seenrelay__observe_fact"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as seenrelay. Review it before you use it.
Capability tags behind 1 rule
- mcp__seenrelay__observe_fact untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ovladon/seenrelay/verify?hash=c3ce8fddb7b8db5f215eb093cf96f23d7ce052ef2783c6298ff0ce8d6b9de194" | jq -e '.changed == false'Pinned hash c3ce8fddb7b8, from Nov 20, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ovladon/seenrelay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ovladon/seenrelay)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:43 UTC.
SeenRelay MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SeenRelay MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SeenRelay MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SeenRelay MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SeenRelay MCP server have?
- 2 tools: 2 write. check_fact and observe_fact.
Does the SeenRelay MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SeenRelay MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SeenRelay MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 6, 2026. Every change is on this page and in its Atom feed.