Remote MCP · Endpoint

WSDL 2.0 interface count, markup discarded MCP server

No. WSDL 2.0 interface count, markup discarded answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/wsdl2-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/wsdl2-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
42 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
WSDL 2.0 interface count, markup discarded
Repository
https://github.com/sadri-dridi/named-mcp-utilities
Listing
From the official MCP registry (active).
Recent checks of WSDL 2.0 interface count, markup discarded
CheckedResultHandshake
18 minutes agoHandshake completed42 ms
9 days agoHandshake completed168 ms
9 days agoHandshake completed30 ms
11 days agoHandshake completed28 ms
12 days agoHandshake completed22 ms
13 days agoHandshake completed48 ms
14 days agoHandshake completed16 ms
15 days agoHandshake completed22 ms
16 days agoHandshake completed28 ms
19 days agoHandshake completed51 ms
22 days agoHandshake completed33 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed24 ms
28 days agoHandshake completed17 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with WSDL 2.0 interface count, markup discarded and makes no claim about it beyond what these checks measured.