DatahyenaDatahyena
MCP server

MCP server

Connect Datahyena to Claude, Cursor, and any MCP client and query signals in natural language.

Datahyena is available as an MCP server, so you can connect it to Claude, Cursor, Codex, Gemini, or any MCP-compatible client and query funding, acquisition, and executive-move signals in natural language. The tools mirror the REST API exactly. Available on every plan.

Server URL

https://api.datahyena.com/mcp

Transport is Streamable HTTP. Authentication is OAuth 2.1 with PKCE: your client opens a browser, you sign in and pick a workspace, and access is granted to that workspace. Revoke a connection any time from the dashboard.

Set up your client

Tools

Each tool maps one-to-one to a public API endpoint, with the same filters and the same response shape.

ToolReturns
funding_eventsFunding rounds. Filter by round, amount range, country, industry, or company.
acquisitionsAcquisition and merger events. Filter by payment type, deal amount, merger flag, or company.
exec_movesExecutive appointments, promotions, departures, and transitions.
companiesCompany records. Search by name, domain, country, industry, employee bucket, or founded year.
investorsInvestor records. Search by name, type, country, or domain.

Every tool returns the standard API envelope (success, data, pagination, meta), so you get the same records and cursor pagination as the REST endpoints.

Credits

MCP tool calls bill exactly like the API: one credit per record returned, charged only on success. If a workspace is out of credits, the tool returns an error instead of data, and a page is trimmed to what the balance covers. See Credits.

Scopes

Access is granted with read scopes, one per resource: read:funding, read:acquisitions, read:exec_moves, read:companies, read:investors. Approving the default connection grants all of them.

MCP tools are read-only. To receive signals as they are confirmed, use Webhooks; to pull on your own schedule, use the REST API.

On this page