Dominion Observatory
REMOTE · DOMINIONOBSERVATORY.COM · SCANNED AUG 3
Trust checks for MCP servers: trust scores, tool-drift detection, signed diligence receipts. Free.
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2025-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · dominionobservatory.com
claude mcp add --transport http com-dominionobservatory-observatory https://dominionobservatory.com/mcp
[mcp_servers.com-dominionobservatory-observatory] url = "https://dominionobservatory.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dominionobservatory-observatory": {
"type": "remote",
"url": "https://dominionobservatory.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dominionobservatory-observatory --url https://dominionobservatory.com/mcp --transport streamable-http
mcp_servers:
com-dominionobservatory-observatory:
url: "https://dominionobservatory.com/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 29 Jul 26 +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.
- 28 Jul 26 0
- Schema quality: excellent → good functional
- 27 Jul 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
- 26 Jul 26 59
First indexed and scored.
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 3 Aug 2026 · Probed https://dominionobservatory.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dominionobservatory.com | CN=WE1,O=Google Trust Services,C=US | 21 Jul 2026 | 19 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 8050b62932fb6ed813d650c31b5b43aa |
| SANs: dominionobservatory.com, www.dominionobservatory.com, *.www.dominionobservatory.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of dominionobservatory.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dominionobservatory.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dominionobservatory.com/mcp | Verified | 200 | |
| http (plaintext) | http://dominionobservatory.com/mcp | Inconclusive | 404 |
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.
check_anomaly ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The MCP server URL to check |
| Name | Type | Req | Description |
|---|---|---|---|
| anomalies | array | — | — |
| is_anomalous | boolean | — | Whether behavior is anomalous |
| recommendation | string | — | — |
| server_baselines | object | — | — |
| server_url | string | — | — |
No examples provided.
check_trust ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_url | string | yes | The URL of the MCP server to check (e.g., https://example.workers.dev/mcp) |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No examples provided.
clawhub_skill_trust ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| skill | string | yes | The ClawHub skill slug, e.g. 'calendar' |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — |
No examples provided.
get_baselines ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The tool category to get baselines for (e.g., weather, finance, code, data) |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — |
No examples provided.
get_compliance_report ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — |
No examples provided.
get_leaderboard ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter by category (optional). Leave empty for overall leaderboard. |
| limit | integer | — | Number of results (default 10, max 50) |
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Category filter applied |
| generated_at | string | — | ISO timestamp |
| servers | array | — | — |
| total_results | integer | — | — |
No examples provided.
get_mica_attestation ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| server_url | string | yes | The MCP server URL to generate attestation for |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — |
No examples provided.
get_server_history ~51
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?
| Name | Type | Req | Description |
|---|---|---|---|
| server_url | string | yes | The MCP server URL |
| Name | Type | Req | Description |
|---|---|---|---|
| history | array | — | — |
| server_url | string | — | — |
| trend | string | — | improving, stable, or degrading |
No examples provided.
observatory_stats ~44
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No examples provided.
paid_trust_verdict ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The MCP server slug/name to get a paid verdict for |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | — | — |
No examples provided.
preflight_check ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| registry | string | — | Optional: set to 'clawhub' to vet an OpenClaw/ClawHub skill instead of an MCP server |
| target | string | yes | The MCP server URL/name — or a ClawHub skill slug (with registry:'clawhub') — to vet before invoking |
| Name | Type | Req | Description |
|---|---|---|---|
| diligence_receipt | object | — | signed (EdDSA) timestamped receipt + verify_url |
| evidence | object | — | — |
| recommendation | string | — | — |
| trust_score | number | — | — |
| verdict | string | — | PASS | UNCERTAIN | FAIL | UNRATED |
No examples provided.
register_server ~118
Register a new MCP server in the observatory. Server owners can register their servers to start building a trust score. Registration is free.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Human-readable name of the server |
| server_url | string | yes | The MCP server URL |
| Name | Type | Req | Description |
|---|---|---|---|
| initial_trust_score | number | — | Starting trust score |
| message | string | — | — |
| name | string | — | — |
| registered | boolean | — | Whether registration succeeded |
| server_url | string | — | — |
No examples provided.
report_interaction ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The URL of the MCP server you called |
| success | boolean | yes | Did the call succeed? true = worked as expected, false = error or unexpected result |
| tool_name | string | — | Which tool you called on the server |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No examples provided.
verify_attestation ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| jws | string | yes | The Dominion attestation as a JWS compact string (header.payload.signature) |
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | — | — |
| key_id | string | — | — |
| payload | object | — | The decoded, verified attestation payload |
| reason | string | — | — |
| valid | boolean | — | Whether the Ed25519 signature is valid |
No examples provided.