Skip to content

TPSClear MCP server

uk.co.tpsclear/tpscleartpsclear.co.ukstreamable-httpv1.1.0Scanned

Screen UK numbers against TPS and CTPS, wash AU numbers against the DNCR, check dead mobiles.

8 tools: 5 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 5 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TPSClear MCP server can do

The TPSClear MCP server is published by tpsclear.co.uk, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: screen_numbers, wash_au_numbers, check_dead_numbers, set_company_name and 1 more), but cannot delete data. 3 tools only read.

4 tools bring in text other people can write (screen_numbers, wash_au_numbers, check_dead_numbers and 1 more); 3 tools can send data out of your system (screen_numbers, wash_au_numbers and check_dead_numbers).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 5Claude Code: ask
  • buy_creditsCreates a Stripe Checkout payment link for a prepaid pack on the connected account and returns the URL.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a payment link for a prepaid pack
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • check_dead_numbersLive mobile network (HLR) lookups: whether each mobile is live, switched off or dead.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone_numbers): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check whether mobiles are live (HLR)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • screen_numbersScreen UK phone numbers against the TPS and CTPS registers before calling.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone_numbers): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Screen UK numbers (TPS and CTPS)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • set_company_nameSet the legal name of the business this account screens numbers for (PATCH /v1/me).No findings

    Why it is in this group

    • The name "set_company_name" says "set": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Set the client business name
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • wash_au_numbersWash Australian phone numbers against the Do Not Call Register.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone_numbers): what the tool writes goes there.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Wash Australian numbers (Do Not Call Register)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_accountThe 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 Austra…No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Account and balances
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_screening_historyThe 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 cr…No findings

    Why it is in this group

    • The name "get_screening_history" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Screening and balance history
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_packsEvery 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.No findings

    Why it is in this group

    • The name "list_packs" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List the prepaid packs on sale
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:20 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://tpsclear.co.uk/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://tpsclear.co.uk
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://tpsclear.co.uk/api/mcp: tools/list returned 8 tools to an anonymous client, including screen_numbers (write), wash_au_numbers (write), check_dead_numbers (write), set_company_name (write), buy_credits (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • RFC 9728 protected resource metadata: none to https://tpsclear.co.uk/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://tpsclear.co.uk
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added.+2 addedView diff
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://tpsclear.co.uk/.well-known/oauth-protected-resource/api/mcp; Authorization servers: none -> https://tpsclear.co.uk; Dynamic client registration: not observed -> y…View diff
    • RFC 9728 protected resource metadata: none to https://tpsclear.co.uk/.well-known/oauth-protected-resource/api/mcp
    • Authorization servers: none to https://tpsclear.co.uk
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  3. Tools6 changed.~6 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http tpsclear https://tpsclear.co.uk/api/mcp
claude mcp add --transport http tpsclear https://tpsclear.co.uk/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tpsclear__get_account",
      "mcp__tpsclear__list_packs",
      "mcp__tpsclear__get_screening_history"
    ],
    "ask": [
      "mcp__tpsclear__screen_numbers",
      "mcp__tpsclear__wash_au_numbers",
      "mcp__tpsclear__check_dead_numbers",
      "mcp__tpsclear__set_company_name",
      "mcp__tpsclear__buy_credits"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tpsclear. Review it before you use it.

Capability tags behind 4 rules
  • mcp__tpsclear__screen_numbers untrusted-input, outbound
  • mcp__tpsclear__wash_au_numbers untrusted-input, outbound
  • mcp__tpsclear__check_dead_numbers untrusted-input, outbound
  • mcp__tpsclear__buy_credits untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/uk.co.tpsclear/tpsclear/verify?hash=4b57f0acdb243f6b81d9a59a6163d9b1853d87b21184b4544009b17e3529730b" | jq -e '.changed == false'

Pinned hash 4b57f0acdb24, from Nov 12, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/uk.co.tpsclear/tpsclear/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for uk.co.tpsclear/tpsclear
[![Anlyon Radar](https://radar.anlyon.com/badge/uk.co.tpsclear/tpsclear.svg)](https://radar.anlyon.com/servers/uk.co.tpsclear/tpsclear)

Source: MCP Registry. Synced Oct 30, 2026, 21:18 UTC.

TPSClear MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TPSClear MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TPSClear MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TPSClear MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TPSClear MCP server have?

8 tools: 5 write, 3 read. screen_numbers, wash_au_numbers, check_dead_numbers, set_company_name, buy_credits, get_account, list_packs and get_screening_history.

Does the TPSClear MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TPSClear MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): screen_numbers, wash_au_numbers and check_dead_numbers.

Has the TPSClear MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.