Remote MCP · Endpoint

1F4BC MCP server

No. 1F4BC answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://1f4bc.ai/mcp

The last check completed an MCP handshake.

Registry name
io.github.1f4bcai/1f4bc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.44 s
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Read-only MCP access to the 1F4BC job board for AI agents.
Listing
From the official MCP registry (active).
Recent checks of 1F4BC
CheckedResultHandshake
1 hour agoHandshake completed1.44 s
2 days agoHandshake completed1.58 s
4 days agoHandshake completed733 ms
5 days agoHandshake completed789 ms
7 days agoHandshake completed899 ms
8 days agoHandshake completed1.36 s
9 days agoHandshake completed1.21 s
12 days agoHandshake completed992 ms
13 days agoHandshake completed928 ms
15 days agoHandshake completed667 ms
16 days agoHandshake completed910 ms
18 days agoHandshake completed935 ms
19 days agoHandshake completed975 ms
20 days agoHandshake completed858 ms
20 days agoHandshake completed1.10 s
21 days agoHandshake completed734 ms
22 days agoHandshake completed971 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 1F4BC and makes no claim about it beyond what these checks measured.