Remote MCP · Endpoint

Babá Certa MCP server

No. Babá Certa answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://plugin.babacerta.com.br/claude/mcp

The last check completed an MCP handshake.

Registry name
br.com.babacerta/babacerta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
604 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Encontre babás por cidade e calcule o custo da contratação e o salário líquido no Brasil.
Website
https://babacerta.com.br/
Listing
From the official MCP registry (active).
Recent checks of Babá Certa
CheckedResultHandshake
5 hours agoHandshake completed604 ms
2 days agoHandshake completed197 ms
5 days agoHandshake completed544 ms
7 days agoHandshake completed511 ms
9 days agoHandshake completed488 ms
11 days agoHandshake completed152 ms
13 days agoHandshake completed147 ms
15 days agoHandshake completed526 ms
17 days agoHandshake completed517 ms
18 days agoHandshake completed161 ms
20 days agoHandshake completed519 ms
21 days agoHandshake completed532 ms
23 days agoHandshake completed250 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Babá Certa and makes no claim about it beyond what these checks measured.