Skip to main content
Glama
crunchtools

mcp-metsuke-crunchtools

Official
by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to mcp-metsuke-crunchtools

No user-submitted related servers found.

    Related Servers

    • codemem

      jeang42
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, searchable memory across coding projects and machines, letting agents record and retrieve projects, reusable assets, sessions, decisions, commits, and handoffs via MCP.
      2
      Apache 2.0

    • Argon Memory

      Tangtaizong-BUAA
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP agents to maintain durable, evidence-aware project knowledge, retrieve precise excerpts on demand, and track decisions, conflicts, and revisions across sessions.
      1
      Apache 2.0

    • totem-mcp

      emiliano-go
      A
      license
      C
      quality
      A
      maintenance
      Enables engineering agents to maintain persistent knowledge across sessions by storing decisions, invariants, gotchas, and rejected ideas, with staleness detection, conflict detection, full-text search, and structured context assembly.
      31
      2
      MIT

    • Context-MCP

      yesheng-oss
      A
      license
      A
      quality
      B
      maintenance
      Acts as a persistent memory and cross-tool shared context store, and builds a queryable codebase knowledge graph to slash token usage via structural answers.
      9
      18 npm
      28
      MIT

    • Memory Cortex

      TYRANNOSAURX
      A
      license
      Not graded
      quality
      C
      maintenance
      Durable, inspectable memory for MCP agents. Preserves decisions, preferences, and project knowledge across sessions with full provenance and version history.
      3
      Apache 2.0
    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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: report definitions versus gathered outputs, and read versus write operations. There is no meaningful overlap between listing definitions, fetching specs, upserting definitions, saving outputs, or reading outputs.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun_tool pattern: list_reports, get_spec, upsert_definition, save_output, get_output. The naming convention is uniform and predictable.

    Tool Count5/5

    Five tools is well-scoped for this server's apparent purpose: managing report definitions and gathering/reading report outputs. Each tool serves a clear role without unnecessary redundancy.

    Completeness4/5

    The server covers the core workflow: create/update definitions, inspect them, gather output, and retrieve output. A delete operation for definitions or outputs is absent but not clearly required by the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources