# Prospect Intelligence (remote · prospect-intelligence.prospectintel.workers.dev)

B2B company research and work-email lookup for AI agents. Pay per call in USDC on Base via x402.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `prospect-intelligence.prospectintel.workers.dev`: 78/100 (this document), [markdown](https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence.md), [page](https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence)

## Channel facts

- Endpoint: `https://prospect-intelligence.prospectintel.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.9.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1267 tokens (~181/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Prospect Intelligence MCP server?

Prospect Intelligence is a hosted endpoint at https://prospect-intelligence.prospectintel.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http truepointmarketingpartners-dotcom-prospect-intel 'https://prospect-intelligence.prospectintel.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "truepointmarketingpartners-dotcom-prospect-intel": {
      "url": "https://prospect-intelligence.prospectintel.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "truepointmarketingpartners-dotcom-prospect-intel": {
      "type": "http",
      "url": "https://prospect-intelligence.prospectintel.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.truepointmarketingpartners-dotcom-prospect-intel]
url = "https://prospect-intelligence.prospectintel.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "truepointmarketingpartners-dotcom-prospect-intel": {
      "type": "remote",
      "url": "https://prospect-intelligence.prospectintel.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add truepointmarketingpartners-dotcom-prospect-intel --url 'https://prospect-intelligence.prospectintel.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  truepointmarketingpartners-dotcom-prospect-intel:
    url: "https://prospect-intelligence.prospectintel.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "truepointmarketingpartners-dotcom-prospect-intel": {
      "Transport": "http",
      "Url": "https://prospect-intelligence.prospectintel.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add truepointmarketingpartners-dotcom-prospect-intel -t streamable-http -u 'https://prospect-intelligence.prospectintel.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "truepointmarketingpartners-dotcom-prospect-intel": {
      "type": "http",
      "url": "https://prospect-intelligence.prospectintel.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `basic_lookup` (~162 tokens)

Basic company lookup

Public company profile: summary plus firmographics (industry, HQ city/country, founded year, employee count and size range, ticker, LinkedIn/X), each field with source, source_url, checked_at and confidence, from Wikidata, Wikipedia, the company homepage and SEC EDGAR. Unknown fields are null, never guessed. Not a contact or CRM record. Price: $0.10 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/basic returns the brief. Read-only.

Input parameters:

- `company` (string, required): Company name, for example "Stripe".
- `domain` (string): Optional company website domain without https, for example stripe.com. Improves accuracy and enables the public website crawl.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { tool, version, company: { name, domain, summary, summary_source_url, public_page, firmographics: { official_name, industry, hq_city, hq_country, founded_year, employee_count, size_rang…
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `enriched_lookup` (~199 tokens)

Enriched company lookup

Prospecting record: everything in basic_lookup plus buying signals (90 days of news, SEC filings), open roles from public job boards, a 0-100 ICP fit score with stated reasons (optional icp input), a sales brief built only from cited facts, recommended next actions and roles to target (no invented names). Every item cites its source. Price: $0.75 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/enriched returns the record. Read-only.

Input parameters:

- `company` (string, required): Company name, for example "Stripe".
- `domain` (string): Optional company website domain without https, for example stripe.com. Improves accuracy and enables the public website crawl.
- `icp` (object): Optional ideal-customer profile for icp_fit: size_ranges (e.g. ["51-200"]), industries (keywords), countries (ISO-2).

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: basic_lookup fields plus buying_signals { status, value[] }, hiring { open_roles, top_departments, source_url }, icp_fit { score, verdict, reasons[] }, sales_brief { points[] }, recommen…
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `prospect_brief` (~116 tokens)

Prospect brief

Full sales prospect brief for one company: overview, positioning, likely needs and talking points, built from public sources with URLs. Price: $3.00 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/deep returns the brief. Read-only.

Input parameters:

- `company` (string, required): Company name, for example "Stripe".
- `domain` (string): Optional company website domain without https, for example stripe.com. Improves accuracy and enables the public website crawl.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: prospect brief with source URLs.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `run_named_tool` (~161 tokens)

Run a named analysis

Run one named public-source analysis: research_company, research_person, find_decision_makers, analyze_marketing_opportunity, identify_buying_signals, enrich_prospect, score_prospect or generate_prospect_brief. Fields with no verified public source come back as unknown rather than guessed. Price: $0.75 USDC on Base per call via x402; this MCP call returns payment instructions and the paid HTTP route POST /v1/tools returns the result. Read-only.

Input parameters:

- `company` (string): Company name (for company tools).
- `domain` (string): Optional company domain, for example stripe.com.
- `person` (string): Person's full name (for research_person).
- `tool` (string, required): Which analysis to run.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: the named analysis with source URLs.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `email_lookup` (~207 tokens)

Email lookup

Find one person's work email at a company domain. Returns the address, whether it was found publicly or inferred from the company's pattern, Hunter's real verification status (valid, accept_all, unknown, invalid), a confidence score, the pages it was seen on and a recommendation. Price: $0.08 USDC on Base via x402, charged only when an address is returned (no result = not charged); this MCP call returns payment instructions for POST /v1/email. Read-only; never sends email. 'valid' means the mail server accepted the address, not that a person reads it.

Input parameters:

- `domain` (string, required): Company email domain, for example stripe.com.
- `first_name` (string): Person's first name.
- `found_only` (boolean): If true, return only addresses found publicly (no pattern inference).
- `full_name` (string): Alternative to first_name + last_name: the full name.
- `last_name` (string): Person's last name.

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { outcome, email, address_origin, verification: { status, provider }, confidence: { score }, evidence: { sources }, recommendation, billing }.
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

### `find_emails_batch` (~205 tokens)

Batch email lookup

Find work emails for 1-25 people in one call, for cleaning a whole prospect list. Each result has exactly the same fields and recommendation labels as email_lookup (found vs inferred, Hunter's real status, score, sources, send / send_with_caution / verify_first / do_not_send), returned in input order with summary counts. Duplicates are looked up once; one contact failing never fails the batch. Price: x402 upto on Base: you authorize up to $0.08 x unique contacts and are charged $0.08 only per address returned. This MCP call returns payment instructions for POST /v1/email/batch. Read-only; never sends email.

Input parameters:

- `contacts` (array, required): 1 to 25 people to look up. Each needs domain plus first_name and last_name, or domain plus full_name.
- `found_only` (boolean): Default for every contact: if true, return only publicly found addresses (no pattern inference).

Output parameters:

- `message` (string): Human-readable summary.
- `payment` (object): Payment instructions. MCP tools/call does not charge or run the paid work; call the HTTP route with x402.
- `result` (object): Paid result: { summary: { requested, unique, duplicates, found, send, send_with_caution, verify_first, do_not_send, no_result, opted_out, errors }, billing, results: [ same shape as email_lookup plus…
- `status` (string): payment_required: pay the HTTP route with x402 to get the result. ok: result is included.
- `tool` (string): Tool name.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 75
- 2026-10-29: 75
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68
- 2026-10-13: 68
- 2026-10-12: 67

## Common questions

### What is the Prospect Intelligence MCP server?

Prospect Intelligence is an MCP server listed in the public MCP registry as io.github.truepointmarketingpartners-dotcom/prospect-intell…. B2B company research and work-email lookup for AI agents. Pay per call in USDC on Base via x402. This page covers its hosted endpoint (https://prospect-intelligence.prospectintel.workers.dev/mcp).

### Is the Prospect Intelligence MCP server safe to use?

Prospect Intelligence scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Prospect Intelligence MCP server expose?

Prospect Intelligence exposes 6 tools: basic_lookup, enriched_lookup, prospect_brief, run_named_tool, email_lookup, find_emails_batch. Their descriptions and schemas cost roughly 1,050 tokens of context every time the server is loaded.

### Does the Prospect Intelligence MCP server require authentication?

No. We connected to Prospect Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Prospect Intelligence MCP server still maintained?

Prospect Intelligence is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://prospect-intelligence.prospectintel.workers.dev/mcp
- Repository: https://github.com/truepointmarketingpartners-dotcom/prospect-intelligence
- Website: https://prospect-intelligence.prospectintel.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence.xml
- Changelog JSON feed: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence.json
- HTML version of this page: https://verifymcp.io/servers/truepointmarketingpartners-dotcom-prospect-intelligence/prospect-intelligence