AI导哈

TCPA同意验证MCP服务器

Verfi MCP服务器为AI代理提供TCPA同意验证工具，用于检查潜在客户是否具有有效同意并生成合规证明，适用于需要自动化合规审核的销售和通信场景。

  • by Verfi-io
  • TypeScript
  • 本地部署
  • 更新于
在 GitHub 查看 Verfi-io/verfi-mcp-server

使用说明

@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.

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.

相关 MCP