{
  "markdown": "# mcp-crates\n\nCrates.io MCP — wraps the crates.io REST API v1 (free, no auth)\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `search_crates` | Search crates.io for Rust packages by keyword. Returns crate name, description, downloads, latest version, and repo URL. |\n| `get_crate` | Get full metadata for a specific crate (e.g., 'serde'). Returns description, downloads, latest version, repo, homepage, and categories. |\n| `get_versions` | List all published versions for a crate in reverse chronological order. Returns version number, download count, and publish date. |\n| `get_crate_dependencies` | List the dependencies of a specific crate version — what <crate> itself depends on. Returns each dependency with its version requirement, kind (normal/build/dev), optional flag, enabled features, and target. Version is optional (defaults to the latest stable). Use for \"what does <crate> depend on\", dependency audits, or sizing a crate's footprint. |\n| `get_crate_reverse_deps` | List crates that DEPEND ON a given crate (reverse dependencies), most-downloaded first — answers \"what uses <crate>\", \"how widely adopted is <crate>\", \"who depends on <crate>\". Returns the total dependent count plus the top dependents with their version requirement, dependency kind, and download counts. |\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"crates\": {\n      \"url\": \"https://gateway.pipeworx.io/crates/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/crates/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Crates data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3432,
  "sha": "f0d22e9061be7739cb654402694c3e14cd07af7c6d4488d962e373de7b5442bf",
  "repo_slug": "pipeworx-io/mcp-crates",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_crates_aadecda6/readme"
}