# Dominion Observatory (remote · dominionobservatory.com)

Trust checks for MCP servers: trust scores, tool-drift detection, signed diligence receipts. Free.

- Trust score: 60/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `dominionobservatory.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/com-dominionobservatory-observatory/dominionobservatory.md), [page](https://verifymcp.io/servers/com-dominionobservatory-observatory/dominionobservatory)

## Channel facts

- Endpoint: `https://dominionobservatory.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 12 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1771 tokens (~110/item across 16 items; 14 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2025-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-dominionobservatory-observatory https://dominionobservatory.com/mcp
```

### Codex

```toml
[mcp_servers.com-dominionobservatory-observatory]
url = "https://dominionobservatory.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-dominionobservatory-observatory --url https://dominionobservatory.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dominionobservatory-observatory:
    url: "https://dominionobservatory.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-dominionobservatory-observatory": {
      "type": "http",
      "url": "https://dominionobservatory.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 60, +1)

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

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

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

### 2026-07-31 (score 58, −2)

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

### 2026-07-30 (score 60, 0)

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

### 2026-07-29 (score 60, +1)

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

### 2026-07-28 (score 59, 0)

- [functional] Schema quality: excellent → good

### 2026-07-27 (score 59, 0)

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

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (14)

### `check_trust` (~103 tokens)

Get the trust score and reliability metrics for any MCP server. Use this BEFORE calling an unknown MCP server to assess if it's reliable. Returns trust_score (0-100), latency stats, uptime, success rate, and how many agents have used it. Scores above 70 indicate reliable servers. Scores below 30 indicate risky servers.

Input parameters:

- `server_url` (string, required): The URL of the MCP server to check (e.g., https://example.workers.dev/mcp)

Output parameters:

- `category` (string): Server category (search, code, database, etc.)
- `first_seen` (string): ISO date when first tracked
- `found` (boolean): Whether the server was found in the observatory
- `last_checked` (string): ISO date of last check
- `metrics` (object)
- `name` (string): Server display name
- `recent_7d` (object)
- `runtime_score` (number): Runtime behavioral score 0-100
- `server_url` (string): The queried server URL
- `static_score` (number): Static analysis score 0-100
- `trust_score` (number): Overall trust score 0-100

### `clawhub_skill_trust` (~129 tokens)

Check the supply-chain trust of a ClawHub (OpenClaw) skill BEFORE installing or invoking it. After the Feb-2026 ClawHavoc supply-chain attack, third-party skills can carry malware. Returns a PASS/UNCERTAIN/FAIL badge and 0-100 score aggregating ClawHub's published security scan (VirusTotal + model), moderation verdict, and provenance. Malicious/suspicious/blocked => FAIL; unscanned => UNCERTAIN.

Input parameters:

- `skill` (string, required): The ClawHub skill slug, e.g. 'calendar'

Output parameters:

- `badge` (string): PASS | UNCERTAIN | FAIL
- `reasons` (array)
- `registry` (string)
- `score` (number): 0-100 supply-chain trust score
- `signals` (object): security_status, virustotal_verdict, verify_decision, moderation_suspicious, publisher, latest_version
- `skill` (string)

### `paid_trust_verdict` (~153 tokens)

Get the PREMIUM behavioral trust verdict for an MCP server, with a signed, citable, tamper-evident attestation receipt. This is a paid x402 service: call WITHOUT payment_tx to receive payment instructions (0.001 USDC on Base), pay, then call again WITH the payment_tx (transaction hash, single-use) to receive the full verdict + receipt. The free check_trust tool remains available for basic scores.

Input parameters:

- `payment_tx` (string): Base transaction hash proving 0.001 USDC was sent to the pay_to wallet (omit on the first call to get payment instructions)
- `server_slug` (string, required): The MCP server slug/name to get a paid verdict for

Output parameters:

- `amount` (string)
- `currency` (string)
- `pay_to` (string)
- `payment_status` (string): payment_required | verified
- `receipt` (object): signed attestation receipt (when paid)
- `trust_score` (number)
- `verdict` (string)

### `verify_attestation` (~101 tokens)

Cryptographically verify a Dominion signed attestation (JWS) — e.g. a trust-verdict receipt, gateway attestation, or MCP Verified badge. Stateless: checks the Ed25519 signature against Dominion's published public key (no trust in this server required). Use this to confirm a receipt another party gave you is authentic and untampered.

Input parameters:

- `jws` (string, required): The Dominion attestation as a JWS compact string (header.payload.signature)

Output parameters:

- `issuer` (string)
- `key_id` (string)
- `payload` (object): The decoded, verified attestation payload
- `reason` (string)
- `valid` (boolean): Whether the Ed25519 signature is valid

### `preflight_check` (~159 tokens)

Run a PRE-FLIGHT due-diligence check on an MCP server BEFORE your agent invokes it. Returns a verdict (PASS/UNCERTAIN/FAIL/UNRATED) plus a SIGNED, timestamped diligence receipt you keep as proof you performed a trust check — the standard of care after the ClawHavoc/Miasma supply-chain attacks. Call this before connecting to or invoking any unfamiliar MCP server.

Input parameters:

- `registry` (string): Optional: set to 'clawhub' to vet an OpenClaw/ClawHub skill instead of an MCP server
- `target` (string, required): The MCP server URL/name — or a ClawHub skill slug (with registry:'clawhub') — to vet before invoking

Output parameters:

- `diligence_receipt` (object): signed (EdDSA) timestamped receipt + verify_url
- `evidence` (object)
- `recommendation` (string)
- `trust_score` (number)
- `verdict` (string): PASS | UNCERTAIN | FAIL | UNRATED

### `report_interaction` (~186 tokens)

Report the outcome of calling an MCP server. Call this AFTER you use any MCP server to contribute to the trust network. Your report helps other agents make better decisions. This is free and takes <1ms.

Input parameters:

- `error_message` (string): If failed: brief error description
- `error_type` (string): If failed: timeout, auth_error, invalid_response, server_error, rate_limited, schema_mismatch
- `http_status` (integer): HTTP status code returned (200, 429, 500, etc.)
- `latency_ms` (number): How long the call took in milliseconds
- `server_url` (string, required): The URL of the MCP server you called
- `success` (boolean, required): Did the call succeed? true = worked as expected, false = error or unexpected result
- `tool_name` (string): Which tool you called on the server

Output parameters:

- `message` (string): Confirmation message
- `new_trust_score` (number): Updated trust score after this report
- `recorded` (boolean): Whether the interaction was recorded
- `server_url` (string): The server URL
- `success_rate` (number): Updated success rate percentage
- `total_interactions` (integer): Total interactions now tracked

### `get_leaderboard` (~92 tokens)

Get the top-rated MCP servers, optionally filtered by category. Use this to discover the most reliable MCP servers in the ecosystem. Categories include: weather, finance, code, data, search, compliance, transport, productivity, communication.

Input parameters:

- `category` (string): Filter by category (optional). Leave empty for overall leaderboard.
- `limit` (integer): Number of results (default 10, max 50)

Output parameters:

- `category` (string): Category filter applied
- `generated_at` (string): ISO timestamp
- `servers` (array)
- `total_results` (integer)

### `get_baselines` (~80 tokens)

Get behavioral baselines for a tool category. Shows what 'normal' looks like — average latency, success rates, typical call patterns. Use this to evaluate whether a specific server's performance is within normal range for its category.

Input parameters:

- `category` (string, required): The tool category to get baselines for (e.g., weather, finance, code, data)

Output parameters:

- `baselines_available` (boolean): Whether enough data exists for baselines
- `category` (string)
- `message` (string)
- `metrics` (object): Per-metric baselines with average, median, p95, min, max
- `preliminary_stats` (object)

### `check_anomaly` (~100 tokens)

Check if observed behavior from an MCP server is anomalous compared to baselines. Use this when a server seems slow, unreliable, or returns unexpected results. Returns whether the behavior deviates significantly from normal patterns.

Input parameters:

- `observed_latency_ms` (number): The latency you observed
- `observed_success_rate` (number): Success rate you've observed (0.0 to 1.0)
- `server_url` (string, required): The MCP server URL to check

Output parameters:

- `anomalies` (array)
- `is_anomalous` (boolean): Whether behavior is anomalous
- `recommendation` (string)
- `server_baselines` (object)
- `server_url` (string)

### `register_server` (~118 tokens)

Register a new MCP server in the observatory. Server owners can register their servers to start building a trust score. Registration is free.

Input parameters:

- `category` (string): Primary category: weather, finance, code, data, search, compliance, transport, productivity, communication, other
- `description` (string): What the server does
- `github_url` (string): GitHub repository URL (optional, improves static score)
- `name` (string, required): Human-readable name of the server
- `server_url` (string, required): The MCP server URL

Output parameters:

- `initial_trust_score` (number): Starting trust score
- `message` (string)
- `name` (string)
- `registered` (boolean): Whether registration succeeded
- `server_url` (string)

### `get_server_history` (~51 tokens)

Get daily trust score and performance history for a server over the last 30 days. Use this to see trends — is the server improving or degrading?

Input parameters:

- `server_url` (string, required): The MCP server URL

Output parameters:

- `history` (array)
- `server_url` (string)
- `trend` (string): improving, stable, or degrading

### `observatory_stats` (~44 tokens)

Get overall statistics about the Dominion Observatory — total servers tracked, total interactions recorded, coverage by category, and data freshness. Use this to understand the scope of the trust network.

Output parameters:

- `avg_trust_score` (number): Network-wide average trust score
- `categories` (object): Server count per category
- `last_interaction` (string): ISO timestamp of most recent interaction
- `total_interactions` (integer): Total interactions recorded
- `total_servers` (integer): Total MCP servers tracked

### `get_compliance_report` (~126 tokens)

Export a compliance-ready audit trail of all recorded interactions. Formatted for EU AI Act Article 12 and Singapore IMDA Agentic AI Governance Framework. Filter by server, agent, or date range. Essential for enterprises that need to prove their AI agents are behaving correctly.

Input parameters:

- `agent_id` (string): Filter by agent ID (optional)
- `end_date` (string): End date in YYYY-MM-DD format (optional)
- `server_url` (string): Filter by server URL (optional)
- `start_date` (string): Start date in YYYY-MM-DD format (optional)

Output parameters:

- `framework` (string): Compliance framework (EU AI Act / IMDA)
- `generated_at` (string)
- `interactions` (array): Audit trail entries
- `period` (object)
- `report_id` (string): Unique report identifier
- `total_records` (integer)

### `get_mica_attestation` (~126 tokens)

Generate an EU AI Act Article 12-style behavioral audit attestation for an MCP server — timestamped, auditable interaction records for record-keeping/traceability. (EU AI Act high-risk obligations were deferred by the Digital Omnibus to 2 Dec 2027 for Annex III and 2 Aug 2028 for Annex I products; GPAI-provider obligations apply from Aug 2026.) Returns behavioral grade, risk level, monitoring continuity status, and links to full audit exports.

Input parameters:

- `server_url` (string, required): The MCP server URL to generate attestation for

Output parameters:

- `attestation_uri` (string): URI for the full attestation document
- `audit_export_url` (string): URL to download full audit trail
- `compliance_grade` (string): A+, A, B, C, D, or F
- `generated_at` (string)
- `monitoring_continuity` (boolean): Whether continuous monitoring is active
- `risk_level` (string): low, medium, high, or critical
- `server_url` (string)
- `trust_score` (number)

## Diagnostics

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

## Score history

- 2026-08-03: 60
- 2026-08-02: 59
- 2026-08-01: 59
- 2026-07-31: 58
- 2026-07-30: 60
- 2026-07-29: 60
- 2026-07-28: 59
- 2026-07-27: 59
- 2026-07-26: 59

## Links

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