SeenRelay
REMOTE · SEENRELAY.COM · SCANNED SEP 21
Avoid redundant expensive validation. CHECK recent evidence; OBSERVE fresh independent results.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 578 tokens (~289/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SeenRelay MCP server?
SeenRelay is a hosted endpoint at https://seenrelay.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · seenrelay.com
claude mcp add --transport http ovladon-seenrelay 'https://seenrelay.com/mcp'
{
"mcpServers": {
"ovladon-seenrelay": {
"url": "https://seenrelay.com/mcp"
}
}
} {
"servers": {
"ovladon-seenrelay": {
"type": "http",
"url": "https://seenrelay.com/mcp"
}
}
} [mcp_servers.ovladon-seenrelay] url = "https://seenrelay.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ovladon-seenrelay": {
"type": "remote",
"url": "https://seenrelay.com/mcp",
"enabled": true
}
}
} openclaw mcp add ovladon-seenrelay --url 'https://seenrelay.com/mcp' --transport streamable-http
mcp_servers:
ovladon-seenrelay:
url: "https://seenrelay.com/mcp" {
"McpServers": {
"ovladon-seenrelay": {
"Transport": "http",
"Url": "https://seenrelay.com/mcp"
}
}
} assistant mcp add ovladon-seenrelay -t streamable-http -u 'https://seenrelay.com/mcp'
{
"mcpServers": {
"ovladon-seenrelay": {
"type": "http",
"url": "https://seenrelay.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_fact” rewrote its description, which is the text the model reads security
- Tool “observe_fact” rewrote its description, which is the text the model reads security
- Schema quality: 220 → 289 ▼ functional
- Tool “check_fact” now declares an output schema ▲ functional
- Tool “observe_fact” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 8 Sept 26 +7
- Schema quality: pass → fail ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: fair → excellent functional
- “check_fact” reworded the description of “fact” cosmetic
- “check_fact” reworded the description of “known_value” cosmetic
- “check_fact” reworded the description of “max_age_seconds” cosmetic
- “observe_fact” reworded the description of “evidence_fingerprint” cosmetic
- “observe_fact” reworded the description of “fact” cosmetic
- “observe_fact” reworded the description of “idempotency_key” cosmetic
- “observe_fact” reworded the description of “observed_at” cosmetic
- “observe_fact” reworded the description of “observer_id” cosmetic
- “observe_fact” reworded the description of “observer_proof” cosmetic
- “observe_fact” reworded the description of “source_validator” cosmetic
- “observe_fact” reworded the description of “value” cosmetic
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://seenrelay.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.seenrelay.com | CN=YR1,O=Let's Encrypt,C=US | 9 Sept 2026 | 8 Dec 2026 | RSA 2048 | SHA256-RSA | 6b167c890bdc9947dc05830caf7c2858f7e |
| SANs: *.seenrelay.com, seenrelay.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of seenrelay.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| seenrelay.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://seenrelay.com/mcp | Verified | 200 | |
| http (plaintext) | http://seenrelay.com/mcp | HTTPS enforced | 308 | https://seenrelay.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_fact Check Fact Freshness ~186
Cost preflight before repeated paid or slow source-backed validation, especially across an agent fleet. Use before paid web search, metered scraping, browser/extraction, rate-limited APIs 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.
| Name | Type | Req | Description |
|---|---|---|---|
| fact | object | yes | Source-backed fact coordinate whose recent shared evidence should be checked. |
| known_value | – | yes | Caller-known value to compare with recent observations. Mutable observed content is excluded from fact identity. |
| max_age_seconds | integer | – | Maximum age, in seconds, of shared observations the caller is willing to consider. Omit to use the service default. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | object | – | Present instead of a decision status when CHECK cannot be admitted or is controlled. |
| fact_key | string | – | Canonical SeenRelay fact identity for this coordinate. |
| hive | – | – | Current bounded Hive admission/lease state. |
| next_step | string | – | Explicit cold/stale-path instruction: validate the authoritative source normally, then OBSERVE the independently obtained result. |
| status | string | – | Decision status when CHECK succeeds. Only SAME_OBSERVED can be considered for reuse, and only under caller policy. CHANGED_OBSERVED, CONTESTED, STALE and UNKNOWN require normal authoritative validati… |
| useful_reuse_awards | integer | – | Qualified reuse awards attributable to this CHECK under SeenRelay telemetry rules; not a truth or independence score. |
No examples provided.
observe_fact Contribute Fact Observation ~289
After independently performing a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_fingerprint | string | – | Optional caller-supplied fingerprint of the independently obtained evidence. SeenRelay stores it as provenance metadata and does not verify it against the source. |
| fact | object | yes | Source-backed fact coordinate for the independently obtained observation. |
| idempotency_key | string | – | Caller-chosen retry key for the same OBSERVE operation. Reusing it deduplicates an idempotent retry. |
| observed_at | string | – | ISO-8601 time when the caller obtained the observation. Omit to use server receipt time. |
| observer_id | string | – | Optional self-asserted continuity label. It is unverified unless accompanied by observer_proof. |
| observer_proof | object | – | Optional Ed25519 proof of key possession, continuity and payload integrity; not proof of truth or real-world independence. |
| source_validator | object | – | Optional source-validator metadata from the independent validation. The caller decides whether a returned hint is sufficient for source confirmation. |
| value | – | yes | Value independently obtained by the caller. Mutable observed content is excluded from fact identity. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | – | True when a new independently obtained observation was stored. Omitted when OBSERVE cannot be admitted. |
| deduplicated | boolean | – | True when an idempotent/recent duplicate was recognized and no new observation row was needed. |
| error | object | – | Present when OBSERVE cannot be admitted or is controlled. This is not a statement about source truth. |
| fact_key | string | – | Canonical SeenRelay fact identity for this coordinate. |
| future_check_eligible | boolean | – | Whether the accepted or deduplicated observation is eligible to support later CHECKs under normal freshness rules. |
| hive | – | – | Current bounded Hive admission/lease state. |
| reason | string | – | Deduplication reason when accepted=false and deduplicated=true. |
No examples provided.
What is the SeenRelay MCP server?
SeenRelay is an MCP server listed in the public MCP registry as io.github.ovladon/seenrelay. Avoid redundant expensive validation. CHECK recent evidence; OBSERVE fresh independent results. This page covers its hosted endpoint (https://seenrelay.com/mcp).
Is the SeenRelay MCP server safe to use?
SeenRelay scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SeenRelay MCP server expose?
SeenRelay exposes 2 tools: check_fact, observe_fact. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Does the SeenRelay MCP server require authentication?
No. We connected to SeenRelay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SeenRelay MCP server still maintained?
SeenRelay is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.