# Leads Discovery Agent by Nova (CIVAI) (remote · nova.civai.co)

I discover new leads from WhatsApp/Telegram groups, Instagram post commenters, and X thread replier…

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `nova.civai.co`: 69/100 (this document), [markdown](https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent.md), [page](https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent)

## Channel facts

- Endpoint: `https://nova.civai.co/mcp/agents/leads-discovery-agent`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-09-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 963 tokens (~60/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "leads_discovery__delete_scans" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 16 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 Leads Discovery Agent by Nova (CIVAI) MCP server?

Leads Discovery Agent by Nova (CIVAI) is a hosted endpoint at https://nova.civai.co/mcp/agents/leads-discovery-agent, 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 co-civai-nova-leads-discovery-agent 'https://nova.civai.co/mcp/agents/leads-discovery-agent'
```

### Cursor

```json
{
  "mcpServers": {
    "co-civai-nova-leads-discovery-agent": {
      "url": "https://nova.civai.co/mcp/agents/leads-discovery-agent"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-civai-nova-leads-discovery-agent": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/leads-discovery-agent"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-civai-nova-leads-discovery-agent]
url = "https://nova.civai.co/mcp/agents/leads-discovery-agent"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-civai-nova-leads-discovery-agent": {
      "type": "remote",
      "url": "https://nova.civai.co/mcp/agents/leads-discovery-agent",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-civai-nova-leads-discovery-agent --url 'https://nova.civai.co/mcp/agents/leads-discovery-agent' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-civai-nova-leads-discovery-agent:
    url: "https://nova.civai.co/mcp/agents/leads-discovery-agent"
```

### Netclaw

```json
{
  "McpServers": {
    "co-civai-nova-leads-discovery-agent": {
      "Transport": "http",
      "Url": "https://nova.civai.co/mcp/agents/leads-discovery-agent"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-civai-nova-leads-discovery-agent -t streamable-http -u 'https://nova.civai.co/mcp/agents/leads-discovery-agent'
```

### Other

```json
{
  "mcpServers": {
    "co-civai-nova-leads-discovery-agent": {
      "type": "http",
      "url": "https://nova.civai.co/mcp/agents/leads-discovery-agent"
    }
  }
}
```

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-09-25 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 69, +1)

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

### 2026-09-23 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-22 (score 68, +35)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Tool coverage: 0
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: fair
- [functional] First check of Destructive annotations: 0
- [functional] First check of Schema quality: pass

### 2026-09-21 (score 33)

First indexed and scored.

## MCP tools (16)

### `leads_discovery__list_connectors` (~37 tokens)

List WhatsApp, Instagram, Email, X connector status for a support agent.

Input parameters:

- `agent_id` (string, required)

### `leads_discovery__suggest_targets` (~83 tokens)

AI-propose Instagram or X @targets for a discovery scan (depth/breadth optional).

Input parameters:

- `agent_id` (string, required)
- `channel` (string, required)
- `disable_hard_filter` (boolean)
- `discovery_breadth` (integer)
- `discovery_depth` (integer)
- `min_followers` (integer)

### `leads_discovery__run_scan` (~50 tokens)

Start a leads discovery scan (whatsapp, instagram, x, or telegram).

Input parameters:

- `agent_id` (string, required)
- `channel` (string, required)
- `params` (object)

### `leads_discovery__continue_scan` (~63 tokens)

Continue a scan paused for selection (WhatsApp/Telegram groups or IG/X targets).

Input parameters:

- `agent_id` (string, required)
- `max_contacts_per_group` (integer)
- `scan_id` (string, required)
- `selected_resources` (array, required)

### `leads_discovery__list_scans` (~32 tokens)

List past and active leads discovery scans for an agent.

Input parameters:

- `agent_id` (string, required)

### `leads_discovery__get_scan` (~56 tokens)

Get one scan with paginated leads (status, progress, leads).

Input parameters:

- `agent_id` (string, required)
- `limit` (integer)
- `offset` (integer)
- `scan_id` (string, required)

### `leads_discovery__list_scan_results` (~57 tokens)

Alias of get_scan — read leads from an active or completed scan.

Input parameters:

- `agent_id` (string, required)
- `limit` (integer)
- `offset` (integer)
- `scan_id` (string, required)

### `leads_discovery__delete_scans` (~42 tokens)

Delete one or more completed scan runs (does not delete schedules).

Input parameters:

- `agent_id` (string, required)
- `scan_ids` (array, required)

### `leads_discovery__import_leads` (~71 tokens)

Import discovered leads into the agent CRM (outreach: none|immediate|bulk_followup).

Input parameters:

- `agent_id` (string, required)
- `label` (string)
- `lead_ids` (array, required)
- `outreach` (string)
- `scan_id` (string, required)

### `leads_discovery__clear_discovery_cache` (~37 tokens)

Clear Leads Discovery scan cache for an agent (seen handles / WA progress).

Input parameters:

- `agent_id` (string, required)

### `leads_discovery__create_scan_schedule` (~145 tokens)

Create an auto-scan schedule (Import Only or Message now outreach).

Input parameters:

- `agent_id` (string, required)
- `auto_import` (boolean)
- `auto_outreach` (string)
- `channel` (string, required)
- `enabled` (boolean)
- `frequency` (string)
- `label` (string)
- `max_leads_per_run` (integer)
- `max_runs` (integer)
- `params` (object)
- `relax_target_filter_after_runs` (integer)
- `run_hour_utc` (integer)
- `source_scan_at` (string)
- `source_scan_id` (string)

### `leads_discovery__list_scan_schedules` (~31 tokens)

List auto-scan schedules for an agent.

Input parameters:

- `agent_id` (string, required)

### `leads_discovery__update_scan_schedule` (~132 tokens)

Update or pause/resume an auto-scan schedule.

Input parameters:

- `agent_id` (string, required)
- `auto_import` (boolean)
- `auto_outreach` (string)
- `channel` (string)
- `enabled` (boolean)
- `frequency` (string)
- `label` (string)
- `max_leads_per_run` (integer)
- `max_runs` (integer)
- `params` (object)
- `relax_target_filter_after_runs` (integer)
- `run_hour_utc` (integer)
- `schedule_id` (string, required)

### `leads_discovery__delete_scan_schedule` (~36 tokens)

Delete an auto-scan schedule.

Input parameters:

- `agent_id` (string, required)
- `schedule_id` (string, required)

### `leads_discovery__trigger_scan_schedule` (~40 tokens)

Run an auto-scan schedule immediately (Run now).

Input parameters:

- `agent_id` (string, required)
- `schedule_id` (string, required)

### `leads_discovery__get_discovery_analytics` (~51 tokens)

Get sourced-leads analytics for an agent (window e.g. 7d, 30d).

Input parameters:

- `agent_id` (string, required)
- `window` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent#diagnostics

## Score history

- 2026-09-25: 69
- 2026-09-24: 69
- 2026-09-23: 68
- 2026-09-22: 68
- 2026-09-21: 33

## Common questions

### What is the Leads Discovery Agent by Nova (CIVAI) MCP server?

Leads Discovery Agent by Nova (CIVAI) is an MCP server listed in the public MCP registry as co.civai.nova/leads-discovery-agent. I discover new leads from WhatsApp/Telegram groups, Instagram post commenters, and X thread replier… This page covers its hosted endpoint (https://nova.civai.co/mcp/agents/leads-discovery-agent).

### Is the Leads Discovery Agent by Nova (CIVAI) MCP server safe to use?

Leads Discovery Agent by Nova (CIVAI) scores 69 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 Leads Discovery Agent by Nova (CIVAI) MCP server expose?

Leads Discovery Agent by Nova (CIVAI) exposes 16 tools: leads_discovery__list_connectors, leads_discovery__suggest_targets, leads_discovery__run_scan, leads_discovery__continue_scan, leads_discovery__list_scans, and 11 more. Their descriptions and schemas cost roughly 963 tokens of context every time the server is loaded.

### Does the Leads Discovery Agent by Nova (CIVAI) MCP server require authentication?

Yes. Leads Discovery Agent by Nova (CIVAI) asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Leads Discovery Agent by Nova (CIVAI) MCP server still maintained?

Leads Discovery Agent by Nova (CIVAI) is still listed as active in the MCP registry. We last reached this channel on 25 September 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://nova.civai.co/mcp/agents/leads-discovery-agent
- Website: https://nova.civai.co/agent/leads-discovery-agent
- Changelog RSS feed: https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent.json
- HTML version of this page: https://verifymcp.io/servers/co-civai-nova-leads-discovery-agent/mcp-agents-leads-discovery-agent