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
      C
      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.
      238 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
      17 npm
      MIT
    • mcpgawk by gawk-dev

      mcpgawkofficial

      gawk-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server lets agents inspect every Model Context Protocol server on the machine, verify tools by running them in a sandbox, and check each call against a human-approved baseline so that changed or newly appeared tools are blocked before they execute. It also surfaces token cost, capability facts, and drift history for each tool entirely locally, without uploading inventory or requiring an account.
      1,055 PyPI
      Apache 2.0

    • 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
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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

    ActivityStale
    ResponsivenessNo issues

    Resources