santismm-knowledge
OfficialRelated Servers
Alternatives to santismm-knowledge
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server that exposes the knowledge base of the Cumplimiento Digital project, allowing AI agents to query KB entries, project status, endpoints, and glossary via MCP tools.-
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to query a structured knowledge library for search, explanations, related concepts, learning paths, examples, and cross-domain references via MCP.Apache 2.0
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents and users to search a unified organizational knowledge warehouse, create and iterate on documents, manage folders and reviews, and curate shareable knowledge packs through any compatible MCP client.-
- AlicenseNot gradedqualityCmaintenanceProvides enterprise knowledge management capabilities via MCP, enabling semantic search across the knowledge base, retrieval of full documents by ID, and search over enterprise project cases.MIT
- AlicenseNot gradedqualityBmaintenanceGoverned knowledge base for AI agents via the Model Context Protocol (MCP), enabling agents to search, read, and contribute persisted knowledge with versioning, audit trails, and approval workflows.80MIT
TDQS
Scored across 30 tools
The list_/get_ pairs for each content type are clearly separated, and the calculate_* tools are unambiguous. The main overlap is among search, search_all, and search_articles: search_all intentionally supersets the others, and while the descriptions clarify the scopes, an agent could still hesitate over which search to call first.
The tool set strongly follows a verb_noun snake_case pattern with consistent list_/, get_/, search_/, and calculate_/ prefixes. Minor deviations such as bare search, search_all, get_related, and the singular get_homeric_place versus plural list_homeric_places prevent a perfect score.
Thirty tools is high for a typical MCP server, but this one explicitly spans multiple surfaces: core knowledge, articles, labs, the Homeric Atlas, and the claim registry. Each surface has dedicated list/get tools plus specialized search and calculation tools, so the count feels purposeful rather than bloated.
The tool set provides full read-side coverage: discovery via get_overview and list_* tools, retrieval via get_* tools, cross-surface discovery via search and search_all, graph traversal via get_related, and specialized calculators. For a read-only knowledge server, create/update/delete tools are not expected, and every described surface is reachable.