A
licenseA
qualityC
maintenanceServes the Pancake API documentation to AI assistants, enabling them to search endpoints, retrieve full API contracts, webhook payloads, and guides without live API access.
7
MIT
mcp-divineapi-docs
Related Servers
Alternatives to mcp-divineapi-docs
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceServes RootApp documentation files with search and retrieval capabilities, enabling users to access specific docs, browse directory structure, and search across file names and content.AGPL 3.0
- AlicenseAqualityCmaintenanceServes Neo-MoFox official documentation to MCP clients, enabling searching, listing, and reading docs via tools and resources.3MIT
- FlicenseAqualityCmaintenanceA read-only MCP server that exposes Automeli's public API documentation (v2 canonical, v1 frozen) to LLMs via fetch and cache over www.automeli.com artifacts. It enables listing, searching, and retrieving endpoints, OpenAPI specs, error explanations, code snippets, and end-to-end flow guides.7-
- AlicenseNot gradedqualityBmaintenanceRead-only, unauthenticated remote MCP server for public Wavedash docs, providing SDK guidance, engine setup help, and publishing checklists for agents.2MIT
- AlicenseBqualityDmaintenanceEnables searching and retrieving documentation files from a local docs folder using a search tool and dynamic resource URIs.1MIT
TDQS
A4.5/5.0
Scored across 5 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: get_endpoint returns reference cards, get_example returns example responses, get_playbook returns global rules, list_endpoints lists paths, and search_docs searches by keyword. There is no overlap or ambiguity.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with lowercase and underscores: get_endpoint, get_example, get_playbook, list_endpoints, search_docs. The naming is predictable and uniform.
Tool Count5/5
With 5 tools, the server is well-scoped for its purpose of serving API documentation. It provides essential functions for retrieving endpoint details, examples, listing, searching, and understanding rules without being excessive or insufficient.
Completeness5/5
The tool set covers all key documentation activities: listing endpoints, searching by keyword, retrieving detailed reference cards, accessing example responses, and obtaining usage rules. There are no obvious missing features for the domain.
Maintenance
ActivitySlowing
ResponsivenessNo issues