MCP Observatory
CI-native security testing for MCP servers. Attack simulation, schema drift detection, and health scoring before agents depend on them.
Is MCP Observatory safe? Strong public trust posture, backed by multiple independent signals.
Compare MCP Observatory
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: MCP Observatory scores 82.6/100 (Grade A), ranked #118 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.6/10; 40% of recent commits are signed; last pushed 2026-09-22. Every point is earned from checkable signals — never paid placement. How scoring works →
How MCP Observatory compares in MCP Servers
- #50 XcodeBuildMCP 83.0 +0.4
- #51 Esa MCP Server 82.8 +0.2
- #52 MCP Observatory 82.6 this agent
- #53 AIquila — Nextcloud MCP Server 82.5 −0.1
- #54 Kubernetes MCP Server 82.2 −0.4
Bars show each HVTrust score; the tick marks MCP Observatory’s 82.6.
Where the 82.6 comes from
HVTrust dimensions vs the MCP Servers average
82.6 / 100 · 100.0% confidenceMCP Observatory MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
60.5 / 100Supply Chain Trust
Common questions about MCP Observatory
Does MCP Observatory publish package provenance?
Does MCP Observatory have an OpenSSF Scorecard?
Is MCP Observatory actively maintained?
What license does MCP Observatory use?
Are MCP Observatory's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to MCP Observatory's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain MCP Observatory?
For maintainers
HVTrust scores MCP Observatory from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/mcp-observatory)
<a href="https://hvtracker.net/agents/mcp-observatory"><img src="https://hvtracker.net/badge/mcp-observatory.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON