TrustedMCP
NPM · TRUSTEDMCP
A-D grades for MCP servers: look one up, check your MCP config, find graded alternatives.
Available components
Last scanned (4 minutes ago)
Scores higher than 49% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 658 tokens (~164/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +4
- Stability: unverified → 0.27 ▲ functional
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 54
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Analysed npm/trustedmcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_config Check an MCP config ~179
Grade every MCP server in an MCP config. With no arguments, reads the usual config files on this machine (Claude Desktop, Claude Code, Cursor, VS Code, Windsurf). Or pass `client` for one app, `path` for one file, or `config` with the JSON text. The file is read locally; only package names, image names and server URLs (no query strings) are sent to TrustedMCP. Env vars, headers, tokens and file paths never leave the machine.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Only this app: claude_desktop, claude_code, cursor, vscode or windsurf |
| config | string | – | The config JSON itself, e.g. the contents of claude_desktop_config.json |
| path | string | – | Path to one .json or .jsonc MCP config file |
No output schema declared.
No examples provided.
find_alternatives Find graded MCP servers ~134
List TrustedMCP-graded MCP servers, best grade first. Filter by category ('databases', 'browser automation'), a search term, or the minimum grade; or pass `instead_of` with a server name or package to get better-graded servers in its category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category name or slug |
| instead_of | string | – | A server to replace: name, slug, package or URL |
| limit | integer | – | – |
| min_grade | string | – | Lowest grade to include (default B) |
| query | string | – | Search term matched against name, vendor and summary |
No output schema declared.
No examples provided.
lookup_server Look up an MCP server ~135
Get an MCP server's TrustedMCP grade (A-D) by name, npm or PyPI package, Docker image, server URL, GitHub repo or launch command (e.g. 'npx -y @playwright/mcp'). Returns the four checks (login, upkeep, known bugs, connection), what to fix first and the TrustedMCP page. For servers without a grade, returns matching official MCP Registry entries.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Name, package, image, URL, repo or command, e.g. 'notion', '@playwright/mcp', 'https://mcp.stripe.com' |
No output schema declared.
No examples provided.
registry_lookup Official MCP Registry entry ~94
Get an official MCP Registry entry ('io.github.owner/repo') with its packages, remotes, TrustedMCP grade if any, and reported security issues (GHSA/CVE advisories, and whether the listed version is affected). Also accepts a package name or search term and picks the best matching entry.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Registry name like 'io.github.owner/repo', or a package name or search term |
No output schema declared.
No examples provided.
How do I install the TrustedMCP MCP server?
TrustedMCP runs locally as an npm package, launched with npx -y trustedmcp mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · trustedmcp
claude mcp add io-trustedmcp-trustedmcp -- npx -y trustedmcp mcp
What is the TrustedMCP MCP server?
TrustedMCP is an MCP server listed in the public MCP registry as io.trustedmcp/trustedmcp. A-D grades for MCP servers: look one up, check your MCP config, find graded alternatives. This page covers its npm package (trustedmcp).
Is the TrustedMCP MCP server safe to use?
TrustedMCP scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TrustedMCP MCP server expose?
TrustedMCP exposes 4 tools: lookup_server, check_config, find_alternatives, registry_lookup. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.
Is the TrustedMCP MCP server still maintained?
TrustedMCP is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the TrustedMCP MCP server under?
TrustedMCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the TrustedMCP MCP server?
VerifyMCP ran 16 checks on TrustedMCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.