Skip to main content
Glama
DanceNitra

inspeximus

by DanceNitra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to inspeximus

Related Servers

  • dakera-mcp by Dakera-AI

    dakera-mcpofficial

    Dakera-AI
    F
    license
    A
    quality
    B
    maintenance
    Self-hosted MCP-native agent memory server. Gives AI agents persistent, decay-weighted memory via 83 MCP tools — no cloud, full control. RocksDB+HNSW backend. Works with Claude Code, Cursor, and any MCP-compatible agent.
    14
    8
    -

  • verifiable-memory

    Mars-proj
    A
    license
    A
    quality
    D
    maintenance
    Memory for AI agents that can't hallucinate — answers only from stored facts with a citation, or honestly abstains. Provable forgetting (GDPR), valid-time, Merkle proofs, deterministic. MCP server, CPU-only, zero dependencies.
    13
    1
    MIT
  • Recall by RecallWorks

    Recallofficial

    RecallWorks
    A
    license
    Not graded
    quality
    C
    maintenance
    Open-source MCP memory server for AI agents — persistent, searchable, tiered memory across sessions. Works over stdio (Cursor, Claude Desktop) or HTTP+SSE. MIT licensed.
    7
    MIT

  • ForkMind

    Medhovarsh
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first MCP server that lets AI agents query their own LLM call history as a branchable DAG and offload conversation context into immutable, AES-256-GCM-encrypted capsules — restorable in full or per segment, crypto-shreddable, with RAID-style replication. 12 tools, no API keys, no cloud.
    62 npm
    3
    MIT

  • Remnic

    joshuaswarren
    A
    license
    Not graded
    quality
    Not graded
    maintenance
    Local-first memory for AI agents: one store shared by Claude Code, Codex CLI, Cursor, Pi, Hermes, OpenClaw, and any MCP client. Plain markdown with YAML frontmatter on your disk, hybrid BM25 + vector recall with per-result provenance (Recall X-ray), a correction contract, and the MemCorrect benchmark.
    198
    MIT

  • NeverOnce

    WeberG619
    A
    license
    A
    quality
    C
    maintenance
    Persistent, correctable AI memory with zero dependencies. Corrections always surface first and never decay. SQLite-backed, 400 lines of pure Python, MCP server included.
    7
    3
    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

A3.6/5.0

Scored across 73 tools

Disambiguation2/5

The tool set has multiple tightly clustered surfaces that are easy to confuse: forget/forget_subject/forget_pii/retention, verify_writes/verify_consistency/verify_witness/verify_audit_bundle/verify_attribution, and compliance_report/compliance_check/governance_report all require reading lengthy descriptions to distinguish. While each description is individually careful, the boundaries between these clusters are subtle enough that an agent would frequently misselect.

Naming Consistency3/5

The majority of tools follow a readable snake_case imperative style (remember_decision, verify_claim, check_conflict), but the set mixes verb-first names with bare nouns (history, provenance, grants, neighbors, sleep, witness, anchor) and noun-phrase report names (supersession_report, erasure_certificate). The convention is not chaotic, but it is inconsistent enough to be a mixed rather than uniform pattern.

Tool Count1/5

73 tools is an extreme count for a single MCP server, far beyond the typical well-scoped 3-15 range. Even with the broad ambition of memory plus integrity, erasure, access control, and compliance, the surface is overloaded and would be better split into focused servers or namespaced submodules.

Completeness5/5

The domain is exceptionally well covered: core memory lifecycle (remember/get/recall/forget), supersession and reversion, multi-hop retrieval, erasure and right-to-forget, access control, provenance, tamper evidence, audit bundles, compliance, retention, and PII handling are all present. There are no obvious dead ends or missing lifecycle operations for the stated purpose.

Maintenance

ActivityActive
ResponsivenessSlow

Resources