Remote MCP · Endpoint

McpStamp Asset Register MCP server

No. McpStamp Asset Register answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.zovo.one/mcp/asset-register

The last check completed an MCP handshake.

Registry name
io.github.theluckystrike/asset-register
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
555 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
A fixed asset register with depreciation from bundled Polish KST, HMRC and IRS MACRS tables.
Listing
From the official MCP registry (active).
Recent checks of McpStamp Asset Register
CheckedResultHandshake
34 minutes agoHandshake completed555 ms
9 days agoHandshake completed147 ms
10 days agoHandshake completed107 ms
11 days agoHandshake completed21 ms
12 days agoHandshake completed572 ms
14 days agoHandshake completed113 ms
14 days agoHandshake completed788 ms
15 days agoHandshake completed85 ms
17 days agoHandshake completed67 ms
19 days agoHandshake completed1.04 s
21 days agoHandshake completed1.20 s
24 days agoHandshake completed1.39 s
26 days agoHandshake completed756 ms
28 days agoHandshake completed44 ms

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

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