# io.github.vdineshk/dominion-observatory

> Runtime behavioral trust scoring for MCP servers. Check reliability before calling unknown tools.

- name: io.github.vdineshk/dominion-observatory
- version: 1.1.0
- connection class: R0 (autonomous)
- trust: 83/100
- quality: 76/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.vdineshk%2Fdominion-observatory
- tools: https://api.protogrid.dev/v1/servers/io.github.vdineshk%2Fdominion-observatory/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "dominion-observatory": {
      "type": "sse",
      "url": "https://dominion-observatory.sgdata.workers.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 99
- freshness: 45
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-97% -stale-193d
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 76/100 (good)

### protocol: 50 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- warn `protocol.transport`: only the legacy HTTP+SSE transport, deprecated until 2027-07-28
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 14 of 14 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: get_baselines (destructiveHint, idempotentHint, openWorldHint); get_compliance_report (destructiveHint, idempotentHint, openWorldHint); check_trust (destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 2,316 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 3 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 14, about 2,316 tokens to load them all
- tool set hash: 30bc6002b481fe1a7d79e2042724a2be
- tools last changed: 2026-10-06T13:38:12.691Z
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.vdineshk/dominion-observatory.svg)](https://protogrid.dev/servers/io.github.vdineshk/dominion-observatory)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-06 `attest_server` removed
  - Issue a one-hour ES256 signed observation of an indexed server's current trust verdict; unknown behavior stays unknown. Not a security guarantee.
- 2026-10-06 `get_mica_attestation` removed
  - 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.
- 2026-10-04 `attest_server` added
  - Issue a one-hour ES256 signed observation of an indexed server's current trust verdict; unknown behavior stays unknown. Not a security guarantee.

Full history: https://api.protogrid.dev/v1/servers/io.github.vdineshk%2Fdominion-observatory/changes

## Remotes

- https://dominion-observatory.sgdata.workers.dev/mcp (sse, auth none, reachable true, uptime30d 0.9741379)

## Packages

_none_

## Tools (14)

- `check_anomaly`: 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.
- `check_trust`: 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.
- `clawhub_skill_trust`: 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.
- `get_baselines`: 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.
- `get_compliance_report`: 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.
- `get_leaderboard`: 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.
- `get_server_history`: 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?
- `observatory_stats`: 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.
- `paid_trust_verdict`: 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.
- `preflight_check`: 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.
- `register_server`: Register a new MCP server in the observatory. Server owners can register their servers to start building a trust score. Registration is free.
- `report_interaction`: 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.
- `verify_attestation`: 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.
- `verify_before_call`: Run a signed pre-invocation verification immediately before an agent sends money, credentials, private data, or write access to an MCP server. The first 3 verifications per agent are free. After that, authenticate the MCP HTTP request with Authorization: Bearer do_<api_key> for Stripe metering ($0.01/call), or call once without payment to receive x402 instructions and retry with payment_tx. Returns PASS/UNCERTAIN/FAIL/UNRATED, evidence freshness, recommendation, and a signed diligence receipt.