VeroID Documentation

VeroID hosts a Model Context Protocol (MCP) server so AI coding assistants like Cursor and Claude can build your integration for you: run DVS test verifications, look up results, pull confirmed IVS test records, and fetch document schemas, integration guides, and code examples, all without leaving your editor.

Test environment only. The MCP server accepts sk_test_* keys exclusively and runs real verifications against the DVS test hub. No credits are used. Live keys are rejected with 403.

Endpoint

https://test-api.veroid.com.au/mcp

The server uses the stateless Streamable HTTP transport. Authenticate with your test key in the X-API-Key header (an Authorization: Bearer token also works). You need a developer account approved for the DVS test hub. See Getting Started.

Connect from Cursor

Add to .cursor/mcp.json in your project (or the global MCP settings):

{
  "mcpServers": {
    "veroid": {
      "url": "https://test-api.veroid.com.au/mcp",
      "headers": {
        "X-API-Key": "sk_test_your_key"
      }
    }
  }
}

Connect from Claude Code

claude mcp add --transport http veroid https://test-api.veroid.com.au/mcp \
  --header "X-API-Key: sk_test_your_key"

Available Tools

Tool	What it does
`verify_document`	Runs a real DVS test verification, same as `POST /v1/verify` with a test key
`get_dvs_test_cases`	Confirmed IVS/Fujitsu test records with full request bodies and expected response codes
`get_verification`	Fetches the processing state of a previous verification by ID
`list_verifications`	Lists the account's recent verifications
`list_document_types`	The 12 supported document types with required fields and formats
`get_sandbox_triggers`	Predefined screening test names and example payloads (screening fixtures only, not DVS)
`screen_subject`	Runs a screening check using predefined test names, same as `POST /v1/screening` on test-api
`get_screening_request`	Fetches a previous screening request and its matches
`list_screening_requests`	Lists recent screening checks for the account
`get_integration_guide`	Integration guides including `screening` topic for AML checks
`get_code_example`	Test-environment integration examples in cURL, JavaScript/TypeScript, Python, and Next.js

Example Prompts

"Add VeroID driver's licence verification to my signup flow using a confirmed DVS test record."
"Screen a customer name against sanctions and PEP lists using the test screening names."
"Which fields does a Medicare card verification need?"
"Fetch the get_dvs_test_cases for passport and run verify_document with a Y case."

Going Live

The MCP server is a development tool. Your production code should call the REST API directly: https://api.veroid.com.au/v1/verify with a sk_live_* key once VeroID approves your account. See Getting Started.