Remote MCP · Endpoint

Fieldwright MCP server

No. Fieldwright answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fieldwright.cybermax-tools.workers.dev/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
io.github.CyberMax-tools/ai-extract
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
1 tool
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Fieldwright: web page to clean Markdown, metadata, JSON-LD, emails, phones.
Listing
From the official MCP registry (active).
Recent checks of Fieldwright
CheckedResultHandshake
1 hour agoHandshake completed150 ms
1 day agoHandshake completed126 ms
3 days agoHandshake completed235 ms
6 days agoHandshake completed143 ms
7 days agoFailed - the check failed for an unclassified reason—
9 days agoHandshake completed90 ms
10 days agoHandshake completed134 ms
11 days agoHandshake completed132 ms
13 days agoHandshake completed91 ms
15 days agoHandshake completed129 ms
17 days agoHandshake completed55 ms
19 days agoHandshake completed316 ms
20 days agoHandshake completed67 ms
21 days agoHandshake completed60 ms
22 days agoHandshake completed61 ms

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