io.github.vdineshk/dominion-observatory

MCPcommunitylive
v1.1.0io.github.vdineshkUnknownUpdated 5mo agoGitHub

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

The behavioral trust layer for the AI agent economy. Check MCP server reliability before you call. Report outcomes to strengthen the trust network. Every AI agent needs to know: "Can I trust this MCP server?" The Dominion Observatory answers that question with real runtime data — not GitHub stars, not static scans, but actual performance metrics from real agent interactions. Before calling an…

Endpoint healthlive
checked 3 days ago · 159ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (sse). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1GitHub stars
3Forks
5mo agoLast update
Package
Authorio.github.vdineshk
LicenseUnknown
Version1.1.0
Sourcemcp-registry
GitHubvdineshk/dominion-observatory
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface20 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

20 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

check_trustNo description published

This tool published no description. Forge does not invent one.

report_interactionNo description published

This tool published no description. Forge does not invent one.

get_leaderboardNo description published

This tool published no description. Forge does not invent one.

get_baselinesNo description published

This tool published no description. Forge does not invent one.

check_anomalyNo description published

This tool published no description. Forge does not invent one.

register_serverNo description published

This tool published no description. Forge does not invent one.

get_server_historyNo description published

This tool published no description. Forge does not invent one.

observatory_statsNo description published

This tool published no description. Forge does not invent one.

get_compliance_reportNo description published

This tool published no description. Forge does not invent one.

get_mica_attestationNo description published

This tool published no description. Forge does not invent one.

assess_server_trustNo description published

This tool published no description. Forge does not invent one.

server_urlNo description published

This tool published no description. Forge does not invent one.

ecosystem_overviewNo description published

This tool published no description. Forge does not invent one.

trustNo description published

This tool published no description. Forge does not invent one.

telemetryNo description published

This tool published no description. Forge does not invent one.

discoveryNo description published

This tool published no description. Forge does not invent one.

complianceNo description published

This tool published no description. Forge does not invent one.

attestationNo description published

This tool published no description. Forge does not invent one.

paymentNo description published

This tool published no description. Forge does not invent one.

dominion-observatoryNo description published

This tool published no description. Forge does not invent one.

0 of 20 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The behavioral trust layer for the AI agent economy. Check MCP server reliability before you call. Report outcomes to strengthen the trust network. Every AI agent needs to know: "Can I trust this MCP server?" The Dominion Observatory answers that question with real runtime data — not GitHub stars, not static scans, but actual performance metrics from real agent interactions. Before calling an unknown MCP server → tells you if it's reliable After calling any MCP server → contributes to the trust…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

20 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.