Remote MCP · Endpoint

Duck Tax MCP server

No. Duck Tax answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://ducktax.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.ducktax/ducktax
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
20 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Check micro-entity company accounts: raw figures in, validated balance sheet and deadlines out.
Listing
From the official MCP registry (active).
Recent checks of Duck Tax
CheckedResultHandshake
1 hour agoHandshake completed114 ms
2 days agoHandshake completed102 ms
4 days agoHandshake completed75 ms
5 days agoHandshake completed73 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed95 ms
9 days agoHandshake completed100 ms
12 days agoHandshake completed103 ms
13 days agoHandshake completed71 ms
15 days agoHandshake completed112 ms
16 days agoHandshake completed106 ms
17 days agoHandshake completed60 ms
18 days agoHandshake completed87 ms
19 days agoHandshake completed67 ms
20 days agoHandshake completed67 ms
21 days agoHandshake completed57 ms
22 days agoHandshake completed155 ms

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

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 Duck Tax and makes no claim about it beyond what these checks measured.