Ext Ops Panel
Open dashboard
Comparison

io.github.achilliesbot/agentiam-mcp vs agentverse

io.github.achilliesbot/agentiam-mcp is an MCP server published by achilliesbot. Marketplaces we read that list it: 1 (Official MCP Registry). agentverse is an MCP server published by doc2mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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

Where each is published
Marketplaceio.github.achilliesbot/agentiam-mcpagentverse
Official MCP Registry Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1781779784
Forks (GitHub): 2
Stars (GitHub): 6
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

io.github.achilliesbot/agentiam-mcp vs agentverse
Factio.github.achilliesbot/agentiam-mcpagentverse
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)6 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Not statedRemote server (doc2mcp.site/api/mcp/353ba712-2c3b-4699-9c58-0dc4e54ff4eb/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/achilliesbot/agentiam-mcpgithub.com/doc2mcp/doc2mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 308 (46 h ago)

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

io.github.achilliesbot/agentiam-mcp

In its own words, on Official MCP Registry:

Stdio MCP wrapper for AgentIAM's 18 x402 endpoints — agent safety + intelligence on Base.

agentverse

In its own words, on Official MCP Registry:

MCP server for agentverse documentation, generated by doc2mcp.

How to run each

io.github.achilliesbot/agentiam-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

agentverse As a remote MCP server

Claude Code
claude mcp add --transport http agentverse https://doc2mcp.site/api/mcp/353ba712-2c3b-4699-9c58-0dc4e54ff4eb/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only agentverse 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: io.github.achilliesbot/agentiam-mcp · What it can do: agentverse · 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.

Where the data comes from: how the catalog is built