Private Company Funding History MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token from console.apify.com/account/integrations. The server lists its tool without a token, but a tool call requires one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_company_funding_historyA | Look up private US companies on SEC EDGAR by legal name or CIK and return their funding history: one company row (offerings on file, total and largest Form D amount sold, first and latest filing, executives) plus one row per Form D private placement or Form C crowdfunding offering (amount offered and sold, first sale date, security types such as equity or SAFE, investor count, crowdfunding platform, filing link). Primary SEC filings only; rounds raised outside Regulation D and Regulation CF are not on EDGAR. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of misselection or overlap. The tool's scope (SEC EDGAR funding lookup) is stated explicitly in its name and description.
The single tool follows a clear verb_noun snake_case convention (get_company_funding_history) that describes exactly what it returns. There is no competing convention to conflict with.
One tool is thin for a general-purpose server, but here the domain is narrow and the tool bundles company-level and offering-level data in a single call, so it earns its place. Splitting into separate company/offering lookups would arguably add complexity without benefit.
The tool covers both the entity summary and the per-offering detail (Form D and Form C), including amounts, dates, security types, and filing links, which is the full lifecycle for this read-only domain. Minor gaps: no batch or multi-company comparison, and the description notes Reg D/CF-only coverage as an inherent EDGAR limitation.