Remote MCP · Endpoint

Bahdan Hal MCP server

No. Bahdan Hal answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bahdanhal.pl/mcp

The last check completed an MCP handshake.

Registry name
io.github.bahdanhal/portfolio
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
657 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Bahdan Hal software consulting: services, pricing, CV and skills, and contact requests.
Listing
From the official MCP registry (active).
Recent checks of Bahdan Hal
CheckedResultHandshake
1 hour agoHandshake completed657 ms
2 days agoHandshake completed186 ms
5 days agoHandshake completed568 ms
7 days agoHandshake completed583 ms
9 days agoHandshake completed629 ms
11 days agoHandshake completed828 ms
13 days agoHandshake completed649 ms
15 days agoHandshake completed564 ms
17 days agoHandshake completed620 ms
19 days agoHandshake completed549 ms
20 days agoHandshake completed564 ms
21 days agoHandshake completed630 ms
23 days agoHandshake completed550 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.

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