verify_certificate — agent offset clearinghouse MCP Tool
verify_certificate
(verify certificate) is one of 19 tools on the
agent offset clearinghouse
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call verify_certificate from your client
- Claude Code agent offset clearinghouse verify_certificate run in your project directory
- Claude Desktop agent offset clearinghouse verify_certificate ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent offset clearinghouse verify_certificate ~/.cursor/mcp.json
- VS Code agent offset clearinghouse verify_certificate .vscode/mcp.json
- Zed agent offset clearinghouse verify_certificate ~/.config/zed/settings.json
- Windsurf agent offset clearinghouse verify_certificate ~/.codeium/windsurf/mcp_config.json
- Cline agent offset clearinghouse verify_certificate ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent offset clearinghouse verify_certificate ~/.gemini/settings.json
- Grok agent offset clearinghouse verify_certificate .mcp.json (in your project root)
- ChatGPT agent offset clearinghouse verify_certificate Settings → Connectors → Advanced → Developer mode
- Claude.ai agent offset clearinghouse verify_certificate Settings → Connectors → Add custom connector
- LangChain agent offset clearinghouse verify_certificate pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-offset-clearinghouse https://mcp.viridisconservation.com/offsets/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 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.