40trust / 100

Signal Nodus SEC Filings

MCP serverFailing, checked 4 h ago

Amendment-safe 10-K/10-Q section diffs, claim checks vs XBRL, 8-K events. Accuracy published.

https://mcp.signalnodus.ai/

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 4 h ago: initialize returned HTTP 410

Add it to any MCP client that supports remote servers. It asks for sign-in, an API key or payment.

{
  "mcpServers": {
    "signal-nodus-sec-filings": {
      "type": "http",
      "url": "https://mcp.signalnodus.ai/"
    }
  }
}

The tool list is behind sign-in or payment, so we can't show it.

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

When	Result	HTTP	Time
4 h ago	initialize returned HTTP 410	410	160 ms
33 h ago	initialize returned HTTP 410	410	134 ms
2 days ago	initialize returned HTTP 410	410	145 ms
4 days ago	initialize returned HTTP 410	410	462 ms
5 days ago	initialize returned HTTP 410	410	760 ms

Show 3 older checks

Availability (30-day uptime)		0 / 35
Response time		0 / 15
Security scan		20 / 20
Transparency (repo, homepage, docs)		15 / 15
Recently checked		5 / 5
Verified owner		0 / 10

Verify ownership to get the badge and 10 more trust points. Featured placement needs it too.

Changed something? Scan it now and see what agents read.

Badges for your README or docs. They update with every check and link here.

Trust score

[![ToolVet trust score](https://toolvet.app/badge/signal-nodus-sec-filings.svg)](https://toolvet.app/s/signal-nodus-sec-filings)

MCP scan grade

From the findings of our latest check. It links to them.

[![ToolVet MCP scan](https://toolvet.app/badge/signal-nodus-sec-filings/scan.svg)](https://toolvet.app/s/signal-nodus-sec-filings#h-sec)