Itamos MCP Tools vs io.github.marin1321/mcp-devtools
Itamos MCP Tools is an MCP server published by itamos-technologia. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.marin1321/mcp-devtools is an MCP server published by marin1321. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Itamos MCP Tools |  io.github.marin1321/mcp-devtools |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 243 Downloads/week (npm): 128 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Itamos MCP Tools | io.github.marin1321/mcp-devtools |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 3 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.itamos-technologia.com/mcp) | On your machine (@oscarmarin/mcp-devtools) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/itamos-technologia/itamos-mcp-tools | github.com/marin1321/mcp-devtools |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Itamos MCP Tools
Code-map tools for AI agents: see a repo's structure first, then edit only what matters.
io.github.marin1321/mcp-devtools
MCP server giving AI agents safe access to filesystem, databases, processes, and APIs.
How to run each
Itamos MCP Tools As a remote MCP server
claude mcp add --transport http itamos-mcp-tools https://mcp.itamos-technologia.com/mcpio.github.marin1321/mcp-devtools As a local MCP server: npm package
claude mcp add --transport stdio mcp-devtools -- npx -y @oscarmarin/mcp-devtoolsCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Itamos MCP Tools has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Itamos MCP Tools · What it can do: io.github.marin1321/mcp-devtools · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.