m-dev-tools
PYPI · M-DEV-TOOLS-MCP · SCANNED SEP 20
MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0).Pass
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 210 tokens (~70/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the m-dev-tools MCP server?
m-dev-tools runs locally as a PyPI package, launched with uvx m-dev-tools-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · m-dev-tools-mcp
claude mcp add m-dev-tools-m-dev-tools-mcp -- uvx m-dev-tools-mcp
{
"mcpServers": {
"m-dev-tools-m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
} {
"servers": {
"m-dev-tools-m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
} codex mcp add m-dev-tools-m-dev-tools-mcp -- uvx m-dev-tools-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"m-dev-tools-m-dev-tools-mcp": {
"type": "local",
"command": [
"uvx",
"m-dev-tools-mcp"
],
"enabled": true
}
}
} openclaw mcp add m-dev-tools-m-dev-tools-mcp --command uvx --arg m-dev-tools-mcp
mcp_servers:
m-dev-tools-m-dev-tools-mcp:
command: "uvx"
args: ["m-dev-tools-mcp"] {
"McpServers": {
"m-dev-tools-m-dev-tools-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"m-dev-tools-mcp"
]
}
}
} assistant mcp add m-dev-tools-m-dev-tools-mcp -t stdio -c uvx -a m-dev-tools-mcp
{
"mcpServers": {
"m-dev-tools-m-dev-tools-mcp": {
"command": "uvx",
"args": [
"m-dev-tools-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 +12
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.80 functional
- 11 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/m-dev-tools-mcp@0.2.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 29 packages
| Packages resolved | 29 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
describe ~77
Return a pointer-blob for a typed ID. Supported kinds: ``tool:`` / ``module:`` / ``cmd:`` / ``recipe:``. Does not inline payloads — returns URLs the caller should fetch next, keeping the catalog's "pointers, not facts" invariant.
| Name | Type | Req | Description |
|---|---|---|---|
| typed_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
route_intent ~71
Return typed IDs matching the plain-English intent. Example: ``route_intent("parse JSON in M")`` returns ``["module:m-stdlib#STDJSON"]``. Results are ``[primary, *see_also]`` from the matched task_index row.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
verify ~62
List the ``verification_commands`` declared in a repo's ``repo.meta.json``. Accepts either a bare repo slug (``m-cli``) or a typed ID (``tool:m-cli``). Does NOT execute the commands.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
What is the m-dev-tools MCP server?
m-dev-tools is an MCP server listed in the public MCP registry as io.github.m-dev-tools/m-dev-tools-mcp. MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify. This page covers its PyPI package (m-dev-tools-mcp).
Is the m-dev-tools MCP server safe to use?
m-dev-tools scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the m-dev-tools MCP server expose?
m-dev-tools exposes 3 tools: route_intent, describe, verify. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Is the m-dev-tools MCP server still maintained?
m-dev-tools is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the m-dev-tools MCP server under?
m-dev-tools declares the AGPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.