Remote MCP · Endpoint

ByeFine MCP server

No. ByeFine answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://byefine.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.byefine/byefine
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
294 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Free UK parking ticket checks, PCN codes and deadlines, then ByeFine writes and files the appeal.
Listing
From the official MCP registry (active).
Recent checks of ByeFine
CheckedResultHandshake
35 minutes agoHandshake completed294 ms
8 days agoCredentials required—
9 days agoCredentials required—
11 days agoCredentials required—
12 days agoCredentials required—
12 days agoCredentials required—
14 days agoCredentials required—
14 days agoCredentials required—
16 days agoCredentials required—
19 days agoCredentials required—
21 days agoCredentials required—
24 days agoCredentials required—

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

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