A
licenseNot graded
qualityA
maintenanceA lightweight, self-hostable MCP server for shared memory, structured command relay, and traceable decision evidence across AI runtimes.
1
MIT
Linka MCP Next
by VodoooFilms
Related Servers
Alternatives to Linka MCP Next
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA minimal MCP server framework that enables zero-config tool discovery and streamable HTTP transport using the LeanMCP SDK. It allows developers to build type-safe services with automatic schema validation and integrated React UI components.-
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server providing file operations, web search, URL scraping, and sandboxed command execution for LLM interactions.1MIT
- AlicenseNot gradedqualityFmaintenanceA lightweight, fast MCP server that provides onchain capabilities for the LLMs and Agents.30 npm253MIT
- -licenseNot gradedqualityNot gradedmaintenanceLocal-first MCP server for repo-scoped development tasks like inspection, testing, documentation, and patching, designed to complement Cline with a structured local execution layer.-
TDQS
B3.2/5.0
Scored across 18 tools
Disambiguation5/5
Each tool targets a distinct resource or action, with clear domain prefixes (bridge, control, health, manifest, migration, session, status, teach). Even within the teach subgroup, tools like list-artifacts, get-artifact, and explain-artifact have non-overlapping purposes.
Naming Consistency4/5
All tools share a 'linka-' prefix and use snake_case. However, within the teach domain, some names are verb_noun (e.g., list-artifacts) while others are noun_noun (e.g., library-summary), creating minor inconsistency.
Tool Count4/5
18 tools is slightly above the typical 3-15 range but still reasonable given the multiple domains covered (bridge, control, health, manifest, migration, session, status, teach). No tool feels redundant.
Completeness3/5
The tool set covers many read-only and planning operations but has notable gaps: teach artifacts lack create/delete tools, and control actions have only planning without execution. This may cause agent failures when full lifecycle management is needed.
Maintenance
ActivityInactive
ResponsivenessNo issues