Skip to main content
Glama
ProspectAPIs

prospectapis-mcp

Official
by ProspectAPIs
README.md
# prospectapis-mcp

prospectapis-mcp is the MCP server for ProspectAPIs, built for sales teams and their AI agents in Claude Code, Claude Desktop, Cursor and other MCP clients. It gives your agent fourteen tools over the ProspectAPIs API: search funding rounds by date, round, amount, company, investor and country, get new matching rounds pushed to your webhook, and order a cited research brief on any company or person. Every funding record carries the URL where the round was announced, when there is one. Records cost $0.02 each after 100 free a month, a completed brief costs $0.15, and there are no seats, no subscription and no card to sign up. It needs Node.js 22 or later.

Install (Claude Code): `claude mcp add prospectapis -e PROSPECTAPIS_API_KEY=pa_live_... -- npx -y prospectapis-mcp`

Other clients: run `npx -y prospectapis-mcp` with `PROSPECTAPIS_API_KEY` from https://prospectapis.com

Website: https://prospectapis.com/mcp

| Tool | Endpoint | Cost |
|---|---|---|
| `funding_search` | `GET /v1/funding` | $0.02 per record returned, after 100 free records a month; no match is free |
| `funding_get` | `GET /v1/funding/:id` | $0.02 when found; a missing id is free |
| `research_submit` | `POST /v1/research` | one research at `research_price_usd` (see `account_balance`), charged only when the brief completes; refunded on failure |
| `research_get` | `GET /v1/research/:id` | free; poll until `status` is `completed` or `failed` |
| `watchlist_create`, `watchlist_list`, `watchlist_get`, `watchlist_deliveries`, `watchlist_test`, `watchlist_delete` | `/v1/watchlists` | free to manage; a delivered event costs one record, only when your webhook answers 2xx |
| `account_balance` | `GET /v1/account` | free |
| `feedback_send` | `POST /v1/feedback` | free; reports a bug, wrong field or missing capability to the team (10 an hour per key) |
| `pricing_get` | `GET /pricing` | free, no key needed; the live price list |
| `api_version` | `GET /v1/version` | free, no key needed |

`funding_search` filters: `since`, `until` (YYYY-MM-DD), `round` (comma list such as `seed,series_a`),
`min_amount_usd`, `max_amount_usd`, `company`, `domain`, `investor`, `country`, `limit` (1 to 100) and
`cursor` (the previous page's `next_cursor`, passed back unchanged).

`research_submit` takes exactly one prospect identifier (`domain`, `website_url`, `company_name`,
`company_linkedin_url`, a work `email` or `linkedin_url`), or `person_name` with `company_name`, plus an optional
`context` (your own product, at most 1,000 characters) and `purpose` (`account_research`, `pre_call` or
`outreach`). It returns a `research_id` at once; a brief takes 20 to 90 seconds.

## Configure

| Variable | Required | Default |
|---|---|---|
| `PROSPECTAPIS_API_KEY` | yes (all tools except `pricing_get` and `api_version`) | none |
| `PROSPECTAPIS_BASE_URL` | no | `https://api.prospectapis.com` |

Client config (for example `claude_desktop_config.json`):

```json
{
  "mcpServers": {
    "prospectapis": {
      "command": "npx",
      "args": ["-y", "prospectapis-mcp"],
      "env": { "PROSPECTAPIS_API_KEY": "pa_live_..." }
    }
  }
}
```

Claude Code: `claude mcp add prospectapis -e PROSPECTAPIS_API_KEY=pa_live_... -- npx -y prospectapis-mcp`.

## FAQ

**Where does the funding data come from?** Each record carries the URL where the round was announced, when there is one.

**What is free?** 100 funding records a month, any search that matches nothing, watchlist management, and the balance, pricing and version tools.

**Which clients work?** Claude Code, Claude Desktop, Cursor and any client that reads an mcpServers config, through `npx -y prospectapis-mcp`.

## Develop

```bash
cd mcp
npm install
npm test        # mocked fetch over an in-memory MCP transport, no network
npm run check
```

The package is versioned independently of the API (SemVer, `CHANGELOG.md` in this folder). It is marked
`private` so it cannot be published by accident; publishing is done only from the product's own npm identity.

TDQS

A3.7/5.0

Scored across 14 tools

Disambiguation5/5

Each tool targets a distinct resource-action: funding_search vs funding_get, research_submit vs research_get, and the watchlist family splits cleanly into create/list/get/deliveries/test/delete. The supporting utilities (account_balance, feedback_send, pricing_get, api_version) are all clearly differentiated. The only faint overlap is pricing_get vs account_balance, but one quotes prices while the other reports the caller's balance, so confusion risk is minimal.

Naming Consistency5/5

All 14 names use lowercase snake_case with a consistent resource_action pattern (funding_search, research_submit, watchlist_create, account_balance, feedback_send). No camelCase or mixed verb styles appear. Grouping by resource prefix (funding_, research_, watchlist_) further reinforces predictability.

Tool Count5/5

14 tools is well-scoped for a server covering three functional areas (funding data, cited research, and webhook alerts) plus billing/info utilities. Each tool earns its place and none look redundant. This sits comfortably in the ideal 3-15 range.

Completeness4/5

The surface covers the core lifecycle: funding search+retrieve, research submit+poll, full watchlist CRUD plus deliveries and test, and account/pricing/version utilities. Minor gaps exist—there is no watchlist_update (alerts must be deleted and recreated to change filters) and no research_delete/cancel—but these are workaroundable and don't block main workflows.