# Spectral — verified-knowledge oracle (remote · mcp.seespectral.com)

Cross-check a factual claim against a verified knowledge graph before you assert it. Never guesses.

- Trust score: 54/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.seespectral.com`: 54/100 (this document), [markdown](https://verifymcp.io/servers/com-seespectral-oracle/mcp.md), [page](https://verifymcp.io/servers/com-seespectral-oracle/mcp)

## Channel facts

- Endpoint: `https://mcp.seespectral.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1274 tokens (~424/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-seespectral-oracle https://mcp.seespectral.com/mcp
```

### Codex

```toml
[mcp_servers.com-seespectral-oracle]
url = "https://mcp.seespectral.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seespectral-oracle": {
      "type": "remote",
      "url": "https://mcp.seespectral.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-seespectral-oracle --url https://mcp.seespectral.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-seespectral-oracle:
    url: "https://mcp.seespectral.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-seespectral-oracle": {
      "type": "http",
      "url": "https://mcp.seespectral.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 52, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 51)

First indexed and scored.

## MCP tools (3)

### `cross_check` (~1133 tokens)

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…

Input parameters:

- `hint` (string)
- `relation` (string)
- `subject` (string, required)
- `value` (string)

### `verify_claims` (~74 tokens)

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.

Input parameters:

- `claims` (array, required)

### `lookup_facts` (~67 tokens)

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.

Input parameters:

- `hint` (string)
- `subject` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-seespectral-oracle/mcp#diagnostics

## Score history

- 2026-08-03: 54
- 2026-08-02: 53
- 2026-08-01: 53
- 2026-07-31: 52
- 2026-07-30: 51

## Links

- Remote endpoint: https://mcp.seespectral.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-seespectral-oracle/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-seespectral-oracle/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-seespectral-oracle/mcp