Skip to main content
Glama
CumulativeWebInc

cwi-mcp-server

Official
by CumulativeWebInc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to cwi-mcp-server

No user-submitted related servers found.

    Related Servers

    • cluby-mcp

      clubytech
      A
      license
      A
      quality
      B
      maintenance
      Enables agents to read Cluby markets, positions, and pre-trade quotes over stdio, using the same arithmetic as the interface while holding no keys and signing nothing.
      9
      MIT

    • Archive MCP Server

      Surajp1602
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying enterprise records and retention policies from any MCP client over stdio, with read-only tools for searching records, fetching retention verdicts, identifying archival candidates, summarizing departments, forecasting retentions, and viewing audit history.
      -

    • DEFAIR MCP Server

      joblinours
      A
      license
      A
      quality
      B
      maintenance
      Exposes forensic case and evidence management operations over stdio, including case creation, evidence registration with SHA-256 hashing, and integrity verification, so clients can manage DFIR investigations programmatically.
      7
      MIT
    • Agent Deck MCP Server by CumulativeWebInc

      Agent Deck MCP Serverofficial

      CumulativeWebInc
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable agents to query a read-only 18-SKU product registry and verified 24-track catalog, with evidence-tied lookups, momentum scoring, skin configurations, and a hash-chain-verified ledger over stdio.
      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.1/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a distinct purpose: ledger_state_get returns the full state document, ledger_agents and ledger_tasks are specialized views, ledger_task_get is a detail lookup, and trust_verdict/needledrop_verify cover different verification domains. The only mild ambiguity is that ledger_state_get can also reach agents/tasks via its fields argument, but descriptions make the specialized tools clearly preferable for those cases.

    Naming Consistency3/5

    The ledger tools share a useful `ledger_` prefix and snake_case, but verb placement is inconsistent: some names end with `_get` (ledger_state_get, ledger_task_get), others are bare nouns (ledger_agents, ledger_tasks), one is a noun phrase (ledger_state_version), and the non-ledger tools use different forms (trust_verdict, needledrop_verify). The convention is readable but not predictable enough to infer tool names without reading descriptions.

    Tool Count5/5

    Seven tools is a well-scoped set for this server. It provides the core read-only ledger views, a task detail endpoint, the state version, plus two specialized verification/scoring tools without unnecessary redundancy.

    Completeness4/5

    The read-only ledger surface covers the main entities: full state, agents with presence, task summaries, and task detail, plus a version endpoint. The main gap is that handoffs and approvals are only reachable through ledger_state_get rather than dedicated tools, but agents can work around that by requesting the full state or selecting fields.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources