Remote MCP · Endpoint

Sec Beneficial Ownership MCP server

No. Sec Beneficial Ownership answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://gateway.pipeworx.io/sec-beneficial-ownership/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/sec-beneficial-ownership
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
803 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
SEC Schedule 13D / 13G — structured beneficial-ownership filings.
Listing
From the official MCP registry (active).
Recent checks of Sec Beneficial Ownership
CheckedResultHandshake
3 hours agoHandshake completed803 ms
1 day agoHandshake completed182 ms
4 days agoHandshake completed69 ms
7 days agoHandshake completed83 ms
9 days agoHandshake completed88 ms
11 days agoHandshake completed1.39 s
13 days agoHandshake completed1.93 s
15 days agoHandshake completed295 ms
18 days agoHandshake completed349 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed72 ms
23 days agoHandshake completed48 ms

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

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