Skip to main content
Glama
BlaineHeffron

nodus-mcp

by BlaineHeffron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nodus-mcp

No user-submitted related servers found.

    Related Servers

    • proxycept-mcp

      MoathOthman
      A
      license
      Not graded
      quality
      C
      maintenance
      A thin stdio-to-HTTP bridge that forwards MCP messages to the hosted Proxycept server, enabling stdio-only MCP clients to access Proxycept's tool catalog.
      9 npm
      MIT

    • @modusop/mcp-server

      jwwd-repos
      A
      license
      Not graded
      quality
      C
      maintenance
      Acts as a stdio-to-HTTP proxy for Modus Brain, enabling MCP-compatible AI clients to access an organization's knowledge base in ModusOp.
      23 npm
      Cryptographic Autonomy 1.0 (Combined Work Exception)

    • mcp-shell

      imajeure
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a secure, token-authenticated command execution tool over MCP Streamable HTTP, with a default-deny allowlist and shell metacharacter rejection.
      5 npm
      1
      Apache 2.0

    • veriloop

      arvindcr4
      A
      license
      A
      quality
      C
      maintenance
      Exposes a verified tool registry (calculator, sandboxed file read, web fetch) over MCP stdio, enabling any MCP-capable client to reuse the same tools from the inspectable ReAct loop.
      3
      MIT

    • neo4j-mcp-gateway

      jeffneo
      F
      license
      A
      quality
      B
      maintenance
      A single local MCP gateway for Neo4j that exposes both proxied generic Neo4j tools (schema, Cypher, GDS) and custom YAML-defined use-case tools behind one stdio endpoint.
      3
      -

    • FastMCP Remote Proxy

      shahil04
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables local MCP clients to access tools from a remote FastMCP server over stdio, handling OAuth authentication and Streamable HTTP communication.
      -
    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.8/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusing it with other operations. Its purpose as a health/readiness check is clear and unambiguous.

    Naming Consistency5/5

    The single tool name is clear, descriptive, and follows a consistent hierarchical pattern with the server prefix. There are no mixed conventions to cause confusion.

    Tool Count1/5

    A lone health-check tool is a trivial surface for an MCP server. Even as a gateway utility, it provides almost no functional value and appears extremely under-scoped.

    Completeness1/5

    The server exposes only a health check, so no substantive domain operations exist. Any real workflow would dead-end immediately after confirming reachability.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources