Skip to main content
Glama
Starksood

fireweed-mcp

by Starksood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to fireweed-mcp

No user-submitted related servers found.

    Related Servers

    • obliviate

      vinayaksonthalia
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server for agent memory that enables remembering, recalling, and provably forgetting knowledge with cascade deletion, cryptographic shredding, and signed erasure certificates.
      MIT

    • Nahuali

      Arakiss
      F
      license
      Not graded
      quality
      A
      maintenance
      Local-first memory for AI agents with evidence-backed recall, deterministic trust verdicts, self-inspection, and a tamper-evident audit history.
      3
      -

    • memotrust

      Idanref
      A
      license
      Not graded
      quality
      C
      maintenance
      Verified memory for AI agents — agents propose memories that are quarantined until verified against evidence, and recall() returns only trusted, fresh, and in-scope facts, preventing poisoned or hallucinated data from spreading.
      13 npm
      1
      MIT

    • Aion Memory Nexus

      234194027-cpu
      A
      license
      Not graded
      quality
      B
      maintenance
      A trusted memory and predictive analysis MCP server for AI agents, enabling evidence-based memory management, pattern analysis, and decision support with full audit trails.
      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.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct operation: writing, recalling, erasing, exporting, auditing reads, tracing provenance, verifying receipts, and reviewing quarantine. The closest pairs (review_reads vs review_quarantine, trace_evidence vs verify_receipts) are clearly separated by their descriptions.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern (add_source, export_memory, verify_receipts, trace_evidence, review_reads, review_quarantine), but remember, recall, and forget are bare verbs and memory_stats is noun_noun. The style is readable and lowercase-snake throughout, but the convention is genuinely mixed.

    Tool Count5/5

    Ten tools is well-scoped for a verifiable memory substrate. Each tool covers a necessary capability—ingestion, recall, deletion with proof, export, audit, verification, quarantine review, and statistics—without redundant or filler tools.

    Completeness5/5

    The surface covers the full evidentiary memory lifecycle: add_source and remember for writing, recall for reading, forget for erasure with proof, export for portability, plus trace_evidence and verify_receipts for auditability. The append-only, evidence-bound design makes an update tool unnecessary; corrections would naturally flow through new evidence.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources