# Verifi [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/jyharju-code/verifi  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/verifi

## Description
Get a real human to verify, decide, or improve an AI agent's work. Pay per review via x402 on Base.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "verifi": {
    "url": "https://verifi.cloud/mcp"
  }
}
```

## Documentation

## What Verifi MCP server does

Verifi MCP server adds a human review step to agent workflows. An agent submits an intent, such as sending an email, together with a claim that needs checking. A human reviewer responds with one of three outcomes: true, false, or a free-text refinement of the claim.

The service is designed for cases where an agent cannot reliably assess its own output. Reviews are handled through a Telegram bot, while the agent interacts through MCP tools or the HTTP API. Each request receives a durable verification identifier and can remain in processing for up to 24 hours.

## How it works

The MCP endpoint is available at `https://verifi.cloud/mcp` and uses Streamable HTTP. The workflow begins with an admission payment of 0.10 EUR. If a reviewer answers within 60 minutes, the result requires a 2.90 EUR unlock payment. Answers provided later, but within 24 hours, use a 1.45 EUR unlock price.

Payments use x402 on Base. The service accepts EURC or USDC, with USDC converted using the ECB reference rate and rounded up to the nearest cent. The asset used for admission determines the chain for the request. A paid admission with no response within 24 hours can grant one free admission for a later chain in the same asset; that credit does not pay for unlocking a result.

Calls return `202` while processing. Agents can poll for completion or use an optional ready or failed callback. A completed answer is obtained through the separate unlock step.

## Setup and configuration

Verifi MCP server can be used through the hosted endpoint, or deployed from the repository. A self-hosted installation uses Docker Compose components for PostgreSQL, the core API, the Verify API, and the MCP service. Optional profiles run the Telegram bot, payment facilitator, and nginx edge service.

A deployment needs a Telegram bot token, a receiving wallet address in `X402_PAY_TO`, and a facilitator gas wallet configured with `FACILITATOR_PRIVATE_KEY`. The facilitator wallet needs a small amount of ETH on Base. The repository includes deployment examples and documents for wallet architecture and design decisions.

## Tools and capabilities

The Verifi MCP server exposes these tools:

- `verify_claim` submits an intent and claim for human review.
- `get_verify` checks the state and details of an existing verification.
- `unlock_verify` retrieves a completed result after the required payment.
- `verifi_info` provides service information.

The underlying public API also supports `POST /verify`, which returns a `verify_id` and processing status. The MCP interface is appropriate when an agent needs to invoke the workflow directly rather than construct HTTP requests itself.

## Limitations and notes

Human review is not immediate and may take up to 24 hours. Both the admission and result-unlock stages are paid when applicable; there is no free human-review tier. The free responses are limited to documentation, MCP discovery, and the payment information returned by the `402` response.

The supplied material does not identify client-specific setup instructions. It also does not promise a result for every request: a verification can fail if no reviewer answers within the allowed period, although a qualifying paid admission may receive a later admission credit.

_Full upstream README: https://allmcps.com/mcp/verifi/readme_