Skip to main content
Glama
BrianGTRxx

api-mock-sandbox

by BrianGTRxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to api-mock-sandbox

No user-submitted related servers found.

    Related Servers

    • obsidian-mcp-server

      FAL1989
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to interact with an Obsidian vault through the Local REST API, allowing file listing, reading, searching, creating, and updating markdown notes.
      9,687 npm
      Apache 2.0

    • mcp-x

      LakshmiSravyaVedantham
      A
      license
      Not graded
      quality
      D
      maintenance
      Turns any CLI tool or REST API into an MCP server for Claude, enabling Claude to use git, databases, or any API through natural language.
      MIT

    • ObsidianMCP

      rcgeorge
      A
      license
      B
      quality
      D
      maintenance
      Enables Claude to interact with an Obsidian vault via the Local REST API plugin, supporting file operations, search, periodic notes, commands, and semantic search.
      22
      3,430 npm
      MIT

    • mcp-api-bridge

      BryceEWatson
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants like Claude to interact with any REST API through typed, validated MCP tools. Provides a pattern to wrap REST APIs as MCP servers.
      MIT
    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

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct roles: one creates/reconfigures the mock API and the other queries its runtime status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern using snake_case: setup_mock_api and get_mock_api_status. The style is uniform and predictable.

    Tool Count4/5

    With only two tools, the surface is minimal but arguably appropriate for a focused mock server utility. It feels slightly thin for a full lifecycle but is not unreasonable.

    Completeness3/5

    The set covers setup and status checking, but lacks obvious lifecycle operations like stopping/resetting the server or clearing collections. Agents can work around this, but the surface leaves gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources