01Getting Started
Sign up for a QORENEXT_API_KEY,
pick your client below, and paste the config in. First tool call in under 5 minutes.
{
"mcpServers": {
"qorenext-mcp": {
"url": "https://mcp.qorenext.com/mcp/",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}
# add the server via CLI claude mcp add --transport http qorenext-mcp \ "https://mcp.qorenext.com/mcp/" \ --header "X-API-Key: YOUR_API_KEY"
{
"mcpServers": {
"qorenext-mcp": {
"url": "https://mcp.qorenext.com/mcp/",
"headers": { "X-API-Key": "YOUR_API_KEY" }
}
}
}
You › Who owns Acme Trading Co.? → calls hierarchy_enrichment ✓ Parent, subsidiaries & verified address returned
02Tools
Your AI client reads these descriptions to decide which tool to call — you never call them directly.
| Tool | Auth | Description |
|---|---|---|
| health_check | Public | Verify the server is running, get version info. |
| submit_entities | API Key | Submit one or more companies for hierarchy analysis or address verification. Required per entity: entity name, country, address, screening type. Optional: crmid, website. |
| get_request_status | API Key | Poll a submitted request by ID. Status values: pending · processing · complete · failed. |
03Data We Return
What actually comes back from get_company_profile(), grouped by capability. Fields marked in development are on the roadmap and not yet populated in live responses.
Duplicate Check Cross-match against your existing CRM
| Field | Type | Example | |
|---|---|---|---|
| is_duplicate | boolean | false | In development |
| duplicate_of_id | string (nullable) | "CRM-10293" | In development |
Hierarchy Enrichment Parent, subsidiaries & ownership chain
| Field | Type | Example | |
|---|---|---|---|
| parent_id | object[] | "101" | Live |
| role_level | string | "Top Parent" | Live |
| entity_company_name | string | "A DAIGGER & CO" | Live |
| registered_address | string | "620 LAKEVIEW PKWY, SUITE 201..." | Live |
| registered_phone_no | string | "+1 (847) 621-7193" | Live |
Verification & Enrichment Address, industry codes, firmographics
| Field | Type | Example | |
|---|---|---|---|
| entity_company_name | string | "A DAIGGER & CO" | Live |
| address (full breakdown) | string | city, state, line 1/2, postal code | Live |
| registered_phone_no | string | "+1 (847) 621-7193" | Live |
| industry_codes | object | SIC "5040" · NAICS "423430" | Live |
| annual_revenue | number (currency) | $14,200,000 | In development |
| employee_count | number | 85 | In development |
| ticker_symbol | string (nullable) | "N/A" or "ACME:SGX" | In development |
| field_confidence_scores | object (0–100) | address: 95 · revenue: 70 | In development |
04Security & Trust
Every Qore MCP server shares one security architecture — the enterprise requirements most MCP servers skip.
Read-only by default
No write action runs without explicit approval.
Per-client keys
Each client gets a unique key, sent as a bearer/query token, validated server-side on every request.
Full audit trails
Every call is logged — who, what, when. Keys can be revoked instantly and stop working immediately.
Human-in-the-loop
Low-confidence outputs escalate for review rather than returning a silent guess.
05Roadmap
One MCP endpoint, growing over time — no need to reconnect or re-key as new servers come online.