MCP Dev Tools (procedures)
Capped at 70: no passing tool call yet; the tests add up to 100. Why scores are capped
Test points add up to 100; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (100/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs15/15
- License10/10
Tested npm @procedures/mcp-dev-tools 0.63.0 (MIT; repo mark1russell7/client). Installed pinned with scripts off (npm --ignore-scripts) and launched: initialize and tools/list over stdio succeeded with no credentials and listed 94 tools (84 annotated by the server: 50 read-only, 22 destructive). Real calls: 0 of 1 real function calls passed. The one call returned the text 'undefined'. Core tools not tested: 70 cap.
Tool-call test (2026-11-18 UTC, direct MCP stdio client, no LLM): fail. 0 of 1 real function calls passed. The one call returned the text 'undefined'. Evidence: local test run, Nov 18, 2026 UTC.
Transport (tested 2026-11-18 UTC): stdio
Token cost (estimate): approx. 12148 tokens, cl100k estimate (94 tools, measured 2026-11-18 UTC, version 0.63.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 21 read, 22 write (state-changing), 51 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
client.all— unclassifiedclient.and— unclassifiedclient.any— unclassifiedclient.chain— unclassifiedclient.conditional— unclassifiedclient.constant— unclassifiedclient.identity— unclassifiedclient.map— unclassifiedclient.none— unclassifiedclient.not— unclassifiedclient.or— unclassifiedclient.parallel— unclassifiedclient.reduce— unclassifiedclient.throw— unclassifiedclient.trace— unclassifiedclient.tryCatch— unclassifiedcue.add— write (state-changing)cue.generate— unclassifiedcue.init— unclassifiedcue.remove— write (state-changing)cue.validate— unclassifieddocker.build— unclassifieddocker.compose.build— unclassifieddocker.compose.down— unclassifieddocker.compose.logs— unclassifieddocker.compose.ps— unclassifieddocker.compose.restart— write (state-changing)docker.compose.up— unclassifieddocker.exec— unclassifieddocker.images— unclassifieddocker.inspect— readdocker.logs— unclassifieddocker.network.create— write (state-changing)docker.network.list— readdocker.network.remove— write (state-changing)docker.ps— unclassifieddocker.pull— unclassifieddocker.rm— write (state-changing)docker.run— unclassifieddocker.stop— write (state-changing)docker.tag— write (state-changing)docker.volume.create— write (state-changing)docker.volume.list— readjson.diff— readjson.merge— write (state-changing)json.patch— write (state-changing)json.query— unclassifiedjson.validate— unclassifiedlib.audit— unclassifiedlib.graph— unclassifiedlib.importCycles— unclassifiedlib.new— write (state-changing)lib.rename— write (state-changing)lib.scan— readlogs.query— unclassifiedlogs.store— unclassifiedmongo.collections.create— write (state-changing)mongo.collections.drop— write (state-changing)mongo.collections.list— readmongo.collections.stats— readmongo.database.info— readmongo.database.ping— unclassifiedmongo.documents.aggregate— readmongo.documents.count— readmongo.documents.delete— write (state-changing)mongo.documents.distinct— unclassifiedmongo.documents.explain— readmongo.documents.find— readmongo.documents.get— readmongo.documents.insert— write (state-changing)mongo.documents.update— write (state-changing)mongo.indexes.create— write (state-changing)mongo.indexes.drop— write (state-changing)mongo.indexes.list— readprocedure.define— unclassifiedprocedure.delete— write (state-changing)procedure.export— unclassifiedprocedure.get— readprocedure.list— readprocedure.manifest— unclassifiedprocedure.new— unclassifiedprocedure.search— readprogram.check— unclassifiedprogram.compile— unclassifiedprogram.diagram— unclassifiedprogram.explain— readsqlite.execute— write (state-changing)sqlite.query— readsqlite.schema— readsqlite.tables— readvitest.coverage— unclassifiedvitest.run— unclassifiedyaml.parse— unclassifiedyaml.stringify— unclassified
handshake and tools listed without a recorded key or OAuth
Score 70/100 · Tools 94 · Token cost approx. 12,148 tokens · Compare · Last tested 2026-11-18 UTC · Version tested 0.63.0 · Package @procedures/mcp-dev-tools · Repo mark1russell7/client
Summary: MCP Dev Tools (procedures) completed an MCP handshake without credentials and exposed 94 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 94
- Context cost
- approx. 12148 tokens, cl100k estimate (94 tools, measured 2026-11-18 UTC, version 0.63.0; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-18 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install @procedures/mcp-dev-tools --ignore-scripts (Node v24.22.1, Linux) succeeded in 5s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 94 tools listed in 4.0s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 0 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. 12148 tokens, cl100k estimate for 94 tools · about 148% 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 94 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)
ecd91e996ea8: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "@procedures/mcp-dev-tools",
"version": "0.63.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-18",
"tools_count": 94,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install @procedures/mcp-dev-tools --ignore-scripts` (Node v24.22.1, Linux) succeeded in 5s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 94 tools listed in 4.0s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 0 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:19:08.771Z"
}Install
npx -y @procedures/mcp-dev-tools
Pin the version we tested
npx -y --ignore-scripts @procedures/mcp-dev-tools@0.63.0
tested 2026-11-18 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"mcp-dev-tools-procedures": {
"command": "npx",
"args": [
"-y",
"@procedures/mcp-dev-tools@0.63.0"
]
}
}
}Tools listed
Showing 40 of 94 names: client.chain, client.trace, client.parallel, client.conditional, client.and, client.or, client.not, client.all, client.any, client.none, client.map, client.reduce, client.identity, client.constant, client.throw, client.tryCatch, procedure.define, procedure.get, procedure.list, procedure.manifest, procedure.search, procedure.delete, lib.scan, lib.rename, lib.new, lib.audit, lib.graph, lib.importCycles, procedure.new, procedure.export, program.check, program.compile, program.diagram, program.explain, json.query, json.patch, json.diff, json.merge, json.validate, yaml.parse.Show all 94 names
client.chain, client.trace, client.parallel, client.conditional, client.and, client.or, client.not, client.all, client.any, client.none, client.map, client.reduce, client.identity, client.constant, client.throw, client.tryCatch, procedure.define, procedure.get, procedure.list, procedure.manifest, procedure.search, procedure.delete, lib.scan, lib.rename, lib.new, lib.audit, lib.graph, lib.importCycles, procedure.new, procedure.export, program.check, program.compile, program.diagram, program.explain, json.query, json.patch, json.diff, json.merge, json.validate, yaml.parse, yaml.stringify, cue.init, cue.add, cue.remove, cue.generate, cue.validate, docker.run, docker.build, docker.pull, docker.exec, docker.stop, docker.rm, docker.ps, docker.logs, docker.compose.up, docker.compose.down, docker.compose.ps, docker.compose.logs, docker.compose.build, docker.compose.restart, docker.images, docker.inspect, docker.volume.list, docker.volume.create, docker.network.list, docker.network.create, docker.network.remove, docker.tag, mongo.database.ping, mongo.database.info, mongo.collections.list, mongo.collections.create, mongo.collections.drop, mongo.collections.stats, mongo.documents.find, mongo.documents.get, mongo.documents.insert, mongo.documents.update, mongo.documents.delete, mongo.documents.count, mongo.documents.aggregate, mongo.documents.distinct, mongo.documents.explain, mongo.indexes.list, mongo.indexes.create, mongo.indexes.drop, sqlite.query, sqlite.execute, sqlite.tables, sqlite.schema, logs.store, logs.query, vitest.run, vitest.coverage
Quick config
{
"mcpServers": {
"mcp-dev-tools-procedures": {
"command": "npx",
"args": [
"-y",
"@procedures/mcp-dev-tools"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install @procedures/mcp-dev-tools --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 (94 in our test).
{
"mcpServers": {
"mcp-dev-tools-procedures": {
"command": "npx",
"args": [
"-y",
"@procedures/mcp-dev-tools"
]
}
}
}Test history
- 2026-11-18 UTC: New
FAQ
Is MCP Dev Tools (procedures) deprecated?
No. MCP Dev Tools (procedures) was not deprecated or archived when we last tested it on 2026-11-18 UTC.
What replaces MCP Dev Tools (procedures)?
Nothing; MCP Dev Tools (procedures) is not deprecated as of 2026-11-18 UTC.
Does MCP Dev Tools (procedures) need an API key?
No. It completed an MCP handshake with no credentials and listed 94 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.