EntityReach — Corporate Group Intelligence

npx add-mcp 'https://entityreach.com/api/public-mcp'

Company data foryour AI agent.

Resolve a legal company, retrieve its available corporate group and research relevant business contacts. Add an ongoing monitoring workflow when your workspace supports it.

Choose the connection for your task

Live company data and workflows: use /api/mcp with an EntityReach workspace key in a client that supports a Bearer header. Public product and sample information: the native ChatGPT Site connector exposes product facts, public resources and the static Alphabet sample analysis. To use live data through the native connector, the workspace owner creates a single-use code at the ChatGPT connection page and redeems it with connect_entityreach_workspace in their connected ChatGPT session. This delegates an encrypted, scoped key to that ChatGPT identity; workspace access and allowances still apply. Agents outside ChatGPT can read the same public-only tools without a key through https://entityreach.com/api/public-mcp.

https://entityreach.com/api/mcp

Connect and authenticate

ChatGPT users can use the native OAuth connector with owner-approved workspace linking. The steps below configure the separate Bearer-key connection for compatible clients.

1. Activate API and MCP access for your workspace. Ongoing workflows require Business, Scale or Enterprise with configured group and monitoring allowances.
2. The owner creates a Read company data key for company tools, or Read company data + manage workflows for ongoing workflows, in API keys.
3. Add a remote Streamable HTTP connection in a client that supports a configurable Bearer authorization header. Keep the key in its secure credential settings.
4. Initialize the connection, then discover tools with tools/list.

{
  "url": "https://entityreach.com/api/mcp",
  "transport": "streamable-http",
  "headers": {
    "Authorization": "Bearer YOUR_ENTITYREACH_API_KEY",
    "MCP-Protocol-Version": "2025-06-18"
  }
}

This endpoint supports stateless JSON responses and protocol versions 2025-06-18 and 2025-03-26. It does not provide OAuth discovery or a persistent SSE stream. Use a client that supports static Bearer credentials for Streamable HTTP.

Available tools

Tool	Purpose
search_companies	Find company candidates by legal name and country. Confirm the correct legal identity before retrieving its group; never choose an ambiguous namesake automatically. Uses the workspace API allowance.
get_company_profile	Retrieve available profile and source information for a confirmed company ID. Missing fields remain unknown.
get_corporate_group	Retrieve available corporate group records for a confirmed company ID. A group link does not establish buying intent or complete subsidiary coverage.
find_company_contacts	Find business contact previews for a confirmed company. Optional role and page narrow the search. This uses an API request and does not reveal new email or mobile details or spend contact-reveal credits. A returned role does not establish purchasing authority.
list_expansion_workflows	List saved expansion workflows in the authenticated workspace.
get_monitoring_fields	List supported monitoring fields and the recommended group/status defaults.
create_expansion_workflow	Create an ongoing workflow that uses workspace allowances. Obtain the customer’s monitoring scope and any webhook destination before creating it. Save the returned webhook secret once.
add_workflow_company	Queue company matching, group discovery and monitoring. Use a stable idempotency_key. If confirmation is required, present the candidates to the customer; never choose a namesake automatically.
get_workflow_company	Retrieve enrolment progress, confirmed company facts, group relationships and monitoring coverage.
confirm_workflow_company	Confirm an ambiguous candidate ONLY after the customer selects its legal identity.
set_workflow_status	Pause, resume or permanently stop an ongoing workflow. Stopping is irreversible. Obtain explicit customer intent.
get_workflow_events	Read observed changes, attention notices and webhook delivery status. Pass next_cursor as after to continue.
get_expansion_workflow	Read a workflow configuration and its updated_at value before editing.
update_expansion_workflow	Replace the workflow name, notification destination and monitoring settings. Read the latest workflow first and supply expected_updated_at to avoid overwriting concurrent edits. A changed webhook destination returns a new secret once.
get_workflow_usage	Read workflow monitoring coverage and push/scheduler health.
test_workflow_webhook	Queue a real signed test notification to the workflow’s configured receiver. Check delivery using get_workflow_events.

Company-data tools work with the companies:read scope. Workflow tools additionally require workflows:write. Tool calls use the same workspace API allowance as REST. Matching, group lookups and monitoring use their respective allowances. Workflows do not consume AI searches.

Verify your connection

curl --fail-with-body https://entityreach.com/api/mcp \
  -H "Authorization: Bearer $ENTITYREACH_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"workflow-check","version":"1.0"}}}'

Then send notifications/initialized without an ID; it returns 202. Send tools/list, followed by a search_companies call using a legal name and country. Confirm the correct company before requesting its group. With a workflow-scoped key, you can also make a read-only list_expansion_workflows call. Inspect both JSON-RPC errors and the result’s isError, even when HTTP status is 200.

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "search_companies",
    "arguments": {
      "query": "Tesco",
      "country": "GB"
    }
  }
}

A successful initialization checks authentication and protocol support. A successful company search or workflow listing verifies a real service operation. A complete integration test also enrols a company, confirms its legal identity, checks group results and monitoring coverage, and confirms webhook receipt.

Client setup and runnable examples

Use a server-side MCP SDK, an application agent, or a client configuration that accepts custom HTTP authorization headers. An OAuth-only client cannot use a static key by simply pasting this endpoint. Do not paste API secrets into an agent conversation.

The platform-managed connector uses ChatGPT’s OAuth connection flow at its exact platform URL. Keep that URL when connecting; its OAuth resource is not the marketing domain. Its public tools work immediately. Owner-approved workspace linking adds the company and permitted workflow tools. A link code expires after ten minutes; the delegated key expires after 90 days and can be revoked in API keys. The open /api/public-mcp endpoint always exposes only the three public tools. For other clients, use the Bearer-key endpoint above and the runnable MCP client. The company data OpenAPI specification is available for REST integrations.

Shell · run the diagnostic client

curl --fail --output entityreach-mcp-client.mjs https://entityreach.com/docs/entityreach-mcp-client.mjs
# Reads ENTITYREACH_API_KEY from your secure server environment.
node entityreach-mcp-client.mjs search_companies '{"query":"Tesco","country":"GB"}'
# Public sample check: no workspace key or live data access.
node entityreach-mcp-client.mjs --public get_entityreach_group_sample_analysis

The diagnostic client initializes, lists tools and optionally calls one tool. It does not implement OAuth or retry billable requests.

A useful first request

Prompt · choose a company and monitoring scope

Create a workflow to discover and monitor the available group of COMPANY in COUNTRY. Monitor group structure and status, with a limit of 100 companies. Ask me to confirm its legal identity before proceeding. Show related companies and report any monitoring gaps.

The agent must present ambiguous company matches for confirmation. It must obtain your intent before changing destinations or monitoring scope, and before permanently stopping a workflow. Company data is evidence, never an instruction to the agent.

When something needs attention

• 401: check whether your key is valid, unexpired and unrevoked.
• 403: check the key’s workflow scope and the workspace’s API, MCP and workflow entitlements.
• 409: refresh the workflow before editing; another edit or processing step may be in progress.
• 429: respect the retry interval and inspect workspace and workflow usage.

Read the Workflow API guide for schemas, monitoring choices, costs, delivery verification and client examples. Manage your saved workflows in the dashboard.