Integration

TPSClear integration

TPSClear screens UK phone numbers against the TPS and CTPS (Telephone Preference Service) registers before you call them, one number or up to 1,000 per request, and stores every screening as an audit record you can fetch later. Keep your own suppression (do-not-call) and consent lists on the account, check whether mobiles anywhere are live or dead (HLR lookup), wash Australian numbers against ACMA's Do Not Call Register, and read usage and balances. Screening with a live key spends one prepaid credit per number; dead number checks and Australian washes are separate prepaid packs and need a live key. Phone numbers are personal data. Key rotation (it returns a new secret), setting the client business name the DMA licence requires (do it on the account page), CSV list uploads and the account's emailed screening log are not exposed. Authentication is a TPSClear API key sent as a Bearer token: create it at tpsclear.co.uk/account; a test key (tpsc_test_) screens built-in fixtures for free and can read but not change the lists, a live key (tpsc_live_) checks the registers.

Connect TPSClear How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with TPSClear

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Consent, 3 operations

add_consentsAdd consentsPOSTAgents: ask firstAdds numbers to the account's consent list (same bodies and limits as add_suppressions); they then come back consented and are not screened. Put the consent evidence in reason. Changes real data; live key only.
list_consentsList consentsGETAgents: ask firstReturns the account's consent list (numbers you hold consent to call): the total count and the 100 most recent entries, each with phone number (personal data), note and dates. Free; needs the consents scope.
remove_consentRemove consentDELETEAgents: ask firstRemoves one number from the account's consent list when consent is withdrawn, so screen_numbers checks it against the registers again. Changes real data; live key only.

Phone number, 3 operations

check_dead_numbersCheck dead numbersPOSTAgents: ask firstAsks the mobile network whether up to 500 numbers (personal data) are live, switched off or dead, and their network and porting. Billed from prepaid dead number checks; live key with the dead_number scope only.
screen_numbersScreen numbersPOSTAgents: ask firstScreens UK phone numbers (personal data) against the TPS and CTPS registers: one result per number, in order. Billed: one credit per distinct valid number on a live key (free on a test key). Store recheckBy. Returns no audit record id.
wash_au_numbersWash au numbersPOSTAgents: ask firstWashes up to 500 Australian numbers (personal data) against ACMA's Do Not Call Register. Billed: one prepaid wash per valid number; live key with the dncr scope only (no test mode). A wash is valid 30 days.

Suppression, 3 operations

add_suppressionsAdd suppressionsPOSTAgents: ask firstAdds up to 10,000 numbers to the account's suppression (do-not-call) list, shared by every key and connected CRM; they then come back suppressed and uncharged. Changes real data; live key only (test keys get 403).
list_suppressionsList suppressionsGETAgents: ask firstReturns the account's own do-not-call (suppression) list: the total count and the 100 most recent entries, each with phone number (personal data), note and dates. Free; needs the suppress scope.
remove_suppressionRemove suppressionDELETEAgents: ask firstRemoves one number from the account's suppression list, so screen_numbers checks it against the registers again. Changes real data; live key only. Optional note says why it came off.

Api key, 1 operation

get_key_infoGet key infoGETAgents: ask firstReturns the calling key's name, last four characters, environment (live or test), plan and scopes. Any valid key can call it whatever its scopes: use it to test the connection.

Dead number balance, 1 operation

get_dead_number_balanceGet dead number balanceGETAgents: ask firstReturns the prepaid dead number checks left on the account (checksRemaining). Free.

Dncr balance, 1 operation

get_dncr_balanceGet dncr balanceGETAgents: ask firstReturns the prepaid Australian Do Not Call Register washes left on the account (washesRemaining). Free.

Screening record, 1 operation

get_screening_recordGet screening recordGETAgents: ask firstFetches a past screening call's stored audit record: when, live or test, lookups, counts by status, provider failures and every result (personal data). Free. screen_numbers does not return its id: ask the user for it.

Usage, 1 operation

get_usageGet usageGETAgents: ask firstReturns the calling key's current fair-use window (limit, used, remaining, reset), the account's 30-day call and lookup totals, and prepaid UK credits left. Free; needs the usage scope.

Use TPSClear from Claude Code, Cursor or Codex

Connect TPSClear in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its TPSClear 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 TPSClear

Create your workspace
Sign up free. Nothing to install.
Connect TPSClear once
Add your TPSClear 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.