Skip to main content
Glama
aj-bartocci

SpyNet

by aj-bartocci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SpyNet

No user-submitted related servers found.

    Related Servers

    • whistle-mcp

      hzbhzb
      A
      license
      B
      quality
      C
      maintenance
      Enables AI to manage whistle mock rules, values, and inspect network sessions, facilitating API mocking and debugging through natural language.
      17
      3 npm
      1
      MIT

    • hookray-mcp

      ShotaTanikawa
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create disposable webhook URLs, capture incoming HTTP requests, inspect headers and bodies, and replay them against local or remote endpoints, streamlining the webhook handler development loop.
      5
      4 npm
      MIT

    • mockserver-mcp

      Akkshay10
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for interacting with MockServer, enabling AI assistants to create mock HTTP expectations, verify requests, clear state, and manage MockServer instances programmatically.
      6
      37 npm
      1
      MIT

    • MCP Playground

      Roelzz
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables admins to author and manage persistent mock MCP servers and OpenAI-compatible endpoints through a browser UI and admin API, with REST mocks, shared datasets, and traffic logging for demos and training.
      -
    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

    B3.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity: clear_endpoints, configure_endpoint, delete_session, get_request_history, list_endpoints, list_sessions, send_websocket_action, and send_websocket_data all target specific, non-overlapping operations in the mock API/WebSocket testing domain. The descriptions reinforce this clarity, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, such as clear_endpoints, configure_endpoint, and list_sessions. This predictability aids agent understanding and selection, with no deviations in style or convention across the set.

    Tool Count5/5

    With 8 tools, the count is well-scoped for a mock API and WebSocket testing server. Each tool serves a distinct role in managing sessions, endpoints, and WebSocket communications, avoiding bloat while covering essential operations for the domain.

    Completeness4/5

    The tool set provides strong coverage for session and endpoint management, including CRUD-like operations (list, configure, clear, delete) and WebSocket messaging. A minor gap exists in not having tools for modifying existing endpoints or detailed session configuration, but agents can work around this with the available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources