dpp_readiness_check — AuthiChain MCP Tool
dpp_readiness_check
(dpp readiness check) is one of 4 tools on the
AuthiChain
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call dpp_readiness_check from your client
- Claude Code AuthiChain dpp_readiness_check run in your project directory
- Claude Desktop AuthiChain dpp_readiness_check ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AuthiChain dpp_readiness_check ~/.cursor/mcp.json
- VS Code AuthiChain dpp_readiness_check .vscode/mcp.json
- Zed AuthiChain dpp_readiness_check ~/.config/zed/settings.json
- Windsurf AuthiChain dpp_readiness_check ~/.codeium/windsurf/mcp_config.json
- Cline AuthiChain dpp_readiness_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AuthiChain dpp_readiness_check ~/.gemini/settings.json
- Grok AuthiChain dpp_readiness_check .mcp.json (in your project root)
- ChatGPT AuthiChain dpp_readiness_check Settings → Connectors → Advanced → Developer mode
- Claude.ai AuthiChain dpp_readiness_check Settings → Connectors → Add custom connector
- LangChain AuthiChain dpp_readiness_check pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http authichain https://authichain.com/mcp
Other tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 27 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.