Remote MCP · Endpoint

Conselho Regional de Odontologia TO: Cadastro MCP server

No. Conselho Regional de Odontologia TO: Cadastro answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_cro_to_cadastro

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/cro_to_cadastro-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
86 ms
Tools exposed
7 tools
Uptime, last 30 days
94.1% from 17 checks
Described by its publisher as
Conselho Regional de Odontologia TO: Cadastro, official-source lookup. Platform-hosted, pay per quer
Listing
From the official MCP registry (active).
Recent checks of Conselho Regional de Odontologia TO: Cadastro
CheckedResultHandshake
1 hour agoHandshake completed86 ms
2 days agoHandshake completed330 ms
4 days agoHandshake completed70 ms
5 days agoHandshake completed35 ms
7 days agoHandshake completed65 ms
8 days agoHandshake completed346 ms
9 days agoHandshake completed220 ms
12 days agoHandshake completed101 ms
14 days agoHandshake completed79 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed63 ms
18 days agoHandshake completed69 ms
19 days agoHandshake completed136 ms
20 days agoHandshake completed39 ms
20 days agoHandshake completed141 ms
21 days agoHandshake completed131 ms
23 days agoHandshake completed94 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 Conselho Regional de Odontologia TO: Cadastro and makes no claim about it beyond what these checks measured.