MCP Scorecard

Mission StatementGitHub
← All posts

The Suite Explosion: When One Publisher Registers 33 Servers

Seven publishers in this batch registered five or more servers each, collectively accounting for 118 entries. rog0x brought 33 utility servers, junct-bot brought 24 DeFi protocols, and ansvar added 21 more countries. The registry is becoming a place where a single namespace can dominate by volume.
io.github.rog0xio.github.junct-boteu.ansvario.github.markswendsen-codeio.github.ofershapio.github.lordbasilaiassistant-sudoio.github.nick-ma

The largest servers-per-publisher ratio in this batch is 33 to 1. A single namespace — io.github.rog0x — registered 33 MCP servers in one go. They cover generic development utilities: file operations, git, JSON, regex, testing, crypto, Docker, database, logging, math, string manipulation, and more. All score 40. All follow the same template.

This is not an anomaly. It is a pattern that defined this batch.

The Suite Publishers

PublisherServersScore RangeDomain
rog0x3340Generic dev utilities
junct-bot2430DeFi protocol bridges
ansvar (new)2149–53Country-specific law
markswendsen-code1640SaaS integrations (DoorDash, etc.)
ofershap14Mixed
lordbasilaiassistant-sudo13Mixed
nick-ma1238UK Parliament APIs

Together, these seven publishers account for 133 servers — nearly 10% of the entire batch from just seven namespaces.

The DeFi Suite

junct-bot is particularly notable. Twenty-four servers, each wrapping a specific DeFi protocol: Uniswap, Aave, Compound, Lido, MakerDAO, Synthetix, Curve, GMX, Hyperliquid, Jupiter, Stargate, Wormhole, and more. All score 30 — Very Low Trust. No packages, minimal repo signals.

But the coverage is interesting. An agent with access to all 24 junct-bot servers could theoretically query liquidity pools across multiple chains, check lending rates on Aave and Compound, monitor staking yields on Lido and Eigenlayer, and route trades through Jupiter and Uniswap — all through MCP tool calls. This is the agent-native DeFi dashboard that crypto has been talking about for two years, built as 24 low-trust MCP servers by a single developer.

The Ansvar Update

Ansvar — the one-man legal database we profiled on February 23 when it had 70 countries — added 21 more. The namespace now covers 97 jurisdictions. New additions include Bahrain, Botswana, Cambodia, Cameroon, Dominican Republic, Ecuador, Ethiopia, Jordan, Malawi, Mozambique, Namibia, Nepal, Paraguay, Russia, Senegal, Sri Lanka, Tanzania, Tunisia, Uganda, and Zambia. At this rate, Ansvar will have every UN member state covered within months.

The Quality Question

Suite publishing creates a tension in the registry. Volume is not quality. A namespace with 33 servers at score 40 contributes noise — diluting search results, inflating publisher counts, and dragging down the average trust score. The median new server in this batch scored 37. Half of all new entries are Very Low Trust.

But suites also represent genuine ambition. junct-bot’s DeFi coverage is comprehensive. Ansvar’s legal database is unique. The UK Parliament suite wraps real government APIs. The registry’s job is to distinguish between these cases — score them honestly, flag the low-signal entries, and let users decide. The suite explosion is a feature of open registries, not a bug. The scoring system exists precisely for moments like this.

← Godot Gets Four MCP Servers: Game Engine AI Tooling ExpandsTwelve MCP Servers for the UK Parliament: Every Public API, One Developer →