Zephira Company Intelligence

npx add-mcp 'https://dashboard.zephira.ai/api/mcp'

Connect with your dashboard API key

In your MCP client, add a remote server using Streamable HTTP and the following URL:

https://dashboard.zephira.ai/api/mcp

Add your active production API key in the client’s secure authentication settings:

Authorization: Bearer YOUR_ZEPHIRA_API_KEY

Create or manage keys in the Zephira dashboard. Use a zph_live_ key with the scopes required by your tools. Clients must support a Bearer authorization header. No separate MCP access request is required.

Six company-data tools

Tool	Returns	Key scope
search_entities	Companies matching a name or identifier in a jurisdiction.	company:read
get_entity	Company identity and available profile fields.	company:read
get_officers	A page of available company officers.	company:read
get_shareholders	A page of available company shareholders.	ownership:read
get_corporate_hierarchy	The available company group structure.	ownership:read
get_financials	Available financial statements.	financials:read

Coverage varies by company and jurisdiction. Preserve source and modelled-data labels when displaying results. Missing data does not prove that a fact does not exist.

Search first, then retrieve a company

Call search_entities with a location and at least one of name, registration_number, vat_number or ticker.

{
  "name": "search_entities",
  "arguments": {
    "location": "GB",
    "name": "Tesco",
    "include_provenance": true
  }
}

Use a numeric company ID returned by the search as a string in entity_id. The ID below is illustrative; replace it with your search result.

{
  "name": "get_entity",
  "arguments": {
    "entity_id": "123",
    "include_provenance": true
  }
}

All retrieval tools accept entity_id and optional include_provenance (default true). Officers and shareholders also accept page (default 1) and per_page (default 10, maximum 50). Search accepts an optional city_or_state array.

Successful tool results provide the API payload under data, with meta.request_id, meta.status, meta.units and meta.remaining_units. Results are available as both text and structured content.

Protocol and client compatibility

The endpoint supports MCP 2026-07-28 and the stateless legacy Streamable HTTP flow. Current clients use server/discover; older clients use initialize, followed by notifications/initialized. Both can then use tools/list and tools/call.

For a direct request using the current protocol, include the per-request metadata and matching HTTP headers. MCP client libraries normally supply these automatically.

curl https://dashboard.zephira.ai/api/mcp \
  -H "Authorization: Bearer $ZEPHIRA_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/list' \
  --data '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientInfo": {
          "name": "my-client", "version": "1.0.0"
        },
        "io.modelcontextprotocol/clientCapabilities": {}
      }
    }
  }'

For tools/call, set Mcp-Method: tools/call, add Mcp-Name matching the tool name, and include name and arguments beside _meta in params. Discovery and tool listing do not consume data credits.

This endpoint provides tools. It does not provide prompts or resources, and does not require a persistent session ID. Modern replies use JSON; legacy clients must also accept text/event-stream.

Usage and troubleshooting

Successful data calls consume one unit from the same workspace allowance as the dashboard API. API-key scopes, revocation and allowance limits apply to every tool call. Failed data requests are not charged.

Response	What to check
401 UNAUTHENTICATED	Supply an active dashboard API key using Authorization: Bearer.
403 INSUFFICIENT_SCOPE	Use or create a key with the tool’s required scope.
429 ALLOWANCE_EXHAUSTED	Review the workspace’s remaining allowance in the dashboard.
Invalid tool arguments	Use the schema returned by tools/list; pass numeric company IDs as strings.
Protocol or header error	Match the protocol metadata and Mcp-Method / Mcp-Name headers to the request body.
Data-service error	Check the tool result’s error and request ID. Retry temporary failures with backoff.

Tool execution failures return isError: true, an error object and request metadata inside the MCP result. Use the request ID when contacting support.

REST API reference · Contact support