A

npm:@kryptosai/mcp-observatory

https://www.npmjs.com/package/@kryptosai/mcp-observatory
95/100 · MCP Trust Grade · checked 2h ago · MCP 0.20.3

What it offers — 13 tools · Developer Tools

scan

Use this to check if all your MCP servers are healthy. Auto-discovers servers from Claude config files, connects to each one, and verifies tools/promp

check_server

Use this to test a specific MCP server before installing or after updating it. Launches the server by command, checks all capabilities, and saves a ru

score_server

Use this to get a quick health grade for an MCP server. Runs all checks (capabilities, tool invocation, security) and returns a 0-100 score with A-F g

diff_runs

Use this to find what changed between two server checks. Compares two run artifacts and surfaces regressions (things that broke), recoveries (things t

get_last_run

Use this to retrieve the last check results for a server. Finds the most recent run artifact by target ID so you can review previous results or diff a

suggest_servers

Use this when setting up a project or wondering what MCP servers to add. Scans the working directory for languages, frameworks, databases, and cloud p

record

Use this to capture a baseline of a working MCP server. Records all JSON-RPC traffic to a cassette file that can be replayed offline (no server needed

replay

Use this to test a server without running it. Replays a previously recorded cassette offline and runs all checks against the recorded responses. Usefu

verify

Use this after updating a server to confirm nothing broke. Connects to the live server, sends the same requests from a recorded cassette, and compares

watch

Use this to check a server and see what changed since the last check. Runs all checks, saves the result, and diffs against the previous run for the sa

lock_verify

Verify that live MCP servers still match a previously saved lock file. Detects schema drift, added/removed tools, and breaking changes.

get_history

Get health score trends for MCP servers from run history.

ci_report

Generate a CI regression report from run artifacts.

Spec / packaging20%100
Security (OWASP MCP)30%90
Maintenance / popularity20%100
Tool hygiene15%95
Transparency / provenance15%90

Findings

INFO Static analysis of npm package @kryptosai/mcp-observatory@0.20.3 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
Grade another server

We re-grade npm:@kryptosai/mcp-observatory on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:@kryptosai/mcp-observatory grade A
Share on X Open card image

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

MCP Trust Grade A · wmcp.sh
[![MCP Trust Grade A](https://wmcp.sh/mcp/grade/npm%3A%40kryptosai%2Fmcp-observatory/badge.svg)](https://wmcp.sh/mcp/grade/npm%3A%40kryptosai%2Fmcp-observatory)
<a href="https://wmcp.sh/mcp/grade/npm%3A%40kryptosai%2Fmcp-observatory"><img src="https://wmcp.sh/mcp/grade/npm%3A%40kryptosai%2Fmcp-observatory/badge.svg" alt="MCP Trust Grade A · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.