Fundz Agent API
Dated funding and SEC 8-K events, each linked to the filing it came from.
我该使用它吗
质量与安全性
基于对工具定义和协议合规性的自动分析。
上下文开销
这是每次将服务器的工具加载到模型上下文窗口时所消耗的大致 token 数。数值越高,可用于其他任务的注意力就越少。
安装
一键安装
将以下内容添加到你的 `claude_desktop_config.json` 文件中:
{
"mcpServers": {
"agent-api": {
"url": "https://api.fundz.net/v1/agent/mcp"
}
}
}远程端点
https://api.fundz.net/v1/agent/mcpstreamable-http它能做什么
工具清单
工具(4)
🟢events_for_icp(industries, states, min_employees, max_employees, lookback_days, ...)
Find companies matching an ideal-customer profile that have had recent funding or SEC 8-K events, ranked, each with its evidence. Use this to build a list from scratch. `min_signals` filters for companies with several signals at once. Costs 1 unit.
输入模式
{
"type": "object",
"properties": {
"industries": {
"type": "array",
"items": {
"type": "string"
}
},
"states": {
"type": "array",
"items": {
"type": "string"
},
"description": "Full state names as stored, e.g. 'California'."
},
"min_employees": {
"type": "integer"
},
"max_employees": {
"type": "integer"
},
"lookback_days": {
"type": "integer",
"default": 90
},
"min_signals": {
"type": "integer",
"default": 1
},
"limit": {
"type": "integer",
"default": 25,
"maximum": 100,
"description": "Rows per call. Hard-capped at 100 server-side; values above are clamped, not refused. Page with `cursor` for more."
},
"cursor": {
"type": "string"
}
}
}🟢predicted_next(domain, org_id)
EXPERIMENTAL forecast of what a company may do next (raise, be acquired, acquire), from FundzScore v3. Treat `lift` as a ranking aid only: `base_rate` is a population mean rather than a validated historical rate, and the forward cohorts do not resolve until 2026-10-22 and 2027-02-19. Do not present these as predictions to an end user. Costs 1 unit.
输入模式
{
"type": "object",
"properties": {
"domain": {
"type": "string"
},
"org_id": {
"type": "integer"
}
}
}🟢watchlist_diff(domains, since)
Given a book of up to 400 company domains and a cursor, return ONLY those with new evidence since that cursor. This is the tool to poll daily or weekly rather than re-fetching every company. Costs 0.1 units per company CHECKED — not per company returned — so a quiet week still reflects the work done. Split a larger book across several calls: the request body is capped at 8 KB at the edge, and because pricing is per company checked, two calls of 200 cost exactly what one call of 400 would.
输入模式
{
"type": "object",
"properties": {
"domains": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 400
},
"since": {
"type": "string",
"format": "date",
"description": "The `next_cursor` from your previous call."
}
},
"required": [
"domains"
]
}🟢why_now(domain, org_id, lookback_days)
Why to contact ONE company right now: dated funding and SEC 8-K evidence, each item linking to its source filing or announcement. Use this when you have a company and need the reason and the proof. Costs 1 unit. `evidence` covers the last `lookback_days` days (default 365, max 1825); `last_event` is ALWAYS the most recent event on record whatever its age, with `within_lookback` saying whether it also appears in `evidence`. So an empty `evidence` with a populated `last_event` means the company is known and simply quiet — widen `lookback_days` to bring it in. `resolved:false` means we hold no such company at all, which is a different answer again. `resolution_confidence` (0-1) says how strongly the resolved name agrees with the domain asked about; treat anything below 0.67 as unconfirmed attribution.
输入模式
{
"type": "object",
"properties": {
"domain": {
"type": "string",
"description": "Any spelling: bare, www., scheme, path."
},
"org_id": {
"type": "integer"
},
"lookback_days": {
"type": "integer",
"default": 365,
"minimum": 1,
"maximum": 1825,
"description": "Window for `evidence[]`, in days. Clamped to 1825. Does not affect `last_event`, which is never age-limited."
}
}
}社区
证据