Skip to main content
Glama
amitboker

anchor-mcp

by amitboker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to anchor-mcp

No user-submitted related servers found.

    Related Servers

    • live-docs-mcp

      Jubast
      F
      license
      B
      quality
      B
      maintenance
      A local-only MCP server that provides AI coding agents with up-to-date documentation for specific libraries or tools during feature implementation, including search tools, multi-version support, and user-defined library entries.
      2
      -

    • cortex-brain

      sani-savaliya
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to search, read, and contribute to a structured markdown knowledge base with citations, freshness tracking, and a safe write path, providing a shared, auditable company memory.
      3 npm
      MIT

    • graphmemory

      graph-memory
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that builds a semantic graph memory from a project directory, indexing documentation and code into graph structures and exposing 70+ MCP tools for search, knowledge management, task management, and more.
      11 npm
      15
      Elastic 2.0

    • Context Loom

      ownasquare
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that integrates with chat tools to provide context from local projects, enabling reviewed and cited prompts.
      MIT

    • KnowledgeRail

      Deviank88
      A
      license
      C
      quality
      A
      maintenance
      Local-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.
      8
      1,003 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: fetching a fragment, drafting content, querying the brain, listing contradictions, listing gaps, and listing sources. There is no functional overlap, so an agent can reliably choose the right tool based on the task.

    Naming Consistency4/5

    The list_* tools are consistent, but get_fragment, draft, and ask_brain deviate from a uniform verb_noun pattern. Despite this, all names are lowercase with underscores and the verbs are descriptive, making the set readable and predictable overall.

    Tool Count5/5

    With six tools, the server is well-scoped for its purpose of analyzing and synthesizing project sources. Each tool earns its place, and the count is within the ideal 3-15 range.

    Completeness4/5

    The tool set covers the main workflows: inspecting sources, retrieving fragments, querying historical context, surfacing contradictions and gaps, and drafting. A minor gap is the lack of a tool to list all fragments or ingest new sources, but the server appears intentionally read-only, so this is an acceptable limitation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources