Skip to content

verfi-io/verfi

v1.1.0MIT

TCPA consent verification for lead generation. Verify lead consent, pull machine-readable proof, and manage consent sessions via the Verfi API.

GitHubOpen Website

Verfi Agent Plugin

An Agent Plugins v1.0.0 package that bundles Verfi's consent-verification tooling into one portable directory any compatible client (Cursor, Claude, OpenAI, etc.) can discover and load.

TCPA consent verification for lead generation: verify lead consent before contact, pull machine-readable proof for disputes, and manage consent sessions via the Verfi API.

What's inside

plugin/
├── plugin.json          # manifest (Agent Plugins 1.0.0)
├── mcp.json             # MCP server config (stdio via @verfi/mcp-server)
└── skills/
    └── verfi/
        ├── SKILL.md     # Verfi consent-verification skill (canonical source)
        └── references/  # api-reference, proof-schema, sdk-reference
  • Skill — SDK install, API auth, session lifecycle (create → claim → verify → proof), compliance workflows. This is the canonical home for the Verfi skill.
  • MCP server — 9 tools including verfi_verify_consent (a proof-summary tool, not a claim or combined PII decision). Source lives in this repo's src/; published as @verfi/mcp-server.

Install

Clone or copy this plugin/ directory into your client's Agent Plugins location, then set your Verfi secret key. Clients expand ${VERFI_API_KEY} from the environment at load time:

export VERFI_API_KEY=sk_you…here

Generate keys in the Verfi dashboard under Integration > API Keys. Key scopes determine which tools are available (sessions:proof, sessions:claim, etc.).

Remote transport (optional)

The stdio config runs the published npm package locally. For a hosted deployment, swap the verfi entry in mcp.json for a streamable-http server pointing at your Verfi MCP endpoint. Do not embed secrets in headers — authorization is client-managed per the spec.

Spec conformance

Both plugin.json and mcp.json validate against the canonical 1.0.0 schemas. 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, 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. PII is a separate verfi_search_session lookup before claiming. Proof summaries do not perform a combined acceptance decision; when verfi_verify_consent checks hashes it also needs sessions:search.