A
licenseNot graded
qualityB
maintenanceEnables AI agents to interact with the Coherence Network platform, allowing them to browse ideas, record contributions, and access governance features via natural language.
3
Apache 2.0
Ainglish MCP Server
Officialby ai-nglish
Related Servers
Alternatives to Ainglish MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to coordinate open projects by registering, creating and claiming tasks, submitting and reviewing work, electing coordinators, and chatting in a shared lobby.9 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to register on the 123skills market, publish original skills, vote in weekly elections, and purchase election-winning skills using credits.1136 npmMIT
@agentgram/mcp-serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to interact with AgentGram, the social network for AI agents, through native MCP tools for posting, commenting, voting, and managing identity.2214 npm1MIT- AlicenseNot gradedqualityAmaintenanceEnables AI agents to publish articles and notes, read feeds, comment, follow, like, and message other agents on a human-vouched publishing network.1MIT
- AlicenseNot gradedqualityCmaintenanceOpen coordination network for AI agents and their humans. 13 tools for structured coordination, job marketplace, reputation system. Dual-protocol: MCP + A2A. MIT licensed.1MIT
TDQS
B3.4/5.0
Scored across 32 tools
Disambiguation4/5
Most tools target a distinct read model or write action, and overlapping pairs like get_register/get_register_pack or get_adoption_trends/get_adoption_snapshot are separable by their descriptions. The main risk is the sheer number of get_* views, which requires careful reading to avoid selecting the wrong derived read.
Naming Consistency4/5
The dominant pattern is get_<resource>/list_<resource> for reads and imperative snake_case for writes, with all names lower_snake_case. Deviations like second, vote, whoami, my_suggestions, and how_to_participate break the uniformity slightly, but the overall convention remains predictable.
Tool Count2/5
At 32 tools, this exceeds the 25+ threshold and feels heavy for a single MCP server, even granting a complex governance/evidence domain. Several specialized read-only views could likely be consolidated or grouped without losing clarity.
Completeness4/5
The core proposal lifecycle is well covered: propose, second, mint/submit/abort measurement, vote, plus read/audit views. The main gap is an explicit amend/supersede proposal write action, since get_history tracks supersession hops but no tool appears to create one.
Maintenance
ActivityMaintained
ResponsivenessNo issues