Skip to main content
Glama
jeffneo

neo4j-mcp-gateway

by jeffneo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to neo4j-mcp-gateway

No user-submitted related servers found.

    Related Servers

    • nodus-mcp

      BlaineHeffron
      A
      license
      A
      quality
      B
      maintenance
      A thin stdio gateway to Nodus's Streamable HTTP MCP server, exposing a curated allowlist of tools for the Research Workbench. It enables secure, bearer-authenticated interactions with Nodus without graph logic or caching.
      1
      MIT

    • @zhangzwd/mcp-gateway

      zhangzwd
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP gateway that aggregates multiple MCP services into a unified stdio interface, automatically prefixing tool names with the service name to avoid conflicts.
      14 npm
      MIT

    • ToolFunnel

      Rendeverance
      A
      license
      A
      quality
      A
      maintenance
      A zero-dependency MCP gateway: host your own tools, forward and curate tools from other MCP servers, expose them leanly to cut agent token cost, and gate every call through your own policy hooks before it runs.
      4
      13 npm
      37
      MIT

    • MCP Capability Matchmaker

      ywh0606
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP gateway and offline catalog CLI that aggregates multiple upstream MCP servers into a single stdio endpoint, and provides tool recommendation and catalog inspection without connecting to upstreams.
      MIT

    • 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
      377
      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.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool addresses a distinctly different use case: synthetic identity detection, movie search, and high-risk transaction analysis. There is no overlap or ambiguity in their intended purposes.

    Naming Consistency3/5

    All tools share the consistent 'usecase_' prefix, but the action part varies: 'detect', 'search', and a noun phrase 'high_risk_transactions' (no verb). This mix of verb_noun and noun-only patterns is somewhat inconsistent.

    Tool Count3/5

    With only 3 tools, the set is on the low side for a Neo4j gateway that could plausibly support many graph operations. It feels like a small demo set rather than a comprehensive service, but it is not absurdly thin.

    Completeness2/5

    The tools are a random assortment of curated use cases with no clear domain coverage. There is no general query, write, or management capability, and the movie search seems unrelated to fraud/AML use cases, leaving significant gaps for any given purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources