Remote MCP · Endpoint

Owasp MCP server

No. Owasp answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/owasp/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/owasp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
324 ms
Tools exposed
48 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
OWASP MCP — keyless.
Website
https://pipeworx.io/packs/owasp
Repository
https://github.com/pipeworx-io/mcp-owasp
Listing
From the official MCP registry (active).
Recent checks of Owasp
CheckedResultHandshake
1 hour agoHandshake completed324 ms
21 hours agoHandshake completed222 ms
2 days agoHandshake completed113 ms
3 days agoHandshake completed109 ms
4 days agoHandshake completed96 ms
5 days agoHandshake completed109 ms
6 days agoHandshake completed67 ms
8 days agoHandshake completed126 ms
11 days agoHandshake completed66 ms
13 days agoHandshake completed65 ms
16 days agoHandshake completed77 ms
18 days agoHandshake completed52 ms
20 days agoHandshake completed64 ms
22 days agoHandshake completed56 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed64 ms
27 days agoHandshake completed62 ms
29 days agoHandshake completed57 ms

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

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