Skip to main content
Glama
portel-dev

NCP - Natural Context Provider

by portel-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to NCP - Natural Context Provider

No user-submitted related servers found.

    Related Servers

    • slop-mcp

      standardbeagle
      A
      license
      B
      quality
      A
      maintenance
      An MCP orchestration layer that aggregates multiple MCP servers while exposing only 8 meta-tools, dramatically reducing context window usage, and provides SLOP scripting, event monitoring, and tool customization.
      10
      19 PyPI
      MIT

    • Bifrost-MCP Gateway

      david-spies
      A
      license
      Not graded
      quality
      D
      maintenance
      Enterprise-grade dynamic MCP proxy that eliminates token bloat by lazy-loading tool schemas based on semantic intent, enabling efficient orchestration of multiple backend tools from a single endpoint.
      MIT

    • 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

    • MCP Gateway

      abdullah1854
      A
      license
      Not graded
      quality
      F
      maintenance
      A universal gateway that aggregates multiple MCP servers into a single interface while providing advanced token optimization, result filtering, and automated summarization. It enables efficient management of large tool catalogs and reduces context usage by up to 95% for major AI clients.
      9 npm
      16
      MIT
    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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    find and code have clearly distinct purposes: one for discovering/listing tools, the other for executing TypeScript code. There is no ambiguity about which tool to use for a given task.

    Naming Consistency4/5

    Both tool names are lowercase single words, so the style is consistent. However, the names are vague and do not follow a descriptive verb_noun convention like search_tools or execute_code.

    Tool Count3/5

    With only two tools, the server feels thin, but as a meta-tool that can execute arbitrary code, it could be reasonably scoped. Still, two tools is on the low end and likely limits direct usability.

    Completeness2/5

    The server advertises ncp.do and direct namespace calls, but these are not exposed as actual tools. The only way to invoke external tools is through the code tool, which is a significant gap for a provider that claims to make tool invocation natural. Basic operations like retrieving a specific tool's schema or directly calling a tool are missing.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources