Skip to main content
Glama
Donnyb369

MCP Spine

by Donnyb369
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to MCP Spine

No user-submitted related servers found.

    Related Servers

    • CtxSlim

      v01dst
      A
      license
      Not graded
      quality
      A
      maintenance
      A local MCP proxy that reduces context bloat by exposing only relevant tools and compressing schemas, enabling efficient use of multiple MCP servers.
      247 npm
      2
      MIT

    • mcpfold

      dj-pearson
      F
      license
      Not graded
      quality
      B
      maintenance
      Local-first CLI + proxy that curates your MCP servers per client from one canonical config, cutting tool-schema tokens ~80% and resolving secret references instead of hardcoding keys.
      -

    • mcpproxy-go

      smart-mcp-proxy
      A
      license
      A
      quality
      A
      maintenance
      Local-first MCP proxy with BM25 tool discovery, quarantine security, Docker isolation, OAuth support, activity logging, and web UI. Routes multiple upstream MCP servers through a single endpoint.
      9
      376
      MIT

    • MCProxy

      danimalquackers
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server proxy that reduces context window bloat by stripping metadata and fetching schemas on-demand, while managing backend MCP servers across multiple transports. It also provides a web dashboard for monitoring and restarting backend servers.
      -

    • mcp-doorman

      Sushank05
      A
      license
      Not graded
      quality
      C
      maintenance
      A drop-in proxy that guards MCP servers with policy enforcement, secret redaction, prompt-injection screening, rug-pull detection, rate limiting, and audit logging.
      5 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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    spine_set_context and spine_recall have completely distinct roles: one writes/updates the current work context and changes tool visibility, the other reads cached results from prior calls. There is no overlap or plausible selection confusion.

    Naming Consistency5/5

    Both tool names follow the same spine_<verb> pattern and use snake_case. The verbs set_context and recall are clear and parallel, so an agent can predict tool naming.

    Tool Count4/5

    At two tools, the server is below the typical 3-15 tool range, but the scope is narrow and each tool serves one essential function: updating context and recalling cached results. The count is slightly under but still reasonable for its purpose.

    Completeness4/5

    The server covers the core context-setting and cache-recall workflows without obvious dead ends. Minor gaps exist (no explicit clear-context or clear-cache operation), but set_context can overwrite context and recall covers the main retrieval need.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources