MCP.Market

m-dev-tools MCP server

by m-dev-tools·io.github.m-dev-tools/m-dev-tools-mcp·v0.2.4

MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
New

0 stars14 downloads/wk

Reviews

Write one

Nobody has reviewed m-dev-tools yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

m-dev-tools tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • _build_parser
  • describe

    Return a pointer-blob for a typed ID.

  • route_intent

    Return typed IDs matching the plain-English intent.

  • verify

    List the ``verification_commands`` declared in a repo's ``repo.meta.json``.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan4 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 55 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How m-dev-tools compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
14
more than 4% of 12,191 servers with a package

What its tools let an agent do: 4 read

Install m-dev-tools in Claude Code, Cursor or VS Code

claude mcp add m-dev-tools-mcp -- uvx m-dev-tools-mcp
Add to Cursor

What the publisher says

From the m-dev-tools repository's README, as published. We do not edit it. Read it on GitHub

m-dev-tools-mcp

MCP server for the m-dev-tools org catalog. Exposes three first-class agent tools:

  • routeintent(query)** — plain-English intent → typed IDs (e.g. "parse JSON in M" → module:m-stdlib#STDJSON)
  • describe(typedid)** — typed ID → pointer-blob (manifest URL, AGENTS.md URL, verification commands, …)
  • verify(repo) — list a repo's declared verification commands (does not execute them)

The server reads the catalog at over the network at call time; it is a thin wrapper, not a cache. See AGENTS.md for the contract and the AI users guide for the full walk-through.

<!-- Required by registry.modelcontextprotocol.io for PyPI ownership validation. Do not remove. --> mcp-name: io.github.m-dev-tools/m-dev-tools-mcp

Install

pip install m-dev-tools-mcp
# or:
uvx m-dev-tools-mcp
# or from a GitHub Release wheel:
pip install https://github.com/m-dev-tools/m-dev-tools-mcp/releases/download/v0.2.4/m_dev_tools_mcp-0.2.4-py3-none-any.whl

Point any MCP client at the m-dev-tools-mcp binary the install provides:

{
  "mcpServers": {
    "m-dev-tools": { "command": "m-dev-tools-mcp" }
  }
}

Or for clients that consult the public MCP registry:

io.github.m-dev-tools/m-dev-tools-mcp

Develop

make install        # creates .venv and installs editable + dev deps
make test           # pytest
make check          # lint + mypy + test + check-manifest + check-agents
make build          # → wheel-out/m_dev_tools_mcp-<ver>-py3-none-any.whl

More

  • Architecture: m-dev-tools/.github's docs/ai-discoverability/AI-discoverability-architecture.md
  • Plan + phases: docs/ai-discoverability/phases/
  • Release process: tag vX.Y.Z on main → .github/workflows/release.yml builds the wheel, attaches it to a GitHub Release, publishes to PyPI via Trusted Publisher OIDC, and updates the MCP registry record via GitHub OIDC.

License

AGPL-3.0. Same license as every other m-dev-tools repo.

Nothing above is checked by us. What we check is on the safety report.

m-dev-tools: common questions

Is m-dev-tools MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the m-dev-tools safety report
How do I install m-dev-tools?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does m-dev-tools need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is m-dev-tools maintained?
The last commit was 93 days ago (2026-08-03). The latest release is v0.2.4.
How does m-dev-tools compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.