# LeadForm AI (remote · leadform-ai.vercel.app)

Paid B2B lead scoring and next-action qualification for AI agents.

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

## Components

- remote · `leadform-ai.vercel.app`: 63/100 (this document), [markdown](https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai.md), [page](https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai)

## Channel facts

- Endpoint: `https://leadform-ai.vercel.app/mcp`
- 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-29.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 153 tokens (~76/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 13% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the LeadForm AI MCP server?

LeadForm AI is a hosted endpoint at https://leadform-ai.vercel.app/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 sarvin-tech-leadform-ai 'https://leadform-ai.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sarvin-tech-leadform-ai": {
      "url": "https://leadform-ai.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sarvin-tech-leadform-ai": {
      "type": "http",
      "url": "https://leadform-ai.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.sarvin-tech-leadform-ai]
url = "https://leadform-ai.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sarvin-tech-leadform-ai": {
      "type": "remote",
      "url": "https://leadform-ai.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sarvin-tech-leadform-ai --url 'https://leadform-ai.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sarvin-tech-leadform-ai:
    url: "https://leadform-ai.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sarvin-tech-leadform-ai": {
      "Transport": "http",
      "Url": "https://leadform-ai.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sarvin-tech-leadform-ai -t streamable-http -u 'https://leadform-ai.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sarvin-tech-leadform-ai": {
      "type": "http",
      "url": "https://leadform-ai.vercel.app/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-09-29 (score 63)

First indexed and scored.

## MCP tools (2)

### `get_leadform_payment_info` (~34 tokens)

Get LeadForm payment info

Returns the LeadForm paid lead-qualification API URL, price, network and x402 payment protocol without charging.

### `qualify_b2b_lead` (~119 tokens)

Qualify a B2B lead with LeadForm AI

Paid B2B lead scoring. Without paymentSignature it returns the x402 payment challenge. Retry with a valid PAYMENT-SIGNATURE for the qualification result.

Input parameters:

- `budget` (string|number)
- `company` (string)
- `email` (string)
- `name` (string)
- `need` (string)
- `paymentSignature` (string): Optional x402 PAYMENT-SIGNATURE header value for a paid retry.
- `team` (string|number)
- `timeline` (string|number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai#diagnostics

## Score history

- 2026-09-29: 63

## Common questions

### What is the LeadForm AI MCP server?

LeadForm AI is an MCP server listed in the public MCP registry as io.github.sarvin-tech/leadform-ai. Paid B2B lead scoring and next-action qualification for AI agents. This page covers its hosted endpoint (https://leadform-ai.vercel.app/mcp).

### Is the LeadForm AI MCP server safe to use?

LeadForm AI scores 63 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 LeadForm AI MCP server expose?

LeadForm AI exposes 2 tools: get_leadform_payment_info, qualify_b2b_lead. Their descriptions and schemas cost roughly 153 tokens of context every time the server is loaded.

### Does the LeadForm AI MCP server require authentication?

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

### Is the LeadForm AI MCP server still maintained?

LeadForm AI is still listed as active in the MCP registry. We last reached this channel on 29 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://leadform-ai.vercel.app/mcp
- Repository: https://github.com/sarvin-tech/leadform-ai
- Changelog RSS feed: https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai.xml
- Changelog JSON feed: https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai.json
- HTML version of this page: https://verifymcp.io/servers/sarvin-tech-leadform-ai/leadform-ai