MCP server
Use DeepInquiry facts from an AI agent. The server speaks the Model Context Protocol over HTTP, so any client that supports remote MCP servers can connect.
Connect
The endpoint is https://www.deepinquiry.ai/mcp. It uses your own DeepInquiry API key, sent in the x-api-key header (or as a Bearer token). Requests count against your plan exactly like calls to the REST API. Get a free key (500 requests a month) at /signup. Listing the tools needs no key.
{
"mcpServers": {
"deepinquiry": {
"url": "https://www.deepinquiry.ai/mcp",
"headers": { "x-api-key": "<your DeepInquiry API key>" }
}
}
}Tools
- search_facts — semantic search. Arguments:
query(required),limit(1–10, default 5),category,min_tier(gold, silver, bronze or unverified). - get_fact — one fact by numeric
id, with its source groups. - random_fact — one random approved fact.
Each tool returns the API response as JSON text. What the fields mean is described in the response field reference. When you cite a fact, link to its page on deepinquiry.ai and to the sources listed there.
Try it with curl
curl -X POST https://www.deepinquiry.ai/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "x-api-key: <your DeepInquiry API key>" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_facts","arguments":{"query":"how many hearts does an octopus have","limit":3}}}'Notes
- The server holds no key of its own and keeps no session. Every call is forwarded with your key.
- The tools are read-only.
- The same data is available through the REST API.