Skip to main content
Glama
Sign In
json-chamber-mcp

json-chamber-mcp

by Slid-Phi-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to json-chamber-mcp

No user-submitted related servers found.

    Related Servers

    • knobe-mcp-server

      KnobeDev
      A
      license
      A
      quality
      C
      maintenance
      MCP server for sealing, verifying, and reading KNOBE Protocol v1 documents with human-confirmed authorship, ensuring document provenance and integrity.
      5
      Apache 2.0

    • genpark-agentic-commerce-agent

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to authenticate legitimate consumer shopping agents through cryptographic proof-of-delegation and block scraper abuse at retail gateways. It also exposes machine-to-machine catalog resolution, spend-bounded tokenized payment delegation, and automated alternating-offers bargaining over STDIO JSON-RPC.
      7
      MIT

    • attest-mcp-remote

      SPAZIO-GENESI
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for verifying and attesting SHA-256 fingerprints of digital works via Streamable HTTP, with zero-install and privacy-preserving design.
      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

    B3/5.0

    Scored across 7 tools

    Disambiguation4/5

    The tools have distinct roles: status/info for licensing, cloak/open for sealing/unsealing, and two separate gate checks (hop_gate vs benefit_check) plus a log. There's minor overlap between status and info (both about license state), but they serve different details. Overall, an agent can tell them apart with clarity.

    Naming Consistency3/5

    Most tools follow a 'chamber_' prefix with a noun or verb (status, info, cloak, open, hop_gate, hop_reject_log), but 'benefit_check' breaks the pattern. The verbs are inconsistent (some are nouns like status, others are imperatives like cloak), though the naming is still readable and mostly predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose: managing sealed JSON chambers, checking license status, and evaluating gates. Each tool has a clear function, and the count is appropriate for the domain without being overwhelming or too sparse.

    Completeness4/5

    The core lifecycle is covered: sealing (chamber_cloak), opening (chamber_open), status (chamber_status), and license info (chamber_info). Gate evaluation and logging are also included. A minor gap is no tool to list or manage multiple chambers, but for the given purpose, the surface is largely complete.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources