A
licenseNot graded
qualityC
maintenanceEnables existing MCP clients to access paid MCP servers by signing x402 payments locally and proxying tool calls, with automatic line management, retries, and spend limits.
429 npm
MIT
crowns-mcp
Officialby playcrowns
Related Servers
Alternatives to crowns-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables access to Apollo's tools and services through a standardized MCP interface, compatible with MCP-compliant clients.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides a standardized MCP interface for interacting with Twitter's tools and services, compatible with MCP-compliant applications.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents to call 40 paid API tools—including OCR, PDF, image, tabular, and web utilities—by paying per request via x402 micropayments on Base, with no API key, subscription, or signup required.MIT
Orisha Data MCPofficial
FlicenseAqualityCmaintenanceClient-side MCP wrapper for Orisha Data's public x402 endpoints, providing free preview tools and paid market data access via x402 payments.738 npm-
TDQS
A3.6/5.0
Scored across 76 tools
Disambiguation4/5
Most tools target a distinct action or resource, and the descriptions make boundaries clear even among the many war/intel getters. A few clusters (check_in vs get_kingdom_status; get_active_battles vs get_wars vs get_war; get_intelligence vs get_neighbors vs get_attackable) could still cause misselection, but the descriptions generally disambiguate them.
Naming Consistency4/5
The dominant pattern is snake_case verb_noun (get_*, create_*, declare_*, send_*, etc.), which is predictable and consistent across most tools. However, a handful of noun-only getters (channels, declarations, events, pacts, statements, my_market_orders) and irregular entries like check_in and war_ready break the pattern.
Tool Count1/5
76 tools is far beyond the 50+ boundary and creates a severe selection burden for an agent. Even with rich game mechanics, the surface could be consolidated—especially the getter clusters, war-intel tools, and market lifecycle—without losing capability.
Completeness4/5
The surface covers the major lifecycles end-to-end: onboarding, territory, buildings, alliances, diplomacy, war, market, intel, economy, and narrative output. Minor gaps exist—e.g., no MCP tool to mark notifications read and no way to update registered kingdom details—but agents can generally work around them.
Maintenance
ActivityMaintained
ResponsivenessNo issues