Hotline Finance FAQ MCP Server
Related Servers
Alternatives to Hotline Finance FAQ MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for a content-first knowledge base, enabling AI agents to search (full-text, semantic, hybrid) and retrieve Markdown documents, list content, and find related docs.-
- AlicenseAqualityBmaintenanceEnables Claude-compatible clients to search a bundled help center with pagination, draft validated support tickets, read documentation resources as Markdown, and use a reusable documentation-explanation prompt. It can run over stdio or streamable HTTP and serves as a configurable starting point for custom MCP servers.2MIT
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1162MIT
- FlicenseNot gradedqualityDmaintenanceMCP server enabling Claude Desktop to answer questions from local Word and PDF documents by searching a vector index built from their contents.-
- FlicenseNot gradedqualityAmaintenanceThis MCP server enables AI clients to search and retrieve up-to-date technical documentation for supported agent frameworks, including LangChain, LlamaIndex, AutoGen, Agno, OpenAI Agents SDK, MCP docs, Camel AI, and CrewAI. It supports both stdio and SSE transports.-
- AlicenseNot gradedqualityDmaintenanceGeneric MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.MIT
TDQS
Scored across 5 tools
The tools have distinct purposes: listing categories, getting questions by category, getting a glossary item, free-text search, and an interactive wizard. There is some overlap among get_faq_questions, find_faq, and faq_wizard, but descriptions clarify their different input modes.
Most tools follow a verb_noun pattern (list_faq_categories, get_faq_questions, get_glossary_item, find_faq), but faq_wizard deviates by using a noun-only name, breaking the otherwise consistent pattern.
With 5 tools, the server is well-scoped for an FAQ and glossary service. Each tool serves a clear and non-redundant role, and the count feels appropriate.
Core FAQ browsing and glossary lookup are covered, but there is a notable gap: get_glossary_item references a get_glossary_list tool that is not present in the set. This creates a dead end for discovering glossary terms.