verfi-mcp-server
OfficialThis MCP server provides Verfi TCPA consent verification and session-claiming tools for AI agents.
Verify a lead's consent by Verfi ID, including TCPA compliance, consent validity, and interaction quality, optionally with email/phone SHA-256 hashes.
Retrieve machine-readable consent proof with hashed PII and tamper verification.
Search sessions by Verfi ID or proof URL and optionally verify PII hash matches.
Read session claim status, recording validity, and availability before claiming.
Claim sessions with buyer gates and idempotency, unclaim sessions, list claimed sessions, and update expiration dates.
Get SDK integration snippets and setup instructions for capturing consent on web forms.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@verfi-mcp-server Verify TCPA consent for lead VF-a1b2c3d4"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@verfi/mcp-server
MCP server for Verfi — TCPA consent verification tools for AI agents.
Tools
Tool | Description |
| Check if a lead has valid consent. The primary tool for compliance verification. |
| Get full machine-readable consent proof for a session. |
| Look up a session by Verfi ID with optional PII hash verification. |
| Read claim mode, availability and recording validity (not a reservation). |
| Claim with buyer gates and a persisted idempotency key. |
| Release a claimed session. |
| List your claimed sessions (paginated). |
| Update a claimed session's expiration date. |
| Get SDK integration snippet and setup instructions. |
Related MCP server: Smallest MCP Server
Setup
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"verfi": {
"command": "npx",
"args": ["-y", "@verfi/mcp-server"],
"env": {
"VERFI_API_KEY": "sk_your_secret_key_here"
}
}
}
}Cursor / Windsurf
Add to your MCP config:
{
"verfi": {
"command": "npx",
"args": ["-y", "@verfi/mcp-server"],
"env": {
"VERFI_API_KEY": "sk_your_secret_key_here"
}
}
}Environment Variables
Variable | Required | Description |
| Yes | Your Verfi secret API key ( |
| No | API base URL (defaults to |
Agent Plugin
This repo also ships a portable Agent Plugins v1.0.0 package in plugin/ that bundles this MCP server together with the Verfi consent-verification skill. Compatible clients (Cursor, Claude, OpenAI, etc.) can discover and load both from one directory. See plugin/README.md.
Quick Start
Developer: "Check if lead VF-a1b2c3d4 has valid TCPA consent"
Agent calls: verfi_verify_consent({ verfiID: "VF-a1b2c3d4" })
→ { consent_valid: true, tcpa_compliant: true, proof_url: "..." }API Key Scopes
Your API key's scopes determine which tools are available:
sessions:search→verfi_search_session,verfi_get_claim_statussessions:proof→verfi_get_proof,verfi_verify_consentsessions:claim→verfi_claim_sessionsessions:unclaim→verfi_unclaim_sessionsessions:expiration→verfi_update_expiration
Generate API keys in the Verfi dashboard under Integration > API Keys.
License
MIT
Building a lead-router integration
Start at https://verfi.io/docs/agent-plugin or read the web-session integration contract. Direct REST does not require MCP installation.
Updated source adds verfi_get_claim_status (sessions:search) and claim options requireRecording, requireVerticals, requireVerifiedScore, minQualityScore, requirePII, emailHash, phoneHash, requireClaimMode, and idempotencyKey. These require the updated server, not just new skill files. Inspect tools/list; use REST or npm install && npm run build followed by node /absolute/path/dist/index.js until the updated npm package is released/installed. Required PII can be enforced in the claim using requirePII with corresponding exact-capture hashes; verfi_search_session remains optional diagnostics. Verify the selected API OpenAPI supports the new fields before enabling them. Version 0.3.0 is the source release for these fields; repository changes do not establish npm publication. Proof summaries do not perform a combined acceptance decision; when verfi_verify_consent checks hashes it also needs sessions:search.
Available Tools
9 toolsverfi_add_sdkA
Get the Verfi SDK integration snippet and setup instructions for capturing consent on a web form.
Inputs: publicKey.
verfi_claim_sessionA
Claim a web session using buyer gates. Requires sessions:claim. Validate required PII separately before calling. Only success=true and data.status=claimed indicates claim success. Reuse the same idempotencyKey and body for identical retries; wallet receipts may replay a historical success without re-evaluating gates.
Inputs: verfiID (required), expirationDate, idempotencyKey, minQualityScore, +3 more.
verfi_get_claim_statusA
Read web-session claimMode, claimable and recording validity before claiming. Requires sessions:search. Not a reservation or buyer-gate evaluation; multi mode does not check your existing claim.
Inputs: verfiID (required).
verfi_get_proofA
Get machine-readable consent proof for a session. Returns structured data including consent status, interaction metrics, form data, device info, and tamper verification. All PII is SHA-256 hashed.
Inputs: verfiID (required).
verfi_list_sessionsB
List sessions claimed by your organization. Returns paginated results with session status and metadata.
Inputs: page, limit, status.
verfi_search_sessionA
Look up a consent session by Verfi ID. Optionally verify email/phone hashes match. Returns session status, metadata, and PII verification results.
Inputs: verfiID (required), email, phone.
verfi_unclaim_sessionA
Release a previously claimed session. Retention drops to 30 days. Only the claiming tenant can unclaim.
Inputs: verfiID (required).
verfi_update_expirationA
Update the expiration date of a claimed session. Must be 30+ days from now, max 5 years from claim date. Rate limited: 3 updates/month per session.
Inputs: verfiID (required), expirationDate (required).
verfi_verify_consentA
Verify consent validity for a lead. Given a Verfi ID and optional PII hashes, returns whether consent was given, TCPA compliance status, and interaction quality. This is the primary tool for checking if a lead has valid consent before contacting them.
Inputs: verfiID (required), email_hash, phone_hash.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Most tools have distinct purposes: search/lookup, proof retrieval, consent verification, claim lifecycle, listing, expiration update, and SDK setup. There is some conceptual overlap among verfi_search_session, verfi_get_proof, and verfi_verify_consent because all involve retrieving or evaluating session/consent data, but descriptions clarify their different outputs and use cases.
All tools use a consistent verfi_ prefix followed by a snake_case verb_noun pattern. Names are predictable and easy to scan, with only natural variations like get_claim_status and add_sdk.
Nine tools is well-scoped for a consent/session management server. Each tool covers a distinct operation in the claim and verification workflow, with no obvious filler tools.
The surface covers session lookup, consent verification, proof retrieval, claim/unclaim, listing, expiration updates, and SDK setup, which is strong lifecycle coverage. Minor gaps may exist around explicit consent revocation or session creation, but those appear to be handled outside the MCP server via the SDK or platform.
Maintenance
Related MCP Connectors
MCP server for SuperPhone — contacts, conversations, tags and consent-based text messages.
Official MCP server for OmniDimension. Drive voice agents, dispatch calls, and run bulk campaigns.
MCP server for OnceAsk, the AI-native current-address layer for people and agents.
FalaAI API MCP server: transcribe audio, diagnose conversations, audit compliance (ISO 18295-1).
Related MCP Servers
- AlicenseAqualityCmaintenanceMCP server for provisioning dedicated real-SIM US phone numbers, receiving inbound SMS, and extracting OTP codes. Built for AI agents automating phone verification workflows.12311 npm1MIT

Smallest MCP Serverofficial
AlicenseAqualityBmaintenanceMCP server for the Smallest AI platform that enables managing AI voice agents, debugging calls, and viewing analytics directly from your IDE.8476 npm1MIT- AlicenseNot gradedqualityBmaintenanceMCP server for storing, managing, and analyzing IETF vCon (Virtual Conversation) data with AI assistants.52 npm4MIT
- AlicenseAqualityDmaintenanceMCP server for verifying high-impact decisions with Trust OS.2MIT