mcp-test-mcp
npm
v0.5.2
Published by rdwj — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
An MCP server for testing MCP servers you are developing with AI assistants
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −1.2 | Package runs install-time scripts MTC-SUP-010 | supply-chain |
2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
In the server's implementation (`index.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: st { spawn } = require('child_process'); const path = require('path'); const fs = require('fs'); /** * Node.js wrapper
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server index.js
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/postinstall.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ync, spawn } = require('child_process'); const path = require('path'); const fs = require('fs'); /** * Postinstall scr
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/postinstall.js
"mcp-test-mcp" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.
Evidence: node scripts/postinstall.js
Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.
Location: package mcp-test-mcp
Each tool and what it can reach — statically extracted from the published source.
addno sensitive capabilitycall_toolno sensitive capabilityconnect_to_serverno sensitive capabilitydisconnectno sensitive capabilityechono sensitive capabilityexecute_prompt_with_llmno sensitive capabilityget_connection_statusno sensitive capabilityget_promptno sensitive capabilityhealth_checkno sensitive capabilitylist_promptsno sensitive capabilitylist_resourcesno sensitive capabilitylist_toolsno sensitive capabilitypingno sensitive capabilityread_resourceno sensitive capabilityScan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.2 latest |
A 92/100 | 3 | 1.13.0 | 2026-09-07 |
v0.4.0 |
A 92/100 | 3 | 1.13.0 | 2026-09-04 |
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan mcp-test-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 9 side by side →
A Model Context Protocol (MCP) server providing mathematical utility tools including Fibonacci sequence generation and number summation
Demo Model Context Protocol server
Security scan results for the Test (npm) MCP server.
mcp test and study - A Model Context Protocol server for train ticket queries
A custom MCP SSE HTTP Server with parameter support
一个天气MCP服务,提供天气预报和天气警报功能
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.