MCP distribution

Content verification tools for MCP agents.

Install the local MCP wrapper for desktop clients or connect hosted remote MCP at https://api.veracityapi.com/mcp so Claude.ai custom connectors and other MCP clients can call VeracityAPI tools for text, image, batch analysis, and balance preflight.

Get API key Integration details Package source

Install

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

Live on npm: @veracityapi/mcp@0.1.0. Install with npx -y @veracityapi/mcp; keep VERACITY_API_KEY in the MCP server environment.

Remote MCP

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

Use this hosted endpoint for Claude.ai custom connectors and any MCP client that supports Streamable HTTP JSON-RPC. Prefer Authorization headers when the client supports them. The endpoint exposes initialize, tools/list, and tools/call.

Tools

  • verify_content as the primary smart tool for text and image inputs.
  • analyze_text, analyze_image, and analyze_batch remain available for typed compatibility.
  • check_balance for autonomous preflight spend checks.
  • get_balance as a compatibility alias for check_balance.

Distribution status

  • NPM package: @veracityapi/mcp@0.1.0.
  • Source package: packages/mcp.
  • Build/test/pack and install-smoke verification passed before publish.
  • Remote MCP is live at https://api.veracityapi.com/mcp for Claude.ai custom connectors and compatible hosted clients.
  • Claude connector instructions: /integrations/claude.

Safety defaults

Never paste API keys into prompts. Keep VERACITY_API_KEY in the MCP server environment. Image MCP calls force store_content:false; raw image bytes, base64, and full URLs are not stored by default.