Remote MCP · Endpoint
SEFAZ AM: Certidão Negativa de Débitos (Certificado Digital) MCP server
No. SEFAZ AM: Certidão Negativa de Débitos (Certificado Digital) answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.mcp.ai/p_sefaz_am_certidao_debitos_cert
The last check completed an MCP handshake.
- Registry name
- io.github.mcp-dir/sefaz_am_certidao_debitos_cert-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 68 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 88.9% from 18 checks
- Described by its publisher as
- SEFAZ AM: Clearance Certificate (Debts) (Certificado Digital), official-source lookup. Platform-host
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 68 ms |
| 1 day ago | Handshake completed | 76 ms |
| 2 days ago | Handshake completed | 425 ms |
| 3 days ago | Handshake completed | 396 ms |
| 4 days ago | Handshake completed | 35 ms |
| 5 days ago | Handshake completed | 33 ms |
| 6 days ago | Handshake completed | 307 ms |
| 8 days ago | Handshake completed | 360 ms |
| 11 days ago | Handshake completed | 41 ms |
| 13 days ago | Failed - the request timed out | — |
| 16 days ago | Handshake completed | 205 ms |
| 18 days ago | Handshake completed | 29 ms |
| 20 days ago | Handshake completed | 153 ms |
| 22 days ago | Handshake completed | 51 ms |
| 24 days ago | Failed - the request timed out | — |
| 26 days ago | Handshake completed | 35 ms |
| 27 days ago | Handshake completed | 143 ms |
| 29 days ago | Handshake completed | 114 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 responding of 29.
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 SEFAZ AM: Certidão Negativa de Débitos (Certificado Digital) and makes no claim about it beyond what these checks measured.