OpenZeppelin Docs MCP Server
Related Servers
Alternatives to OpenZeppelin Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to generate and retrieve secure, audited smart contract templates from OpenZeppelin including ERC20, ERC721, ERC1155 tokens, access control, governance, and finance contracts through natural language prompts.MIT
- AlicenseAqualityCmaintenanceUnifies 11 protocol specification repositories (EIPs, BIPs, CIPs, etc.) and canonical contract addresses across 10 chains into a local FTS5 index, enabling coding agents to retrieve exact spec text and contract addresses via natural language queries.436MIT
- AlicenseNot gradedqualityCmaintenanceEnables fast, offline search and retrieval of Expo documentation from local .mdx files, with tools for searching, getting content, listing sections, API references, and quick start guides.25 npm17MIT
- AlicenseAqualityCmaintenanceEnables offline, real-time search of Apple Developer Documentation from Xcode's local index, returning full text, code examples, availability, and framework listings without network calls.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI-optimized offline access to the Gravity UI design system, enabling natural language search and retrieval of components, hooks, utilities, and recipes.2MIT
- AlicenseAqualityDmaintenanceProvides instant access to authoritative security documentation from organizations like OWASP, NIST, and major cloud providers through natural language semantic search. It enables users to retrieve security best practices, frameworks, and vulnerability information directly from a locally cached knowledge base.41MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: get_oz_contract retrieves contract-level details, get_oz_function focuses on specific functions, list_oz_modules provides a catalog, oz_index_status checks system readiness, and search_oz_docs performs general documentation searches. There is no overlap in functionality, making tool selection straightforward for an agent.
All tools follow a consistent snake_case naming pattern with clear verb_noun structures: get_oz_contract, get_oz_function, list_oz_modules, oz_index_status, and search_oz_docs. The 'oz' prefix is uniformly applied, and verbs like 'get', 'list', and 'search' accurately describe the actions, ensuring predictability across the set.
With 5 tools, this server is well-scoped for its purpose of accessing OpenZeppelin documentation. Each tool serves a distinct and necessary function, from indexing and searching to retrieving specific details, without being overly sparse or bloated, making it efficient for agents to navigate.
The tool set covers core documentation needs comprehensively, including listing, searching, and retrieving detailed information at both contract and function levels, with a status check for system readiness. A minor gap might be the lack of tools for updating or managing documentation, but this is reasonable for a read-only documentation server, and agents can perform all essential queries without dead ends.