Cerell-mcp
Related Servers
Alternatives to Cerell-mcp
No user-submitted related servers found.
Related Servers
AlicenseBqualityAmaintenanceOfficial MCP server for accepting crypto payments through OrcaRail. It enables AI agents to create payment intents, manage subscriptions, handle product catalogs, and get exchange rates via natural language.26217 npmMIT- AlicenseNot gradedqualityDmaintenanceAn MCP server that gates content and tools behind x402 stablecoin micropayments with pluggable content and payment network adapters.MIT
- AlicenseAqualityCmaintenanceA template for building MCP servers with a built-in paywall gate that offers free local execution and premium server-side execution via Stripe and x402 payment lanes.1MIT
- AlicenseAqualityDmaintenanceThis MCP server assists Minecraft Java plugin developers by providing dependency documentation lookups, version checking, and automated scanning for Gradle and Maven projects. It supports popular APIs such as Paper, Spigot, and LuckPerms to streamline plugin development and workspace analysis.43MIT
- AlicenseAqualityAmaintenanceOfficial local MCP server for AllMCPs.com, enabling users to submit MCP servers to the directory directly from MCP-compatible agents.1387 npm4MIT
- AlicenseAqualityAmaintenanceOpen source MCP server for OpenProject aimed at community edition users59396 PyPI6MIT
TDQS
Scored across 1 tool
With only one tool, there is no cross-tool overlap or misselection risk. However, the single tool bundles many distinct operations (partners, stack, cashback, portal), so agents must disambiguate through parameters rather than tool choice.
There is only one tool name, so consistency cannot be meaningfully evaluated. The name 'infra' is broad and does not follow a verb_noun pattern, but it is readable.
The apparent scope spans partner provisioning, stack optimization, evolution, cashback, and portal operations. Collapsing all of that into one mega-tool is too thin for the domain and forces excessive reliance on parameter conventions.
The description mentions several major capability areas, suggesting broad coverage, but the surface lacks granular operations and clear CRUD/lifecycle boundaries. Agents may work around this with the detail/limit parameters, but specific workflows are opaque.