Is Mcptrustchecker safe and trustworthy?

tashan scores Mcptrustchecker on public evidence — tashan score 54.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Mcptrustchecker?

In Claude Code: run `claude mcp add mcptrustchecker -- npx -y mcptrustchecker`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Mcptrustchecker?

source: illiahaidar/mcptrustchecker.

‹ The Index

Mcptrustchecker

npm

Local-first, deterministic security scanner for Model Context Protocol (MCP) servers. Cross-tool toxic-flow analysis, Unicode-smuggling decode, prompt-injection & supply-chain detection, with an auditable 0–100 Trust Score.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Security — see all ranked ›

Work: Security review

Who it is for: Security engineer

Install (Claude Code):

claude mcp add mcptrustchecker -- npx -y mcptrustchecker

tashan score: 54.0
Adoption: 114/wk
Upkeep: 66.0
Freshness: 93.0
Evidence coverage: 100% of the inputs this score can use
Health: active

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.12.1 — this package, not its dependency tree

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Mcptrustchecker scores 54 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-mcptrustchecker.svg)](https://tashan.sh/capability/pkg-mcptrustchecker.html)

npm ↗ · source ↗ · pkg:mcptrustchecker

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-15 · scorer s5 · how · something wrong here?