Remote MCP · Endpoint

Boring API MCP server

No. Boring API answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.relaex-engineers.de/mcp

The last check completed an MCP handshake.

Registry name
de.relaex-engineers/boring-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
427 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Deterministic data tools: price list diff, PDF tables, feed validation, data mapping, table diff
Listing
From the official MCP registry (active).
Recent checks of Boring API
CheckedResultHandshake
1 hour agoHandshake completed427 ms
6 hours agoHandshake completed315 ms
2 days agoHandshake completed330 ms
4 days agoHandshake completed517 ms
7 days agoHandshake completed309 ms
9 days agoHandshake completed367 ms
11 days agoHandshake completed305 ms
13 days agoHandshake completed310 ms
15 days agoHandshake completed377 ms
17 days agoHandshake completed299 ms
19 days agoHandshake completed327 ms
21 days agoHandshake completed297 ms
23 days agoHandshake completed318 ms
24 days agoHandshake completed316 ms
25 days agoHandshake completed294 ms

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

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