LeadForm AI

io.github.sarvin-techPublished by GitHub account sarvin-techv1.0.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant score and qualify B2B leads through a paid x402 API, with a free step to look up pricing first.

What you can do
Look up the paid lead-qualification API details: endpoint URL, price, network and x402 payment protocol, without being charged. Score and qualify a B2B lead through the paid API. Receive an x402 payment challenge when no payment signature is supplied, then retry with a valid payment signature to get the qualification result.
When to use it
Use it when an assistant needs to score or qualify B2B leads and the workflow can handle a paid, pay-per-call API. The free info tool lets you check price and network before committing to a paid call.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. Paid calls need an x402 payment signature supplied as the PAYMENT-SIGNATURE header, which implies a funded wallet on the stated network. Network access to the endpoint is required.
Before you install
The qualification tool is paid and charges per call through the x402 protocol; check the price and network with the free info tool first. Payment is authorized by a PAYMENT-SIGNATURE header tied to a wallet, so treat wallet credentials as sensitive. Lead data submitted for scoring is sent to a third-party endpoint.

Installation

In SourceWeft

  1. Open LeadForm AI in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sarvin-tech%2Fleadform-ai/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "leadform-ai": {
      "type": "http",
      "url": "https://leadform-ai.vercel.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

2

get_leadform_payment_info

Get LeadForm payment info

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

Takes no parameters.

qualify_b2b_lead

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.

ParametersnameneedteamemailbudgetcompanytimelinepaymentSignature

Version history

1
  1. v1.0.0LatestSep 29, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.