Trace MCP
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm trace-mcp 3.44.3 (MIT; repo nikolai-vysotskyi/trace-mcp). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 29 tools (29 annotated by the server: 25 read-only, 0 destructive). Real calls: 2 of 2 real function calls passed.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): pass. 2 of 2 real function calls passed. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 7192 tokens, cl100k estimate (29 tools, measured 2026-11-18 UTC, version 3.44.3). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 24 read, 3 write (state-changing), 2 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
batch— readfind_usages— readget_call_graph— readget_change_impact— readget_context_bundle— readget_coverage_report— readget_diagnostics— readget_feature_context— readget_index_health— readget_optimization_report— readget_outline— readget_preset_info— readget_project_map— readget_real_savings— readget_session_analytics— readget_session_stats— readget_symbol— readget_task_context— readget_usage_trends— readinvalidate_decision— write (state-changing)load_tools— unclassifiedmine_sessions— write (state-changing)plan_turn— readquery_decisions— readregister_edit— write (state-changing)remember_decision— unclassifiedsearch— readsearch_text— readsuggest_queries— read
handshake and tools listed without a recorded key or OAuth
Score 100/100 · Tools 29 · Token cost approx. 7,192 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 3.44.3 · Package trace-mcp · Repo nikolai-vysotskyi/trace-mcp
Summary: Trace MCP completed an MCP handshake without credentials and exposed 29 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 29
- Context cost
- approx. 7192 tokens, cl100k estimate (29 tools, measured 2026-11-18 UTC, version 3.44.3; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install trace-mcp --ignore-scripts (Node v24.22.1, Linux) succeeded in 14s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 29 tools listed in 9.8s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 204 GitHub stars. |
| docs | pass | 15 | README over 3,000 chars; install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 7192 tokens, cl100k estimate for 29 tools · about 88% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-18 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 29 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-18 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
c7ae06171cfc: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "trace-mcp",
"version": "3.44.3",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 29,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install trace-mcp --ignore-scripts` (Node v24.22.1, Linux) succeeded in 14s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 29 tools listed in 9.8s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 204 GitHub stars."
],
"docs": [
"pass",
15,
"README over 3,000 chars; install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
},
"testedAt": "2026-11-18T04:18:52.519Z"
}Install
npx -y trace-mcp
Pin the version we tested
npx -y --ignore-scripts trace-mcp@3.44.3
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"trace-mcp": {
"command": "npx",
"args": [
"-y",
"trace-mcp@3.44.3"
]
}
}
}Tools listed
get_index_health, register_edit, get_project_map, search, suggest_queries, get_symbol, get_outline, get_change_impact, get_context_bundle, get_feature_context, get_task_context, find_usages, get_call_graph, search_text, get_diagnostics, mine_sessions, remember_decision, query_decisions, invalidate_decision, get_preset_info, load_tools, get_session_analytics, get_optimization_report, get_coverage_report, get_real_savings, get_usage_trends, get_session_stats, plan_turn, batch
Quick config
{
"mcpServers": {
"trace-mcp": {
"command": "npx",
"args": [
"-y",
"trace-mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install trace-mcp --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-18 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (29 in our test).
{
"mcpServers": {
"trace-mcp": {
"command": "npx",
"args": [
"-y",
"trace-mcp"
]
}
}
}Test history
- 2026-11-18 UTC: New
Related: Best dev MCP servers
FAQ
Is Trace MCP deprecated?
No. Trace MCP was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces Trace MCP?
Nothing; Trace MCP is not deprecated as of 2026-11-18 UTC.
Does Trace MCP need an API key?
No. It completed an MCP handshake with no credentials and listed 29 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.