Skip to main content
Glama
ipvolt

ipvolt Proxy Toolkit

Official
by ipvolt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ipvolt Proxy Toolkit

No user-submitted related servers found.

    Related Servers

    • verimcp

      rudranaresh0201
      A
      license
      Not graded
      quality
      B
      maintenance
      A transparent MCP proxy that independently re-verifies tool-call claims instead of trusting them, paired with devmcp — the git/CI server it's proven against.
      1
      MIT

    • Warrant

      humanitysystems
      F
      license
      Not graded
      quality
      B
      maintenance
      A local, transparent MCP proxy with an admin console that connects MCP clients to downstream MCP servers, forwards requests unchanged, and exposes live operational events over a localhost dashboard.
      5 npm
      -

    • 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.
      -

    • Agentrim MCP

      almohtadyg1
      A
      license
      Not graded
      quality
      B
      maintenance
      A least-privilege enforcement proxy for MCP servers. It sits between MCP clients and upstream servers, enforcing tool policies, hiding denied tools, requiring human approval for risky actions, and providing a structured audit trail.
      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 4 tools

    Disambiguation5/5

    Each tool occupies a distinct phase of a support workflow: discovery (search_proxy_docs), retrieval (get_proxy_doc), generation (generate_proxy_config), and troubleshooting (diagnose_proxy_error). The search/retrieve pair is explicitly linked via document IDs and cursors, and generate vs. diagnose are clearly separated by intent. No two tools could be mistaken for one another.

    Naming Consistency5/5

    All four tools use a consistent verb_noun snake_case pattern with a stable 'proxy' domain prefix (search_proxy_docs, get_proxy_doc, generate_proxy_config, diagnose_proxy_error). The verb choice matches the action in every case, and the only variation (docs vs. doc) is a natural plural/singular distinction.

    Tool Count4/5

    Four tools is a tight, well-scoped set that covers the core workflow without redundancy, which fits a focused proxy guidance toolkit. It sits at the thin end of the range, since broader operations like listing available client versions or documents are absent, but nothing feels padded or missing at the task level.

    Completeness4/5

    Search-plus-retrieve covers the documentation lifecycle, and generate/diagnose address the two main user actions (writing config, fixing errors), so agents have a path through the domain. Minor gaps remain: no tool to enumerate supported client/version combinations or to validate a generated example before use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources