Skip to main content
Glama
wrong-nebula

nock

by wrong-nebula
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nock

No user-submitted related servers found.

    Related Servers

    • projscan

      abhiyoheswaran1
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that provides AI coding agents with AST-accurate, context-budget-aware codebase querying, safety gates, and team policy integration via structured tools and a local plugin layer.
      65 npm
      4
      MIT

    • worker-mcp

      noosxe
      A
      license
      A
      quality
      A
      maintenance
      MCP server that enables a coordinator AI agent to spawn, control, and supervise local coding agents with interactive gating for high-risk operations.
      10
      4 npm
      MIT

    • LeanRigor MCP Server

      badrabbitt
      A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP gateway that reduces context overhead in coding-agent sessions by exposing only relevant tools and enforcing task-appropriate engineering gates, with privacy-first defaults and no network calls until explicitly enabled.
      Apache 2.0

    • toke-local

      rianprei
      A
      license
      Not graded
      quality
      B
      maintenance
      A local, zero-dependency MCP server that cuts coding-agent round-trips by aggregating search, read, edit, exec, git, and savings tools into single, validated calls, with cost tracking and no data leaving the machine.
      1
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: resolve handles natural-language routing, call executes concrete tool envelopes, search retrieves catalog metadata without executing, and status reports health. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools share the consistent nock.* prefix and use short, lowercase action-oriented names. The pattern is uniform and predictable across the set.

    Tool Count5/5

    Four tools is well-scoped for a gateway/catalog server: discovery, resolution, execution, and status. Each tool earns its place with no redundancy.

    Completeness5/5

    The tool surface covers the full proxy lifecycle: search the catalog, resolve natural language to a call, execute via upstream, and check server health. No obvious missing operation for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources