Remote MCP · Endpoint

Fieldwright MCP server

No. Fieldwright answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://fieldwright.cybermaxtools.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
dev.workers.cybermax-tools.cybermax/fieldwright
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
153 ms
Tools exposed
1 tool
Uptime, last 30 days
100% 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 completed153 ms
1 day agoHandshake completed85 ms
2 days agoHandshake completed89 ms
3 days agoHandshake completed79 ms
4 days agoHandshake completed96 ms
5 days agoHandshake completed158 ms
7 days agoHandshake completed174 ms
10 days agoHandshake completed85 ms
12 days agoHandshake completed99 ms
14 days agoHandshake completed193 ms
17 days agoHandshake completed54 ms
19 days agoHandshake completed153 ms
21 days agoHandshake completed81 ms
23 days agoHandshake completed87 ms
25 days agoHandshake completed57 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 Fieldwright and makes no claim about it beyond what these checks measured.