cryptbrew-mcp
OfficialRelated Servers
Alternatives to cryptbrew-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceServes a site's validated public profile, product list and newest-first posts to AI agents through three read-only tools (get_profile, list_products, list_posts) over stdio or any Web Request/Response runtime.7 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to integrate stablecoin crypto checkout into applications by registering workspaces, configuring settlement wallets and webhooks, creating payment links and invoices, and verifying payment status and webhook signatures. It exposes these payment operations as tools over stdio so agents can complete end-to-end payment setup without manual dashboard work.-
- FlicenseNot gradedqualityAmaintenanceEnables AI clients to query and retrieve current technical documentation for popular agent frameworks such as LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP, Camel-AI, and CrewAI through stdio or SSE.-
- AlicenseNot gradedqualityCmaintenanceExposes any OpenAPI spec endpoints as AI agent tools via stdio, requiring no code generation or maintenance.18MIT

@shieldlabs-ai/mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to read identification verdicts, search history, summarize entities, explain risk scores, and verify webhook signatures through read-only tools over stdio or streamable HTTP.6216 npmMIT
@klappay/mcpofficial
AlicenseNot gradedqualityAmaintenanceLets an AI assistant run locally over stdio to inspect and test the Klap Core API — looking up charges and timelines, listing webhooks and deliveries, checking accepted token/network pairs, querying metrics, and, in test mode, creating charges, re-checking them on-chain, retrying deliveries and driving sandbox payments. Live environments are read-only unless writes are explicitly opted into, and money-moving or endpoint-management operations are never exposed.195 npmMIT
TDQS
Scored across 8 tools
Most tools target a distinct informational topic, but cryptbrew_faq, cryptbrew_about, and cryptbrew_how_it_works overlap for general 'how does it work?' queries. The pricing vs. lock_info boundary is well handled, but the broad-faq catch-all remains a misselection risk.
All tools follow a predictable cryptbrew_<topic> snake_case pattern with no mixed conventions. Names are readable and consistently structured.
The set has 8 tools, which is well-scoped for a product-information server. Each major aspect has a dedicated tool without excessive granularity.
Covers pricing, links, mechanism, Lock app, FAQ, health, contact, and overview. Minor gaps exist for terms/legal details or deeper API reference beyond the links tool, but the core informational surface is solid.