Local MCP capabilities provider for Expo
Nothing to run from here
Dominion Observatory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Runtime behavioral trust scoring for MCP servers. Check reliability before calling unknown tools.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport sse vdineshk-dominion-observatory-mcp https://dominion-observatory.sgdata.workers.dev/mcp
# 2 — ask your agent for something these tools do
# check_trust, clawhub_skill_trust, verify_before_call and 11 more
Dominion Observatory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
VDAll 2 servers
vdineshk2 servers
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is sse, as the publisher's own manifest declares it.
claude mcp add --scope user --transport sse vdineshk-dominion-observatory-mcp https://dominion-observatory.sgdata.workers.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | yes | The URL of the MCP server to check (e.g., https://example.workers.dev/mcp) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| skill | string | yes | The ClawHub skill slug, e.g. 'calendar' |
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. Return
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | yes | The MCP server URL or tracked server name to verify |
| agent_id | string | no | Stable, non-secret agent identifier used to count the 3 introductory calls. If omitted, Dominion derives a privacy-preserving hash from network metadata. |
| payment_tx | string | no | Optional Base transaction hash proving the x402 USDC payment after a payment_required response |
| reason | string | no | Optional reason for verification, e.g. money, credentials, private_data, write_access |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_slug | string | yes | The MCP server slug/name to get a paid verdict for |
| payment_tx | string | no | Base transaction hash proving 0.001 USDC was sent to the pay_to wallet (omit on the first call to get payment instructions) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jws | string | yes | The Dominion attestation as a JWS compact string (header.payload.signature) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | The MCP server URL/name — or a ClawHub skill slug (with registry:'clawhub') — to vet before invoking |
| registry | string | no | Optional: set to 'clawhub' to vet an OpenClaw/ClawHub skill instead of an MCP server |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 |
| latency_ms | number | no | How long the call took in milliseconds |
| tool_name | string | no | Which tool you called on the server |
| error_type | string | no | If failed: timeout, auth_error, invalid_response, server_error, rate_limited, schema_mismatch |
| error_message | string | no | If failed: brief error description |
| http_status | integer | no | HTTP status code returned (200, 429, 500, etc.) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Filter by category (optional). Leave empty for overall leaderboard. |
| limit | integer | no | Number of results (default 10, max 50) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | The tool category to get baselines for (e.g., weather, finance, code, data) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | yes | The MCP server URL to check |
| observed_latency_ms | number | no | The latency you observed |
| observed_success_rate | number | no | Success rate you've observed (0.0 to 1.0) |
Register a new MCP server in the observatory. Server owners can register their servers to start building a trust score. Registration is free.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | yes | The MCP server URL |
| name | string | yes | Human-readable name of the server |
| description | string | no | What the server does |
| category | string | no | Primary category: weather, finance, code, data, search, compliance, transport, productivity, communication, other |
| github_url | string | no | GitHub repository URL (optional, improves static score) |
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?
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | yes | The MCP server URL |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server_url | string | no | Filter by server URL (optional) |
| agent_id | string | no | Filter by agent ID (optional) |
| start_date | string | no | Start date in YYYY-MM-DD format (optional) |
| end_date | string | no | End date in YYYY-MM-DD format (optional) |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Dominion Observatory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Dominion Observatory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.