cryptbrew-mcp
OfficialRelated Servers
Alternatives to cryptbrew-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceExposes any OpenAPI spec endpoints as AI agent tools via stdio, requiring no code generation or maintenance.18MIT
- AlicenseBqualityBmaintenanceEnables AI clients to connect locally over stdio, discover and read schemas for native page tools, and execute user-authorized operations supplied by websites and independent user scripts.13MIT
- FlicenseBqualityBmaintenanceEnables AI agents to create and control persistent terminal sessions, run and monitor asynchronous jobs, page through ordered event history, and resolve registered device connection details without exposing stored secrets. Exposes 15 MCP tools over stdio that mirror a REST API, keeping session state alive independently of the agent that started it.15-

lsfusion-mcpofficial
FlicenseNot gradedqualityBmaintenanceEnables RAG-powered documentation search using OpenAI embeddings and Pinecone vector database. Provides an extensible framework for adding additional tools with support for both local STDIO and production HTTP transports.1-- AlicenseNot gradedqualityBmaintenanceProvides LLM clients with market intelligence tools over stdio, including market snapshots, price history, sentiment scoring, evidence search, and research briefs, with saved-run resource access.AGPL 3.0
- FlicenseBqualityCmaintenanceEnables an AI assistant to read and manage a local project-management database over stdio: listing and creating projects, tasks, expenses, chats and people, and pulling money, margin, deadline and overdue summaries. It runs on the same service layer and SQLite file as the bundled web UI, so figures shown to the assistant and to the human always agree.14-
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.