readRunEmail — Riskcovery MCP Tool
readRunEmail
(read run email) is one of 33 tools on the
Riskcovery
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call readRunEmail from your client
- Claude Code Riskcovery readRunEmail run in your project directory
- Claude Desktop Riskcovery readRunEmail ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Riskcovery readRunEmail ~/.cursor/mcp.json
- VS Code Riskcovery readRunEmail .vscode/mcp.json
- Zed Riskcovery readRunEmail ~/.config/zed/settings.json
- Windsurf Riskcovery readRunEmail ~/.codeium/windsurf/mcp_config.json
- Cline Riskcovery readRunEmail ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Riskcovery readRunEmail ~/.gemini/settings.json
- Grok Riskcovery readRunEmail .mcp.json (in your project root)
- ChatGPT Riskcovery readRunEmail Settings → Connectors → Advanced → Developer mode
- Claude.ai Riskcovery readRunEmail Settings → Connectors → Add custom connector
- LangChain Riskcovery readRunEmail pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://www.riskcovery.com/api/mcp
Other tools on this server
- sites
- review
- runs
- listIssues
- listLatestIssues
- report
- addSite
- readSiteVerification
- confirmSiteVerification
- deleteSite
- readAgreement
- acceptAgreement
- revokeAgreement
- listShareLinks
- createShareLink
- revokeShareLink
- listTeams
- createTeam
- teamDeletionLink
- listMemberInvitations
- memberInvitationsLink
- readInvitation
- readTeamBilling
- billingLink
- listPlans
- listApiKeys
- createApiKey
- revokeApiKey
- setRunEmail
- reportProblem
- listCves
- readCve
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.