Skip to main content
Glama
Sign In
wiki.mcp

wiki.mcp

by ccancellieri
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to wiki.mcp

No user-submitted related servers found.

    Related Servers

    • mcp-hyperspace-memory

      mcp-hyperspace-memoryofficial

      YARlabs
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to store, semantically recall, update, forget, consolidate, and verify persistent memories with session isolation and hyperbolic concept navigation. It also supports knowledge-graph linking and claim verification for anti-hallucination workflows.
      16
      426 npm
      MIT

    • context-m

      ssmurfgg04-gif
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to use a neuro-symbolic memory fabric with bi-temporal knowledge graph and holographic VSA, providing tools for adding, searching, temporal queries, auditing, and proving memories with cryptographic provenance and zero-LLM ingest.
      2
      Apache 2.0

    • ProofGraph

      AI-BuildInfra
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to retrieve compact, evidence-backed knowledge graph packets, verify claims against sourced provenance, trace cryptographic audit trails, and explore entity relationships while minimizing context token usage.
      12
      13 npm
      1
      MIT

    • CiteAnything MCP Server

      veriglow
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create verifiable, replayable citations, search private knowledge bases, and publish Markdown with verified citation markers.
      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.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct action: search (FTS retrieval), navigate (depth-projected tree read), crawl_delta (indexing), verify_citation (validation), record_episode (write/append). The only mild overlap is search vs. navigate, since both are retrieval paths, but the descriptions (FTS5 vs. Merkle-tree depth projection) give an agent enough signal to choose correctly.

    Naming Consistency5/5

    All five tools follow a strict wiki_<verb>_<noun> pattern (wiki_search, wiki_navigate, wiki_crawl_delta, wiki_verify_citation, wiki_record_episode). The prefix and snake_case style are consistent, so the set is predictable and easy to scan.

    Tool Count5/5

    Five tools is well within the ideal 3-15 range for a knowledge-base server, and each one maps to a distinct lifecycle stage (retrieve, project, index, verify, record). No obvious filler or redundant tools are present.

    Completeness3/5

    The surface covers read/search, indexing, citation verification, and episode recording, but there is no page-level write path: no create/update/delete of a note or branch, and no listing or backlink operation. An agent that needs to author or correct content would hit a dead end and have to fall back to raw content delivery.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources