TPSClear
REMOTE · TPSCLEAR.CO.UK
Screen UK numbers against TPS and CTPS, wash AU numbers against the DNCR, check dead mobiles.
Available components
Last scanned (19 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1688 tokens (~211/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1385 → 1688 ▼ functional
- New tool “get_screening_history” functional
- New tool “list_packs” functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “buy_credits” rewrote its description, which is the text the model reads security
- Tool “check_dead_numbers” rewrote its description, which is the text the model reads security
- Tool “get_account” rewrote its description, which is the text the model reads security
- Tool “screen_numbers” rewrote its description, which is the text the model reads security
- Tool “wash_au_numbers” rewrote its description, which is the text the model reads security
- MCP protocol: fail → pass ▲ functional
- Schema quality: good → excellent functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Tool “buy_credits” changed its title: Buy a prepaid pack → Get a payment link for a prepaid pack cosmetic
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Tool “buy_credits” rewrote its description, which is the text the model reads security
- Schema quality: 199 → 219 ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://tpsclear.co.uk/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tpsclear.co.uk | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 5918f333d4139bcbd8451bfe1837d4f98fe |
| SANs: tpsclear.co.uk, www.tpsclear.co.uk | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tpsclear.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| co.uk. | present | 11810 | 8 | Verified |
| tpsclear.co.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | object-src 'none'; base-uri 'self'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tpsclear.co.uk/api/mcp | Verified | 200 | |
| http (plaintext) | http://tpsclear.co.uk/api/mcp | HTTPS enforced | 308 | https://tpsclear.co.uk/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buy_credits Get a payment link for a prepaid pack ~568
Creates a Stripe Checkout payment link for a prepaid pack on the connected account and returns the URL. Nothing is charged by this tool: a person opens the link and pays by card, and the credits land on the account once paid. Needs a live, self-serve account that names its client business. Prices are in minor units in the response. Packs: pack-1k: TPSClear UK API credits (1,000 checks), £9.00 ex VAT; pack-5k: TPSClear UK API credits (5,000 checks), £24.00 ex VAT; pack-10k: TPSClear UK API credits (10,000 checks), £39.00 ex VAT; pack-50k: TPSClear UK API credits (50,000 checks), £149.00 ex VAT; pack-100k: TPSClear UK API credits (100,000 checks), £199.00 ex VAT; pack-500k: TPSClear UK API credits (500,000 checks), £599.00 ex VAT; pack-1m: TPSClear UK API credits (1,000,000 checks), £799.00 ex VAT; pack-5m: TPSClear UK API credits (5,000,000 checks), £2499.00 ex VAT; au_100: TPSClear Australian DNCR washes (100), A$4.00 ex VAT; au_250: TPSClear Australian DNCR washes (250), A$9.00 ex VAT; au_500: TPSClear Australian DNCR washes (500), A$14.00 ex VAT; au_1000: TPSClear Australian DNCR washes (1,000), A$24.00 ex VAT; au_2500: TPSClear Australian DNCR washes (2,500), A$48.00 ex VAT; au_5000: TPSClear Australian DNCR washes (5,000), A$85.00 ex VAT; au_10000: TPSClear Australian DNCR washes (10,000), A$145.00 ex VAT; au_25000: TPSClear Australian DNCR washes (25,000), A$310.00 ex VAT; au_50000: TPSClear Australian DNCR washes (50,000), A$600.00 ex VAT; au_100000: TPSClear Australian DNCR washes (100,000), A$1170.00 ex VAT; dn_100: TPSClear dead number checks (100), £1.00 ex VAT; dn_250: TPSClear dead number checks (250), £2.50 ex VAT; dn_500: TPSClear dead number checks (500), £5.00 ex VAT.
| Name | Type | Req | Description |
|---|---|---|---|
| pack | string | yes | The pack id. |
No output schema declared.
No examples provided.
check_dead_numbers Check whether mobiles are live (HLR) ~107
Live mobile network (HLR) lookups: whether each mobile is live, switched off or dead. Needs a live account (an OAuth sign-in or a tpsc_live_ key). One prepaid dead number check per mobile, two for a US number; numbers that are not mobiles and invalid numbers cost nothing. Same as POST /v1/dead-number.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_numbers | array | yes | Phone numbers, up to 500 per call, for example "+447700900123". |
No output schema declared.
No examples provided.
get_account Account and balances ~95
The connected account and the key it acts as: environment, scopes, company name and whether one is still required (GET /v1/me), plus the UK credits left (GET /v1/usage), the Australian washes left (GET /v1/dncr) and the dead number checks left (GET /v1/dead-number). A balance the key lacks the scope for comes back as that error. Costs nothing.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_screening_history Screening and balance history ~157
The account's recent activity, newest first: each UK screening call (time, environment, numbers checked, counts by outcome, campaign_ref, request_id) and each movement on the UK credit, AU wash and dead number balances (purchases, draws, refunds). Phone numbers are never returned. Page back by passing next_before as before. Needs the usage scope. Costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| before | string | – | Optional ISO 8601 timestamp with a time zone, for example "2026-11-02T09:30:00Z". Only events before it are returned. Pass next_before from the previous page. |
| limit | integer | – | How many events to return, 20 by default and up to 100. |
No output schema declared.
No examples provided.
list_packs List the prepaid packs on sale ~98
Every prepaid pack on sale: its id (the one buy_credits takes), name, what it buys, price in minor units ex VAT, currency and how many months the credits last. Optionally filter by kind. Costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Optional. uk_credits for UK TPS and CTPS checks, au_washes for Australian Do Not Call Register washes, dead_number_checks for live mobile (HLR) checks. |
No output schema declared.
No examples provided.
screen_numbers Screen UK numbers (TPS and CTPS) ~138
Screen UK phone numbers against the TPS and CTPS registers before calling. Each result is clean, tps-listed, ctps-listed, unknown, suppressed or consented. Draws the account's prepaid UK credits, one per distinct valid number; a test API key (tpsc_test_) returns fixtures at no cost. Same as POST /v1/screen.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign_ref | string | – | Optional reference stored on the audit record: letters, digits, spaces and . , : / # _ - only. |
| phone_numbers | array | yes | Phone numbers, up to 1,000 per call, for example "+447700900123". |
No output schema declared.
No examples provided.
set_company_name Set the client business name ~113
Set the legal name of the business this account screens numbers for (PATCH /v1/me). Required before a live key can screen. Voll Studios Ltd, the company behind TPSClear, is licensed by the DMA as a TPS and CTPS list cleaner. The licence requires a monthly declaration naming each client, so a live API key must belong to an account that names the business it screens numbers for.
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | The legal name of the client business, for example "Acme Outbound Ltd". |
No output schema declared.
No examples provided.
wash_au_numbers Wash Australian numbers (Do Not Call Register) ~105
Wash Australian phone numbers against the Do Not Call Register. Needs a live account (an OAuth sign-in or a tpsc_live_ key), as the register has no test mode. One prepaid AU wash per distinct valid number; invalid numbers cost nothing and numbers the register gave no answer for are refunded. Same as POST /v1/dncr.
| Name | Type | Req | Description |
|---|---|---|---|
| phone_numbers | array | yes | Phone numbers, up to 500 per call, for example "+61412345678". |
No output schema declared.
No examples provided.
How do I install the TPSClear MCP server?
TPSClear is a hosted endpoint at https://tpsclear.co.uk/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tpsclear.co.uk
claude mcp add --transport http uk-co-tpsclear-tpsclear 'https://tpsclear.co.uk/api/mcp'
What is the TPSClear MCP server?
TPSClear is an MCP server listed in the public MCP registry as uk.co.tpsclear/tpsclear. Screen UK numbers against TPS and CTPS, wash AU numbers against the DNCR, check dead mobiles. This page covers its hosted endpoint (https://tpsclear.co.uk/api/mcp).
Is the TPSClear MCP server safe to use?
TPSClear scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TPSClear MCP server expose?
TPSClear exposes 8 tools: screen_numbers, wash_au_numbers, check_dead_numbers, get_account, set_company_name, and 3 more. Their descriptions and schemas cost roughly 1,381 tokens of context every time the server is loaded.
Does the TPSClear MCP server require authentication?
No. We connected to TPSClear without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TPSClear MCP server still maintained?
TPSClear is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.