No user-submitted related servers found.
Scored across 15 tools
Several pairs have blurred boundaries: catalog.search vs catalog.find (browse vs decide), catalog.call vs route_and_execute (internal catalog vs external x402 sellers), and payment.info vs server.describe (both meta/info with overlapping install guidance). Descriptions do draw the distinctions explicitly, which rescues most selections, but an agent could easily misroute between the two routing tools. web.search/web.news/web.answer are genuinely distinct.
Thirteen of fifteen tools follow a clean dotted namespace_verb convention (memory.read, catalog.search, web.search, browser.render, market.quote, audio.transcribe, sellers.list). The lone flat snake_case outlier, route_and_execute, is also the one tool whose function most resembles others, which makes the inconsistency slightly more costly than a cosmetic one.
Fifteen tools is at the top of the healthy band but still reasonable for a gateway spanning memory, search, rendering, finance, audio, payments, and external routing. Two largely informational tools (server.describe, payment.info) feel like padding against a 628-tool catalog already reachable via catalog.call, so there is mild redundancy.
The flagship surface leans heavily on catalog.call as an escape hatch: descriptions repeatedly reference extract, screenshot, search-lite, multi-search, stock-history, crypto-price, memory-recall and memory-remember, none of which are exposed as first-class tools. Memory also has no dedicated delete (folded into memory.write via delete:true), so lifecycle coverage is workable but indirect.
