MCP
A live MCP server at aidealigence.com/mcp — works with or without a trailing slash, authenticated with the same API key as the REST API. Eight tools, thin wrappers over the same research engine — no separate contract to learn.
{
"mcpServers": {
"ai-dealigence": {
"url": "https://aidealigence.com/mcp",
"headers": {
"Authorization": "Bearer dl_live_xxx"
}
}
}
}{
"mcpServers": {
"ai-dealigence": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://aidealigence.com/mcp",
"--header", "Authorization: Bearer dl_live_xxx"
]
}
}
}{
"mcpServers": {
"ai-dealigence": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://aidealigence.com/mcp",
"--header", "Authorization: Bearer dl_live_xxx"
]
}
}
}Small and specific rather than one do-everything call — a model can reason about when to use each one.
resolve_objective
Find the people most capable of achieving a business objective.
objective (string, required), location (string, optional), max_results (integer, default 5)
find_decision_maker
Find the most relevant decision maker inside a specified company.
company (string, required), objective (string, required)
resolve_company
Find companies relevant to a business objective.
objective (string, required), market (string, optional)
resolve_function
Determine which organisational function owns an objective.
objective (string, required), company (string, optional)
verify_person
Verify whether a person currently holds a specified role.
person_id (string, required)
get_evidence
Retrieve the evidence behind a recommendation.
evidence_id (string, required)
find_access_route
Find a legitimate route to reach the recommended person.
person_id (string, required)
compare_targets
Compare several candidates by relevance, authority, and access.
person_ids (array of strings, required)
Auth today is a bearer API key, the same one the REST API uses — a working model, not a placeholder. Full OAuth 2.1 authorization (client registration, delegated end-user consent) is the documented next step once there’s a concrete reason to need it.
A tool call that fails returns a real MCP tool error (is_error: true on the result, not a bare crash) with the same structured error body the REST API uses — see the error codes for what each one means. A malformed request to the server itself (missing headers, invalid JSON-RPC) returns a standard JSON-RPC error object instead, before any tool even runs.
401/403 almost always means the Authorization header didn’t reach the server — check your client config passes it exactly as shown above, and that a bridge process like mcp-remote is actually forwarding --header rather than dropping it.