INTEGRATIONS + MCP

A company data MCP server for Claude and AI workflows.

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.

Connect CompanyProof to Claude Create an API key

ONE ENDPOINT / YOUR CLIENTPublic beta

Claude

CompanyProof OAuthConnect your account

COMPANYPROOF MCPhttps://companyproof.ai/v2/mcp

Add the remote server in Claude, sign in to CompanyProof and review the permissions requested by the connector.

Follow the Claude setup

REST APILive

Signed webhooksLive

MCP endpointPublic beta

ChatGPT connectorOAuth live

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. ChatGPT connects to MCP with OAuth; REST and custom MCP clients use CompanyProof API keys. The same account rate, Stripe-period usage and plan controls apply; billing-suspended live credentials return payment-required until recovery, then resume automatically.

Use OAuth in ChatGPT; never paste an API key there
Keep REST and custom-client keys in a server-side secret
Use one stable idempotency key per verification
Require approval before credit-consuming calls

mcp.json

{
  "mcpServers": {
    "companyproof": {
      "type": "http",
      "url": "https://companyproof.ai/v2/mcp",
      "headers": {
        "Authorization": "Bearer ${COMPANYPROOF_API_KEY}"
      }
    }
  }
}

This is a configuration shape, not universal client syntax. Use it only with a Streamable HTTP MCP client that supports custom Authorization headers, and replace the placeholder through that client's secure secret-substitution mechanism.

Select an example for your integration.

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.

MODEL / AGENTCompany answer

→

MCP TOOLSSearch · profile · verify

→

COMPANYPROOFContext + verdicts

→

OPTIONALProof monitoring

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 WORLD

INPUT

Company name, registration number or VAT/tax ID plus jurisdiction.

RETURNS

Ranked CompanyProof matches with identifiers and evidence metadata.

Pass the opaque ID to get_company_profile, another read-only tool.

SECURE BY DEFAULT

Use the right authorization path for each client.

OAuth for ChatGPT

Connect the CompanyProof MCP URL and complete OAuth sign-in. Do not paste an API key into ChatGPT.

Normal account controls

MCP tool calls use the same rate limits, claim credits and plan permissions as the REST API.

Keys for custom clients

REST and custom MCP clients may use a CompanyProof bearer API key kept in a secure secret store.

CHATGPT CONNECTOR

Connect directly with CompanyProof OAuth.

Add https://companyproof.ai/v2/mcp as the remote MCP server in ChatGPT, then complete CompanyProof OAuth sign-in. Discovery and tool listing are public; tool calls request company.read for search and profiles or proof.write for verification.

Open the connection guide →

START WITH THE DOCUMENTED SAMPLE

Connect one model to one verifiable company claim.

Create an API key Read the MCP reference →

FROM DISCOVERY TO A FIRST RESULT

Resolve the company. Keep the evidence.

CompanyProof's company data MCP server exposes three tools: search_companies, get_company_profile and verify_company_claims. Resolve the intended legal entity, retrieve its available profile modules, then compare supported claims with the source evidence.

Discovery is public. Data calls require account authentication and the relevant entitlement. Accepted live searches and profiles each use one shared credit; verification uses credits per accepted claim and can write a proof. Review cost and permissions before enabling an agent workflow.

Developer resources

Markdown quickstart · OpenAPI contract · MCP server metadata · Capability summary · Runnable REST example

See a dated registry evidence example →

CLAUDE CUSTOM CONNECTOR

How to add CompanyProof MCP to Claude.

Server URL: https://companyproof.ai/v2/mcp

CompanyProof exposes company search, company profiles and claim verification through a remote Model Context Protocol (MCP) server. Claude can use these tools after you connect your CompanyProof account through OAuth.

Start on CompanyProof. Sign in and review your account access. Real-company requests need an eligible live evaluation or paid live plan.
Add the server in Claude. Open Customize → Connectors → + → Add custom connector. Name it CompanyProof and enter https://companyproof.ai/v2/mcp, then select Add.
Connect your account. Choose Connect, sign in to CompanyProof when prompted and review the requested permissions. OAuth handles the connection; you do not paste an API key into the chat.
Enable it in a conversation. Use the conversation’s + menu and Connectors to enable CompanyProof. Ask Claude to search for the company, confirm the registration number and retrieve its profile.

For Claude Team and Enterprise, an owner first adds the remote server in Organization settings → Connectors → Add → Custom → Web. Members then connect their own accounts. See Claude’s current custom connector instructions.

Try a specific research request

“Find the company matching this legal name and registration number in GB. Retrieve its profile and show the source context and any unavailable modules before drawing a conclusion.”

CompanyProof MCP is in public beta. For clients that support custom headers, use a scoped Bearer API key instead. The MCP reference covers tool behavior, scopes and error handling.

CHOOSE THE CONNECTION

One company-data workflow, several entry points.

CompanyProof integration options
Client	Connection	Start here
Claude web or desktop remote connector	Hosted MCP with account OAuth	Claude setup steps
Claude Code or another compatible MCP client	Streamable HTTP; supported OAuth or custom Bearer headers	MCP protocol and tools
Enterprise application	Server-side REST requests with a scoped API key	Company profile quickstart

Verification creates a proof and consumes credits. Keep user approval enabled where the client supports it and inspect the response before using a claim in a decision.

FREQUENTLY ASKED QUESTIONS

CompanyProof API and MCP integration FAQs

How can I integrate CompanyProof into an AI application?

Use the REST API from your application backend or connect a compatible MCP client. Both routes expose supported company operations, with authentication, billing and usage controls applying to the account.

What is the CompanyProof MCP server URL?

The Streamable HTTP MCP endpoint is https://companyproof.ai/v2/mcp. Use the integration instructions for your client and complete the appropriate authentication before calling protected tools.

How do I connect CompanyProof to ChatGPT?

Add the CompanyProof MCP endpoint in a supported ChatGPT connector flow and complete CompanyProof OAuth sign-in and consent. Do not paste a CompanyProof API key into ChatGPT.

Read the MCP setup guide

Can a custom MCP client use a CompanyProof API key?

Yes. Compatible custom MCP clients can send a CompanyProof bearer API key. ChatGPT uses OAuth instead. Test and live key restrictions, tool permissions and account limits still apply.

Which operations are available through CompanyProof MCP?

The documented tools include company search, company profile retrieval and company-claim verification. Tool discovery describes the current input schemas; extended data remains subject to coverage and commercial rights.

Can I use CompanyProof with Claude Code or LangChain?

The integration hub provides patterns for compatible agent and application clients, including Claude Code and LangChain. Use the supported HTTP or REST interface and keep credentials in server-side configuration.

Do REST and MCP calls share the same allowance?

Yes. Account credit and rate controls apply across the supported interfaces. Search and profile calls consume credits even when described as read-only; verification is metered by accepted claims.

How do I check whether an MCP tool call failed?

Inspect both the transport response and the MCP result. A completed exchange can contain an error result, so clients must handle authentication, billing, rate limits and operation errors explicitly.

Can an AI agent create company verification proofs?

The verify_company_claims tool writes a proof and consumes claim credits. Configure the agent’s permissions and budget policy for this action rather than treating verification as an unrestricted background read.

Can CompanyProof notify my application when facts change?

Eligible monitored claims can send signed webhooks to a configured endpoint. Your application should validate signatures, process events idempotently and decide whether the change requires correction or review.

See the evidence lifecycle