Company intelligence.
Inside your AI workflow.

Connect your AI client

1. Open the integrations or connectors settings in a client that supports remote MCP connections.
2. Add a custom MCP connection. Enter https://mcp.globaldatabase.com/mcp as the server URL.
3. Complete the connector’s authentication flow with your Global Database API key.
4. Confirm the connection is available and review the company-data tools it exposes.
5. Start a conversation and ask a focused company research question.

MCP access and data entitlements are provisioned separately. EntityReach’s website search allowance does not define your MCP quota. Confirm permitted datasets and usage as part of your Enterprise access setup.

Available company-data tools

These are the five tool categories listed in the provider’s MCP reference. The labels below describe capabilities; your connected client supplies the exact callable tool names and input schemas.

Available fields and results depend on company coverage and account permissions. Inspect the current tool list after connecting; this page does not assert undocumented machine-readable tool names.

Start with a clear company identity

Give your assistant a company name and country, a registration number, or a website or LinkedIn company URL. The provider also supports company identifiers such as VAT number, ticker and email. These are lookup inputs, not a promise that every tool accepts the same argument names.

Find the legal entity behind tesco.com.
Confirm its company name, country and registration number
before retrieving its corporate group.

For ambiguous results, confirm the intended legal entity before continuing. Keep the provider company ID with the research so later tool calls refer to the same company.

Prompts for account expansion

Use these in sequence after connecting. The later prompts rely on research already present in the conversation. Replace the customer, offering and territory with your own context.

Our customer is Tesco PLC in the UK, registration number 00445790. First confirm the legal entity. Then use the available company tools to map its parent, subsidiary and sister-company relationships. Return company identifiers, countries and the relationship evidence where available. Flag ambiguous matches and missing data.

Using the verified group from our previous research, assess potential expansion for workforce scheduling software in the UK and Ireland. Separate companies within territory from those outside it. For each candidate, distinguish sourced company facts from a possible product-fit hypothesis. Do not assume the company needs our software or is covered by our existing contract.

For the shortlisted companies, retrieve the available financial and employee data. Show reporting periods, currencies and sources. Explain what the data can tell us about company scale and what we still need to learn from the account owner. Treat missing data as unavailable, not zero.

Create an account expansion brief from the verified research in this conversation. Include the existing customer, candidate companies, corporate connections, territory fit, evidence, open questions and recommended next actions. Keep confirmed facts separate from assumptions. Do not claim a revenue opportunity is qualified until the account owner validates need and contract coverage.

Use MCP from your own agent

Use a maintained MCP client implementation that supports the server’s authentication and protocol version. The provider setup page does not declare a fixed protocol revision; let the client handle compatibility and transport details.

1. Connect with the account’s approved credentials.
2. Discover tools using tools/list. Follow pagination when the response includes nextCursor.
3. Use the returned name and validate inputs against inputSchema.
4. Call the selected tool through tools/call, then inspect the result before adding it to the account research.

The JSON below illustrates method payloads. It is not a ready-to-send HTTP request or a client configuration file. Your MCP client supplies authentication, protocol metadata and any required connection lifecycle.

{
  "method": "tools/list",
  "params": {}
}

{
  "method": "tools/call",
  "params": {
    "name": "TOOL_NAME_FROM_TOOLS_LIST",
    "arguments": {}
  }
}

Replace TOOL_NAME_FROM_TOOLS_LIST with a discovered name and populate arguments according to that tool’s schema. An empty object is only valid when the tool accepts it.

Protocol references: tool discovery and results · version compatibility. Use the revision supported by your client and server.

Choose the right integration

The downloadable OpenAPI file describes REST APIs. MCP tools are discovered through the MCP connection and are documented separately on this page.

When something needs attention