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