Remote MCP · Endpoint

Fieldwright MCP server

No. Fieldwright answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://fieldwright.cybermax-tools.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.shawmena-dotcom/ai-extract
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 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 day agoHandshake completed152 ms
4 days agoHandshake completed107 ms
6 days agoHandshake completed160 ms
7 days agoHandshake completed65 ms
9 days agoHandshake completed112 ms
10 days agoHandshake completed197 ms
11 days agoHandshake completed126 ms
14 days agoHandshake completed80 ms
15 days agoHandshake completed150 ms
17 days agoHandshake completed78 ms
18 days agoHandshake completed70 ms
20 days agoHandshake completed93 ms
21 days agoHandshake completed63 ms
22 days agoHandshake completed101 ms

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

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.