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