Integration

Veremark integration

Veremark runs pre-employment background checks (references, identity, right to work, criminal record, education, employment history, sanctions and more). Order a background check for a candidate from one of your criteria packages, follow its status, download the full PDF report or one check's report, share the report through an expiring link, move a check between review and completed, and manage criteria, users, account settings, candidates and uploaded documents. Rotating the API token, creating child accounts (a permission granted by Veremark), the restricted force-status route and the parameterless collection-level candidate delete are not exposed. Authentication is an API token sent in the Authorization header as Token <key>.

Connect Veremark How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Veremark.Built from the 29 Veremark tools below, on the connection you add once.

What you can do with Veremark

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Company setting, 5 operations

create_company_settingCreate company settingPOSTCreate an account setting as a name and value pair.
delete_company_settingDelete company settingDELETEDelete an account setting.
get_company_settingGet company settingGETGet one account setting by guid.
list_company_settingsList company settingsGETList the account settings, each a name and value pair with its guid.
update_company_settingUpdate company settingPUTReplace an account setting. Both name and value are required: read the current pair with get_company_setting and send the one you keep back with the change.

Background check, 4 operations

create_requestCreate requestPOSTOrder a background check (billed per check in your criteria). Needs a criteria_guid from list_criteria and the candidate; Veremark emails the candidate unless send_initial_candidate_email is false.
delete_requestDelete requestDELETEDelete a background check request. Veremark only allows it while the status is requested, draft or expired.
get_requestGet requestGETGet a background check request: overall status, each check with its status, completion date and costs, the candidate guid and the web app links.
list_requestsList requestsGETList background check requests on the account, optionally only those whose status changed on or after a date, or linked to your own external_id.

Criteria, 4 operations

create_criteriaCreate criteriaPOSTCreate a criteria package: a named set of checks for one country, then usable as criteria_guid in create_request.
delete_criteriaDelete criteriaDELETEDelete a criteria package.
get_criteriaGet criteriaGETGet one criteria package with its checks and questionnaires.
list_criteriaList criteriaGETList the criteria packages of the account: each one's guid (the criteria_guid create_request takes), name, country and checks.

User, 4 operations

create_userCreate userPOSTAdd a user to the Veremark account by email, with an optional name and role.
delete_userDelete userDELETERemove a user from the Veremark account.
get_userGet userGETGet one user of the account by guid.
list_usersList usersGETList the users of the Veremark account (email, name and guid).

Candidate, 3 operations

delete_candidateDelete candidateDELETESoft-delete one candidate by guid.
get_candidateGet candidateGETGet one candidate by guid (the candidate_guid of a request).
list_candidatesList candidatesGETList the candidates of the account (email and guid).

Document, 2 operations

download_documentDownload documentGETDownload an uploaded document as a stored file. The guid comes from the documents list of a check in get_request.
upload_documentUpload documentPOSTUpload a document (passport, CV, proof of address and others) to one check of a background check request.

Check, 1 operation

list_checksList checksGETList the checks available to the account, with their name, title, guid and price in credits per country; filter by country.

Check report, 1 operation

download_check_reportDownload check reportGETDownload the PDF report of one check within a request. Returns a stored file.

Check status, 1 operation

update_check_statusUpdate check statusPATCHMove one check of a request between review and completed, when Veremark allows that transition.

Child account, 1 operation

list_child_accountsList child accountsGETList the child accounts under this account: name, region and countries of employment.

Dbs role, 1 operation

list_dbs_rolesList dbs rolesGETList the DBS (UK Disclosure and Barring Service) roles approved for the account, with workforce type and check level.

Full report, 1 operation

download_full_reportDownload full reportGETDownload the full PDF report of a request (every check performed on the candidate). Returns a stored file.

Report link, 1 operation

create_report_linkCreate report linkPOSTCreate a link to a request's full report that expires after expires_in seconds. Returns full_report_url and its expiry. Anyone holding the link can read the candidate's report, so share it only with entitled people.

Use Veremark from Claude Code, Cursor or Codex

Connect Veremark in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Veremark operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Veremark

Create your workspace
Sign up free. Nothing to install.
Connect Veremark once
Add your Veremark connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.