Remote MCP · Endpoint

Contazz AutoPilot MCP server

No. Contazz AutoPilot answered an MCP handshake 18 hours ago.

UpLast checked 18 hours ago

Server URL

https://appcontazz.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.MarcioKorpHub/contazz-autopilot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
453 ms
Tools exposed
61 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Brazilian AI-powered accounting & tax automation: NFS-e invoicing, CBS/IBS tax reform, compliance.
Listing
From the official MCP registry (active).
Recent checks of Contazz AutoPilot
CheckedResultHandshake
18 hours agoHandshake completed453 ms
11 days agoHandshake completed616 ms
11 days agoHandshake completed740 ms
12 days agoHandshake completed495 ms
14 days agoHandshake completed636 ms
15 days agoHandshake completed891 ms
15 days agoHandshake completed569 ms
16 days agoHandshake completed562 ms
18 days agoHandshake completed391 ms
19 days agoHandshake completed755 ms
22 days agoFailed - the response was not JSON-RPC—
25 days agoFailed - the server returned an HTTP error—
27 days agoHandshake completed462 ms
29 days agoHandshake completed789 ms

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

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