Spectral — verified-knowledge oracle
REMOTE · MCP.SEESPECTRAL.COM
Cross-check a factual claim against a verified knowledge graph before you assert it. Never guesses.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 25 Aug 2026.
Category Memory and Knowledge
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security0
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 1 Sept 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 31 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 30 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 29 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 28 Aug 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 27 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 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.
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 1 Sept 2026 · Probed https://mcp.seespectral.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.seespectral.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| seespectral.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.seespectral.com/mcp | Unreachable | ||
| http (plaintext) | http://mcp.seespectral.com/mcp | Inconclusive | 503 |
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 →
cross_check ~1,133
Cross-check ONE factual claim against a verified knowledge graph BEFORE you assert it — the "am I sure?" instant, just before a discrete fact leaves your mouth. Prefer this over stating such a fact from memory. Its whole job is to catch your own hallucination before it reaches the user: every call either CONFIRMS your claim with a citable source, CORRECTS it with the real value + source, or honestly ABSTAINS — it NEVER hands back a guessed value, so a call can only help or stay neutral. Honest abstention (UNVERIFIED over a confident guess) is the point, not a failure. INVOKE only when BOTH gates hold: (1) the claim is a lookup-able, atomic subject–relation–object attribute of a real, named entity a public knowledge graph would hold — a who/what/when/where property such as date of birth, place of birth, author, capital, founder, publication date, director, spouse, population — keyed on a real person, place, creative work, organization, event, or species — and, at its highest-confidence tiers, the graph also carries exact values such as a physical constant (CODATA/NIST) or a machine-checked theorem (Metamath), which it verifies best of all; AND (2) being wrong would matter — you are about to state it, cite it, or act on it. Rule of thumb: if you'd attach a citation to it and an error would be consequential, check it here first. One call per uncertain fact, at the moment of doubt — not a per-token or per-sentence reflex. INPUTS — subject: entity name ("Marie Curie") or Wikidata QID ("Q7186"), required; relation: the property as free text ("place of birth"), optional; value: your claimed value ("Warsaw"), optional — omit to just fetch the verified value(s); hint: a short disambiguator ("physicist", "1997 film") when the name is shared. RETURNS {verdict, summary (one-line, ready to quote), confidence (high|medium|none — a coarse tier-derived signal, NOT a probability), subject_id (QID), verified_values, evidence[{rel,value,tier,source}], sources, note}. V…
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | – |
| relation | string | – | – |
| subject | string | yes | – |
| value | string | – | – |
No output schema declared.
No examples provided.
lookup_facts ~67
Get the verified facts known about an entity, each with a source — to ground a statement or see what's actually established before you write. subject: a name or QID; hint: a disambiguator.
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | – | – |
| subject | string | yes | – |
No output schema declared.
No examples provided.
verify_claims ~74
Cross-check MANY claims at once — sanity-check a whole draft or answer before you commit to it. Pass a list of {subject, relation, value, hint}; get one verdict per claim (see cross_check). Ideal as a final pass over anything factual you're about to output.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
No output schema declared.
No examples provided.
How do I install the Spectral — verified-knowledge oracle MCP server?
Spectral — verified-knowledge oracle is a hosted endpoint at https://mcp.seespectral.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 · mcp.seespectral.com
claude mcp add --transport http com-seespectral-oracle 'https://mcp.seespectral.com/mcp'
What is the Spectral — verified-knowledge oracle MCP server?
Spectral — verified-knowledge oracle is an MCP server listed in the public MCP registry as com.seespectral/oracle. Cross-check a factual claim against a verified knowledge graph before you assert it. Never guesses. This page covers its hosted endpoint (https://mcp.seespectral.com/mcp).
Is the Spectral — verified-knowledge oracle MCP server safe to use?
Spectral — verified-knowledge oracle scores 0 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 Spectral — verified-knowledge oracle MCP server expose?
Spectral — verified-knowledge oracle exposes 3 tools: cross_check, verify_claims, lookup_facts. Their descriptions and schemas cost roughly 1,274 tokens of context every time the server is loaded.
Does the Spectral — verified-knowledge oracle MCP server require authentication?
Its publisher declares no required credentials for Spectral — verified-knowledge oracle. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Spectral — verified-knowledge oracle MCP server still maintained?
Spectral — verified-knowledge oracle has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 25 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.