Remote MCP · Endpoint

Signal Nodus SEC Filings MCP server

Yes, as of 6 hours ago: the server returned an HTTP error.

DownLast checked 6 hours ago

Server URL

https://mcp.signalnodus.ai/

The last check failed: the server returned an HTTP error.

Registry name
ai.signalnodus/sec-filings
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
31 tools
Uptime, last 30 days
47.1% from 17 checks
Described by its publisher as
Amendment-safe 10-K/10-Q section diffs, claim checks vs XBRL, 8-K events. Accuracy published.
Website
https://signalnodus.ai/
Repository
https://github.com/hgenix20/signalnodus
Listing
From the official MCP registry (active).
Recent checks of Signal Nodus SEC Filings
CheckedResultHandshake
6 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed393 ms
16 days agoHandshake completed174 ms
17 days agoHandshake completed184 ms
18 days agoHandshake completed320 ms
19 days agoHandshake completed163 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed31 ms
23 days agoHandshake completed234 ms

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

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