Skip to main content
Glama
driftwork-llc

@sandboxapis/mcp

by driftwork-llc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @sandboxapis/mcp

No user-submitted related servers found.

    Related Servers

    • fetchsandbox-mcp by fetchsandbox

      fetchsandbox-mcpofficial

      fetchsandbox
      A
      license
      A
      quality
      A
      maintenance
      A 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.
      19
      1,384 npm
      1
      MIT

    • companysim

      dolevhayut
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to explore and query a locally generated synthetic organization—with employees, teams, projects, documents, and relationships—through read-only MCP tools, facilitating agent testing, evaluation, and demos without external APIs.
      3
      MIT

    • APIMock MCP Server

      shrestharikesh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • sandbox-seed

      PranavNagrecha
      A
      license
      Not graded
      quality
      A
      maintenance
      Salesforce sandbox seeding, built for AI agents. SOQL-driven org-to-org record copy with automatic dependency-graph walking, cross-org FK remapping, and a hard AI-never-sees-your-data boundary.
      30 npm
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 10 tools

    Disambiguation4/5

    The data tools each target a distinct resource+action (repositories, pull requests, issues, users, commits), and the three meta tools (orient, get_snapshot, check_budget) serve clearly different setup/reproducibility/budget purposes. Minor risk that orient overlaps conceptually with check_budget and get_snapshot as 'introspection' tools, but descriptions clearly separate them.

    Naming Consistency4/5

    Nearly all tools follow a predictable verb_noun pattern (get_snapshot, check_budget, list_repositories, get_repository, list_pull_requests, get_pull_request, list_issues, get_user, search_commits_by_author). The lone bare verb 'orient' is a minor deviation from the otherwise consistent scheme.

    Tool Count5/5

    Ten tools is well-scoped for a read-only multi-provider API surface with a few setup helpers. Each tool earns its place with no obvious redundancy or filler.

    Completeness4/5

    The read-only surface covers lists/gets for repositories and pull requests plus issues, users, and commit search, matching the stated read-only, snapshot-oriented purpose. Asymmetries remain (list_issues with no get_issue, get_user with no user list, no issue/PR comment retrieval), but agents can work around these via the returned REST paths.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources