Remote MCP · Endpoint

HebrewCore by baba Hebrew MCP server

No. HebrewCore by baba Hebrew answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://hc.itsbaba.com/mcp

The last check completed an MCP handshake.

Registry name
com.itsbaba/hebrewcore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
327 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hebrew translation that keeps prices, names and dates exact, RTL display, nikud, clinical Hebrew.
Listing
From the official MCP registry (active).
Recent checks of HebrewCore by baba Hebrew
CheckedResultHandshake
5 hours agoHandshake completed327 ms
9 days agoHandshake completed403 ms
10 days agoHandshake completed406 ms
11 days agoHandshake completed650 ms
12 days agoHandshake completed504 ms
14 days agoHandshake completed345 ms
14 days agoHandshake completed544 ms
15 days agoHandshake completed300 ms
17 days agoHandshake completed343 ms
19 days agoHandshake completed543 ms
21 days agoHandshake completed565 ms
24 days agoHandshake completed351 ms
26 days agoHandshake completed598 ms
28 days agoHandshake completed303 ms

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

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