SpyNet
Related Servers
Alternatives to SpyNet
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceLets AI assistants create and manage Mockoon mock APIs through natural language.2120 npm3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to dynamically add, update, and remove Mock Service Worker network mocks through MCP tools without restarting the application. It also supports scaffolding MSW setup and managing browser-connected mocking sessions via a WebSocket bridge.15 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to dynamically add, update, and remove Mock Service Worker network mocks through MCP tools, without restarting the application source code. It bridges the MCP/CLI side with the browser via WebSocket for live handler updates and setup scaffolding.15 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to build, debug, and test hosted mock REST APIs by scaffolding persistent CRUD resources, importing OpenAPI specs, simulating requests, auto-healing failing endpoints, and injecting latency or error faults. It also exposes live OpenAPI and TypeScript contract resources for each workspace.MIT
- AlicenseBqualityDmaintenanceEnables AI to manage whistle mock rules, values, and inspect network sessions, facilitating API mocking and debugging through natural language.174 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to dynamically add, update, and remove Mock Service Worker network handlers in a running browser app through a WebSocket bridge, without touching application source code or reloading the page. It also provides a setup prompt to scaffold the MSW and client integration in a project.15 npmMIT
TDQS
Scored across 8 tools
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.
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.
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.
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.