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