Skip to main content
Glama
shashankcube

sor-mcp-server

by shashankcube
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to sor-mcp-server

No user-submitted related servers found.

    Related Servers

    • MCPLens

      jcgs2503
      F
      license
      Not graded
      quality
      D
      maintenance
      A context-efficient proxy that replaces individual tool schemas with three meta-tools for semantic search, schema retrieval, and tool routing. It enables agents to manage hundreds of backend tools while maintaining a constant context footprint of approximately 500 tokens.
      1
      -

    • mcp-search-proxy

      p1s4
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients of tool-heavy MCP aggregators to find and use upstream tools on demand through four fixed bridge tools (search, describe, call, refresh), cutting per-turn tool context from ~180k tokens to ~2–3k. It merges multiple upstream servers behind sticky sessions and a local lexical BM25 index, so only the schemas actually needed are retrieved.
      4
      MIT

    • mcptool

      kspatel29
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A drop-in MCP proxy that aggregates multiple backend servers into two meta-tools for efficient tool discovery and execution. It enables AI clients to access hundreds of tools while minimizing context window usage through searchable indexing.
      1 npm
      -

    • MCP of MCPs

      eliavamar
      A
      license
      Not graded
      quality
      D
      maintenance
      A meta-server that aggregates multiple MCP servers into a single interface, reducing token usage by 98%+ through progressive tool discovery and direct code execution that processes data between tools without consuming context window space.
      16 npm
      10
      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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: search_tools is for discovery, get_tool_schema is for inspecting a known tool's schema, and execute_tool is for running the selected tool. The overlap between search_tools returning schema fields and get_tool_schema providing full schema is managed well by the descriptions.

    Naming Consistency5/5

    All tool names follow a consistent lowercase verb_noun pattern: search_tools, execute_tool, get_tool_schema. This makes the tool set predictable and easy to navigate.

    Tool Count5/5

    Although only 3 tools are exposed, this is appropriate for a meta-server that dynamically accesses 174 underlying CRUD tools. Each tool earns its place in the discover-schema-execute workflow, so the count is well-scoped rather than thin.

    Completeness4/5

    The set covers the full meta-workflow: discover tools, inspect schemas, and execute operations. A minor gap is the lack of an explicit list-all-tools operation, though search_tools likely covers discovery if used with a broad query.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources