Skip to main content
Glama

Related Servers

Alternatives to web3-docs

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Crypto-aware project memory for AI coding agents. Typed entities for Solana Programs/PDAs and EVM Contracts across Base, Optimism, Polygon, Arbitrum, Ethereum — plus chain-agnostic Decisions, Findings, and Integrations. Anchor + Hardhat auto-ingest, SQLite + FTS5 BM25 ranking, append-only versioning, git-aware diffs.
      30 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides intelligent code indexing with 15 MCP tools for symbol extraction, hybrid search (FTS5+vector), call graphs, and incremental indexing of local folders and remote repos, enabling token-efficient code retrieval for AI agents.
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      The open retrieval layer for AI agents. Index your entire project — code, docs, legal, research, data — and serve surgical context via MCP. FTS5 full-text search, optional semantic search (FastEmbed/ONNX), 10 built-in parsers, incremental auto-sync.
      8
      574 PyPI
      24
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides fast, token-efficient search over coding agent documentation (e.g., Claude Code, Cursor) using local SQLite FTS5 indexing, with tools for searching snippets, reading pages, and grepping markdown.
      5
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local index and hybrid search (SQLite FTS5 + on-device vector KNN) over your AI coding-agent conversation history across 11 tools (Claude Code, Codex, Cursor, and more). Exposes search_threads, search_current_project, recent_threads, get_thread, list_tags, and list_open_todos so any agent can recall its own past work.
      22
      39
      AGPL 3.0

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of Web3 documentation: forks, proposal discovery, proposal reading, and contract addresses. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., list_fork_proposals, resolve_proposal), making them predictable and easy to understand.

    Tool Count5/5

    Four tools is a compact yet complete set for the server's purpose—covering fork proposals, proposal search/reading, and contract resolution—without unnecessary bloat.

    Completeness5/5

    The tool surface covers the full workflow: find proposals (resolve_proposal), read them (query_protocol_docs), list fork contents (list_fork_proposals), and look up deployed contracts (resolve_contract). No obvious gaps for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues