F
licenseB
qualityD
maintenanceEnables web page scraping via Jina reader API and searching FastMCP documentation using minsearch. Supports fetching markdown content from URLs and querying indexed documentation files.
3
-
FastMCP Documentation Search Server
Related Servers
Alternatives to FastMCP Documentation Search Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch, index, and perform semantic RAG-based searches on API documentation from various sources. It provides tools for hybrid search and collection management, allowing users to access up-to-date documentation from projects like Gemini and FastMCP.-
- FlicenseNot gradedqualityCmaintenanceEnables querying local documents via retrieval-augmented generation, along with current UTC datetime and safe arithmetic evaluation through MCP tools over HTTP.-
- AlicenseAqualityCmaintenanceEnables searching and browsing the entire F5 AI Security documentation using TF-IDF search and section reader tools.2Apache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides a versatile set of utility tools for LLMs, including text processing, web fetching, and search capabilities, all accessible via MCP.-
- FlicenseNot gradedqualityBmaintenanceEnables document Q&A, summarization, keyword extraction, and Wikipedia lookup through MCP tools, using RAG with FAISS and Ollama.-
TDQS
B3.1/5.0
Scored across 4 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: add performs arithmetic, hash_text handles cryptographic hashing, scrape_page extracts web content, and search_docs searches documentation. The functions are so different that misselection is highly unlikely.
Naming Consistency2/5
The naming is inconsistent with mixed conventions: add uses a simple verb, hash_text uses verb_noun, scrape_page uses verb_noun, and search_docs uses verb_noun. There is no uniform pattern, and the single-word 'add' deviates significantly from the others.
Tool Count3/5
With 4 tools, the count is borderline for the server's stated purpose of 'Documentation Search Server'—only one tool directly supports this, while others are unrelated utilities. This feels thin and misaligned with the domain, though not extreme.
Completeness2/5
For a documentation search server, there is a significant gap: only search_docs directly serves the purpose, while add, hash_text, and scrape_page are unrelated. This lacks coverage for typical documentation workflows like browsing, filtering, or managing documentation, likely causing agent failures.
Maintenance
ActivityInactive
ResponsivenessNo issues