Remote MCP · Endpoint

RFQdecoder MCP server

No. RFQdecoder answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rfqdecoder.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Mounirt879/rfqdecoder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
933 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Should-cost of a machined, sheet metal or cast part from its PDF, DXF or STEP drawing, line by line.
Listing
From the official MCP registry (active).
Recent checks of RFQdecoder
CheckedResultHandshake
1 hour agoHandshake completed933 ms
6 hours agoHandshake completed705 ms
2 days agoHandshake completed374 ms
4 days agoHandshake completed755 ms
7 days agoHandshake completed431 ms
9 days agoHandshake completed1.05 s
11 days agoHandshake completed759 ms
13 days agoHandshake completed365 ms
15 days agoHandshake completed857 ms
17 days agoHandshake completed1.20 s
19 days agoHandshake completed552 ms
21 days agoHandshake completed628 ms
23 days agoHandshake completed739 ms
24 days agoHandshake completed540 ms
25 days agoHandshake completed1.04 s

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