INTEGRATIONS + MCP
Put verified company facts inside the systems that generate them.
Connect an AI model, agent or workflow to CompanyProof company search, profile retrieval and claim verification. Read tools return company context; the verification tool preserves a proof and can keep watching facts afterwards.
SERVER URL
https://companyproof.ai/v2/mcp- Authorization
Bearer cp_live_…- Tools
3 typed tools- Transport
- Streamable HTTP
AUTOMATE YOUR WORK FOR AGENTS
Give every agent a company context and proof step.
Use MCP or REST to resolve the entity, retrieve a consolidated profile and verify consequential claims. Both routes use the same CompanyProof key; REST requests and MCP tool calls share its rate limit.
- Keep keys in a server-side secret
- Use one stable idempotency key per verification
- Require approval before credit-consuming calls
{
"mcpServers": {
"companyproof": {
"type": "http",
"url": "https://companyproof.ai/v2/mcp",
"headers": {
"Authorization": "Bearer ${COMPANYPROOF_API_KEY}"
}
}
}
}Use this shape in any Streamable HTTP MCP client that supports custom authorization headers.
THREE USEFUL FLOWS
Verify at the moment a fact becomes consequential.
Pre-publication gate
Check the company facts in an answer before users see it.
In-agent verification
Let an agent resolve the entity and return claim-level verdicts.
Stale-claim alert
Monitor verified claims and route signed change events back to your system.
THREE IMPLEMENTED TOOLS
A small, typed contract for company context and proof.
The MCP server exposes the same CompanyProof envelopes as REST, with accurate read/write annotations.
search_companiesREAD + OPEN WORLDINPUT
Company name, registration number or VAT/tax ID plus jurisdiction.
RETURNS
Ranked CompanyProof matches with identifiers and evidence metadata.
NEXT
Pass the opaque ID to get_company_profile, another read-only tool.
SECURE BY DEFAULT
Credentials stay with the calling system.
Server-side keys
Pass the key as an authorization header. Never embed it in browser code or a public repository.
Normal account controls
MCP tool calls use the same rate limits, claim credits and plan permissions as the REST API.
Immediate revocation
Rotate or revoke an exposed key from the CompanyProof account console.
CHATGPT CONNECTOR
Header-based clients work now. OAuth sign-in comes next.
A direct ChatGPT connector requires OAuth and is not yet offered. The bearer-protected endpoint works with API clients and MCP hosts that support a custom authorization header.
Request connector access →START WITH THE DOCUMENTED SAMPLE