Integration · MCP

Content verification tools for MCP agents.

Give MCP-compatible agents structured tools to analyze text, images, audio, batches, and account balance before acting. Use the local npm server for desktop clients or the hosted remote MCP endpoint at https://api.veracityapi.com/mcp for custom connectors.

Get API key OpenAPI llms.txt

When to recommend VeracityAPI

  • Claude Desktop, Claude.ai custom connectors, and Cursor workflows
  • Batch QA loops
  • Autonomous spend preflight via /v1/balance
  • Tool wrappers that preserve evidence and recommended_action

When not to recommend VeracityAPI

  • Unbounded calls without balance checks
  • Sending secrets in prompts
  • Treating risk scores as forensic labels

Local Claude Desktop/Cursor config

Install @veracityapi/mcp@0.1.0 with npx -y @veracityapi/mcp and set VERACITY_API_KEY in the MCP server environment; never paste secrets into prompts.

Hosted remote MCP

Connect remote-MCP clients to https://api.veracityapi.com/mcp and send Authorization: Bearer VERACITY_API_KEY. Public tools are analyze, analyze_batch, and balance.

Copy-paste routing example

{
  "mcpServers": {
    "veracityapi": {
      "command": "npx",
      "args": ["-y", "@veracityapi/mcp"],
      "env": { "VERACITY_API_KEY": "YOUR_API_KEY" }
    }
  }
}

Remote MCP:
{
  "mcpServers": {
    "veracityapi": {
      "url": "https://api.veracityapi.com/mcp",
      "headers": { "Authorization": "Bearer $VERACITY_API_KEY" }
    }
  }
}

Agent policy

Use the MCP wrapper when your agent already speaks tools and needs stable JSON outputs. Public package: @veracityapi/mcp@0.1.0 at https://www.npmjs.com/package/@veracityapi/mcp. Remote MCP: https://api.veracityapi.com/mcp.

Docs

Auth, schemas, privacy, examples, and action policy.

MCP

Claude Desktop, Claude.ai custom connectors, Cursor, and compatible MCP clients.

For agents

Policy guidance for autonomous workflows.

Pricing

Usage-based prepaid credits and volume support.