web3-docs
Related Servers
Alternatives to web3-docs
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables AI coding agents to query a fully local SQLite FTS5 memory index of a codebase, returning high-density identity cards with exact line references, AST symbol contracts, phase maps, and colloquial intent search so agents can work without scanning raw files. It also supports incrementally syncing code changes and enriching knowledge under a six-pillar quality gate, keeping everything on-device with no cloud leakage.5MIT
- AlicenseNot gradedqualityCmaintenanceCrypto-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.46 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to index local codebases into isolated SQLite FTS5 databases and search them for ranked file paths, line ranges, and highlighted snippets, reducing context spent opening whole files.31MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search locally indexed documentation entirely offline, resolving libraries and retrieving relevant Markdown fragments under a token budget through SQLite FTS5 full-text search. Docs never leave the machine, with no API keys or cloud dependencies.1MIT
- AlicenseNot gradedqualityDmaintenanceProvides 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.3MIT
- AlicenseAqualityBmaintenanceThe 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.8367 PyPI27MIT
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of Web3 documentation: forks, proposal discovery, proposal reading, and contract addresses. No overlap in functionality.
All tools follow a consistent verb_noun pattern with underscores (e.g., list_fork_proposals, resolve_proposal), making them predictable and easy to understand.
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.
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.