Skip to main content
Glama
verfi-mcp-server

verfi-mcp-server

Official
by Verfi-io

@verfi/mcp-server

MCP server for Verfi — TCPA consent verification tools for AI agents.

Tools

Tool

Description

verfi_verify_consent

Check if a lead has valid consent. The primary tool for compliance verification.

verfi_get_proof

Get full machine-readable consent proof for a session.

verfi_search_session

Look up a session by Verfi ID with optional PII hash verification.

verfi_get_claim_status

Read claim mode, availability and recording validity (not a reservation).

verfi_claim_session

Claim with buyer gates and a persisted idempotency key.

verfi_unclaim_session

Release a claimed session.

verfi_list_sessions

List your claimed sessions (paginated).

verfi_update_expiration

Update a claimed session's expiration date.

verfi_add_sdk

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

VERFI_API_KEY

Yes

Your Verfi secret API key (sk_...)

VERFI_API_URL

No

API base URL (defaults to https://api.verfi.io/tenant/v1)

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_status

  • sessions:proof → verfi_get_proof, verfi_verify_consent

  • sessions:claim → verfi_claim_session

  • sessions:unclaim → verfi_unclaim_session

  • sessions: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 tools
verfi_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).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers