Skip to main content
Glama
Sign In
Tamperbox MCP

Tamperbox MCP

by oceanrescue
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Tamperbox MCP

No user-submitted related servers found.

    Related Servers

    • openapi-mcp

      diogofabri
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any OpenAPI 3.x spec into an MCP server that exposes one validated tool per API operation, so AI agents can discover and call a REST API over stdio or Streamable HTTP. It is read-only by default, with allow/deny lists, environment-based auth, timeouts and response truncation for safe agent access.
      MIT

    • Code Mode

      jamesrowdyy
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any OpenAPI spec into two sandboxed tools, search and execute, so an AI agent can discover endpoints and run small JavaScript programs against an entire API using under 1,000 tokens of context. Requests are read-only by default and the API key never enters the sandbox.
      MIT

    • tool-forge

      moeealii
      A
      license
      Not graded
      quality
      C
      maintenance
      Turns any OpenAPI spec into a single-tool MCP server where the model writes JavaScript against a typed api object in a QuickJS sandbox, so multi-step tasks run in one round trip and only the final result reaches context. Credentials, rate limiting, retries, write gating and audit logging stay on the host, outside the sandbox.
      MIT

    • Universal MCP

      rtostudioco
      A
      license
      B
      quality
      B
      maintenance
      Enables AI clients to access modular tools for file and data handling, statistical analysis, local NLP, automation, and system information over stdio or HTTP, with automatic module discovery and built-in sandboxing and security controls.
      31
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are mostly distinct: search is for discovering/filtering the OpenAPI spec and examples without making API calls, while execute is for making documented API requests via tamperbox.request. There is still some overlap because both run async JavaScript bodies, and search mentions builders/evidence analysis, which could blur the boundary slightly.

    Naming Consistency4/5

    Both names are lowercase imperative verbs, so the style is consistent and readable. They do not follow a descriptive verb_noun pattern, but for a two-tool meta-server the naming is predictable enough.

    Tool Count3/5

    Two tools is borderline thin, especially given the very broad domain implied by DNS, email, TLS, website, network, JWT, timestamp, and conversion workflows. The search+execute meta-tool pattern can justify a small surface, but it depends heavily on agents understanding the OpenAPI discovery workflow.

    Completeness4/5

    Together, search and execute provide a generic discover-then-call surface that can cover all documented operations in the underlying API. Minor gaps remain because there are no dedicated convenience tools or direct operation listings, but the meta-tool model avoids hard dead ends if the spec is complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources