pep_screen — CompanyVerify MCP Tool
pep_screen
(pep screen) is one of 21 tools on the
CompanyVerify
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call pep_screen from your client
- Claude Code CompanyVerify pep_screen run in your project directory
- Claude Desktop CompanyVerify pep_screen ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CompanyVerify pep_screen ~/.cursor/mcp.json
- VS Code CompanyVerify pep_screen .vscode/mcp.json
- Zed CompanyVerify pep_screen ~/.config/zed/settings.json
- Windsurf CompanyVerify pep_screen ~/.codeium/windsurf/mcp_config.json
- Cline CompanyVerify pep_screen ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CompanyVerify pep_screen ~/.gemini/settings.json
- Grok CompanyVerify pep_screen .mcp.json (in your project root)
- ChatGPT CompanyVerify pep_screen Settings → Connectors → Advanced → Developer mode
- Claude.ai CompanyVerify pep_screen Settings → Connectors → Add custom connector
- LangChain CompanyVerify pep_screen pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http companyverify https://api.companyverify.uk/mcpOther tools on this server
- uk_company_search
- uk_company_profile
- lei_lookup
- sanctions_screen
- entity_match
- counterparty_evidence
- uk_psc_ubo
- cross_registry_resolve
- adverse_media
- uk_director_changes
- uk_insolvency_notices
- fca_register_check
- kyb_verdict
- vessel_sanctions
- uk_procurement_awards
- eu_vat_check
- registry_doc_fetch
- charge_register
- find_capability
- request_data
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.