Docs

Agent Plugin

Install Verfi's consent-verification tooling into any AI agent client with one portable package.

Overview

Agent Plugins is an open, vendor-neutral standard for packaging reusable agent components — Agent Skills and MCP servers — into one portable directory that compatible clients can discover and load consistently.

The Verfi Agent Plugin bundles our MCP server (8 tools, including verify_consent) together with the Verfi consent-verification skill. Install it once and your agent gains TCPA consent verification: check 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
        └── references/  # api-reference, proof-schema, sdk-reference

Skill — SDK install, API auth, session lifecycle (create → claim → verify → proof), and compliance workflows.
MCP server — 8 tools including verify_consent, the primary one-call compliance check.

Get the Package

The plugin lives in the public MCP repo under plugin/:

git clone https://github.com/Verfi-io/verfi-mcp-server
# package is in ./verfi-mcp-server/plugin

Or browse it directly on GitHub.

Install

Copy the plugin/ directory into your client's Agent Plugins location (see your client's docs for where that is), then set your Verfi secret key. The plugin's mcp.json launches the published @verfi/mcp-server via npx and expands ${VERFI_API_KEY} from your environment at load time:

export VERFI_API_KEY=sk_your_secret_key

Generate keys in the Verfi dashboard under Integration → API Keys.

Configuration

The MCP server reads two 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`)

Key Scopes

Your secret key's scopes determine which tools are available:

sessions:search → search_session
sessions:proof → get_proof, verify_consent
sessions:claim → claim_session
sessions:unclaim → unclaim_session
sessions:expiration → update_expiration

Remote Transport

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

Notes

Both plugin.json and mcp.json validate against the canonical Agent Plugins 1.0.0 schemas.
Prefer a plain MCP setup without the skill? The MCP server works standalone in any MCP-compatible client.
License: MIT.