Is Test Servers safe and trustworthy?

tashan scores Test Servers on public evidence — tashan score 44.0/100, it is currently abandoned, 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 Test Servers?

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

Who maintains Test Servers?

See the linked source repository..

‹ The Index

Test Servers

npm

A collection of MCP test servers including working servers (ping, resource, combined, env-echo) and test failure cases (broken-tool, crash-on-startup)

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

Install (Claude Code):

claude mcp add msfeldstein-mcp-test-servers -- npx -y @msfeldstein/mcp-test-servers

Looking for a replacement? npx tashan-cli doctor is free and tells you everything above about your whole config. tashan Pro names the replacement — which one, and how it measures. $6/mo.

tashan score: 44.0
Adoption: 433/wk
Upkeep: 68.0
Freshness: 48.0
Evidence coverage: 100% of the inputs this score can use
Health: abandoned
License: ISC

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.1.72 — 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

Test Servers scores 44 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

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-msfeldstein-mcp-test-servers.svg)](https://tashan.sh/capability/pkg-msfeldstein-mcp-test-servers.html)

npm ↗ · pkg:@msfeldstein/mcp-test-servers

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?