fieldtwin
Related Servers
Alternatives to fieldtwin
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to read realistic, coherent data—repos, pull requests, issues, commits, users—through API-compatible, read-only replicas of 21 developer platforms including GitHub, Jira, Linear, Slack, Sentry and Salesforce, all preloaded with one simulated company so integrations can be built and tested with no accounts, credentials, rate-limit worry, or cleanup.10197 npmMIT

Rystic MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables coding agents to run local simulators of real APIs, load scenarios, seed records, move clocks, inspect state and outbound effects, diff changes, and save runs as regression tests.1MIT- AlicenseNot gradedqualityBmaintenanceEnables developers and AI agents to start stateful local twins of real APIs from built-in packs, OpenAPI specs, HAR recordings, or documentation, then inspect requests, state, and webhooks; force scenarios, chaos, and time changes; and reset or stop twins through MCP tools.107 npm1Apache 2.0

fetchsandbox-mcpofficial
AlicenseAqualityBmaintenanceA deterministic eval engine for coding agents. Your agent claims it fixed the bug—this checks it. The same scenario runs twice against a sandbox of the services your code calls, with failures injected on purpose. It must fail on the old code and pass on the new. The verdict is an exit code, not a model's opinion. Every run leaves a receipt.19442 npm1MIT- 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
- AlicenseNot gradedqualityBmaintenanceExposes a fictional small business as 46 MCP tools spanning CRM, inbox, calendar, invoicing and phone, letting agents read and modify customers, deals, messages and payments with validated, audited writes that stay inside the process.Apache 2.0
TDQS
Scored across 14 tools
Most tools target clearly distinct operations (load scenario, set faults, advance clock, rewind), and descriptions actively disambiguate close pairs, e.g. twin_export_log points to twin_changes for a summary and twin_reset points to twin_rewind for partial undo. The main residual confusion is the read/write pair twin_webhooks vs twin_set_webhooks, and the three 'restore world' tools (reset, rewind, load_scenario), which descriptions clarify but which still sit close together.
Every tool uses the same 'twin_' prefix and snake_case, giving a strong shared identity. The verb position is mostly predictable (twin_set_*, twin_list_*, twin_export_*, twin_advance_*), but read-only getters break the pattern by using bare nouns (twin_status, twin_webhooks, twin_changes, twin_checkpoint), creating an asymmetry with twin_set_webhooks.
Fourteen tools is well within the sweet spot and each maps to a distinct responsibility in the simulation lifecycle: world setup, environment knobs, time control, observation, and rollback. Nothing feels padded or bolted on.
Lifecycle coverage is strong: build/load a world, configure faults, auth and webhooks, move time, trigger actions, observe via status/log/changes, and roll back via checkpoint/rewind/reset. The notable gap is there is no way to inspect the twin's actual records (customers, invoices, jobs) directly—only event streams and status—and no way to delete or list a single checkpoint.