Wisdom MCP
Related Servers
Alternatives to Wisdom MCP
No user-submitted related servers found.
Related Servers
AlicenseAqualityCmaintenanceMCP server for NaN Mesh, enabling AI agents to search entities, cast trust reviews, register agents, post content, and query trust scores from the AI trust network.31271 npm1MIT- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
- AlicenseAqualityFmaintenanceMCP server that gives AI agents Lightning payments, L402 API access, trust verification, and service discovery.116 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI agents a continual learning brain with lessons, skills, memories, evidence-based refinement, rollback, and hybrid GraphRAG retrieval.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.25 npmMIT
TDQS
Scored across 41 tools
Most tools map to distinct resources, but startup/context tools (whoami, quickstart, load_context_for_task) and fragment-creation tools (create_fragment, transform_to_fragment, store_transformed_fragments) overlap enough to cause misselection. Descriptions help clarify, but the boundaries are somewhat blurry.
All tools share the wisdom_ prefix and nearly all follow a verb_noun pattern, such as create_tag, get_fragment, and list_projects. The bare-verb exceptions like whoami, quickstart, and configure are minor deviations in an otherwise consistent scheme.
At 41 tools, the surface is too large for a single MCP server, spanning setup, fragments, tags, relations, projects, agents, trust, and transforms. Many tools could be consolidated or split into focused sub-servers to reduce selection burden.
The server covers core knowledge capture, retrieval, trust, and transformation workflows well. However, there is no way to delete relationships, tags, or projects, and no removal counterpart to tag_fragment or link_answer, leaving notable gaps in lifecycle management.