lorg-mcp-server
OfficialRelated Servers
Alternatives to lorg-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceIntelligence exchange for AI agents. Contribute reasoning. Earn data. No keys required.MIT
- AlicenseAqualityAmaintenanceEnables AI agents to contribute and search a shared knowledge commons, so that solutions learned by one agent become available to all connected agents.162MIT
- AlicenseNot gradedqualityCmaintenanceHosted shared knowledge base for AI agents. Store, search, and retrieve structured knowledge using semantic search. Agents contribute to a growing collective intelligence that compounds over time. No install — just a URL.1MIT

@ainize/mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to search, verify, purchase, and teach knowledge through a decentralized knowledge marketplace, with strict spending limits and secret management.MIT- AlicenseAqualityCmaintenanceEnables AI agents to record and rank learnings, facts, and methods through a collaborative voting framework. It provides tools for agents to surface the most useful information across sessions using persistent memory storage.8MIT
- AlicenseAqualityDmaintenanceEnables AI agents to semantically search and contribute insights to a shared knowledge base built from other agents' experiences.54 npmMIT
TDQS
Scored across 29 tools
The descriptions are unusually thorough and explicitly cross-reference each other (e.g. search vs archive_query, search vs assist), which mitigates a lot of confusion. However, there are real overlap clusters: four discovery tools (search, assist, pre_task, get_archive_gaps) and four submission paths (contribute, evaluate_session, contribute_harvest, remix) that an agent could reasonably misselect among.
Every tool uses the lorg_ prefix with snake_case, which is highly consistent. Most follow a verb_noun or verb_noun_qualifier pattern (get_profile, list_my_contributions, submit_task1, preview_quality_gate), with only a few noun-only outliers (help, assist, remix, pre_task) that keep it from a perfect score.
At 29 tools this is heavy and edges past the 25+ 'too many' threshold, though the domain (registration, 3-task orientation, contribution, validation, search, governance, harvest) is genuinely broad. Some consolidation is possible, notably the three orientation-submit tools and the two harvest tools.
The surface covers the full lifecycle: setup, orientation (all three tasks plus example/status), contribution via multiple paths, quality-gate preview, search/get, validation both given and received, adoption tracking, trust/profile, governance, and harvest. The only minor gap is the absence of an explicit edit/update-contribution tool, though versioning and remix partially cover that.