Remote MCP · Endpoint

CodeAtlas MCP server

No. CodeAtlas answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://codeatlas.com.br/mcp

The last check completed an MCP handshake.

Registry name
br.com.codeatlas/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
146 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only CodeAtlas service catalog: list, get and search services. No authentication.
Listing
From the official MCP registry (active).
Recent checks of CodeAtlas
CheckedResultHandshake
5 hours agoHandshake completed146 ms
9 days agoHandshake completed158 ms
10 days agoHandshake completed109 ms
11 days agoHandshake completed230 ms
12 days agoHandshake completed125 ms
14 days agoHandshake completed116 ms
14 days agoHandshake completed173 ms
15 days agoHandshake completed211 ms
17 days agoHandshake completed190 ms
19 days agoHandshake completed78 ms
21 days agoHandshake completed128 ms
24 days agoHandshake completed137 ms
26 days agoHandshake completed146 ms
28 days agoHandshake completed132 ms

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

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