Remote MCP · Endpoint

TapTax MCP server

No. TapTax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.taptax.co.uk/mcp

The last check completed an MCP handshake.

Registry name
uk.co.taptax/taptax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
140 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
UK tax: take-home pay, self-employed and company tax, VAT, stamp duty, invoices and MTD.
Listing
From the official MCP registry (active).
Recent checks of TapTax
CheckedResultHandshake
1 hour agoHandshake completed140 ms
1 day agoHandshake completed165 ms
4 days agoHandshake completed156 ms
6 days agoHandshake completed797 ms
9 days agoHandshake completed150 ms
11 days agoHandshake completed180 ms
13 days agoHandshake completed158 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed345 ms
19 days agoHandshake completed163 ms
21 days agoHandshake completed138 ms
22 days agoHandshake completed255 ms
24 days agoHandshake completed482 ms
25 days agoHandshake completed176 ms
27 days agoHandshake completed150 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with TapTax and makes no claim about it beyond what these checks measured.