Signal Ledger Financial Intelligence
REMOTE · 43-135-4-66.SSLIP.IO · SCANNED SEP 24
Paid bilingual MCP tools for evidence-linked SEC filing risk and finance-author track records.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 498 tokens (~249/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Signal Ledger Financial Intelligence MCP server?
Signal Ledger Financial Intelligence is a hosted endpoint at https://43-135-4-66.sslip.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · 43-135-4-66.sslip.io
claude mcp add --transport http blf2097-signal-ledger-financial-intelligence 'https://43-135-4-66.sslip.io/mcp'
{
"mcpServers": {
"blf2097-signal-ledger-financial-intelligence": {
"url": "https://43-135-4-66.sslip.io/mcp"
}
}
} {
"servers": {
"blf2097-signal-ledger-financial-intelligence": {
"type": "http",
"url": "https://43-135-4-66.sslip.io/mcp"
}
}
} [mcp_servers.blf2097-signal-ledger-financial-intelligence] url = "https://43-135-4-66.sslip.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"blf2097-signal-ledger-financial-intelligence": {
"type": "remote",
"url": "https://43-135-4-66.sslip.io/mcp",
"enabled": true
}
}
} openclaw mcp add blf2097-signal-ledger-financial-intelligence --url 'https://43-135-4-66.sslip.io/mcp' --transport streamable-http
mcp_servers:
blf2097-signal-ledger-financial-intelligence:
url: "https://43-135-4-66.sslip.io/mcp" {
"McpServers": {
"blf2097-signal-ledger-financial-intelligence": {
"Transport": "http",
"Url": "https://43-135-4-66.sslip.io/mcp"
}
}
} assistant mcp add blf2097-signal-ledger-financial-intelligence -t streamable-http -u 'https://43-135-4-66.sslip.io/mcp'
{
"mcpServers": {
"blf2097-signal-ledger-financial-intelligence": {
"type": "http",
"url": "https://43-135-4-66.sslip.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://43-135-4-66.sslip.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=43-135-4-66.sslip.io | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f4ec26b8c8960fa0dd1f6966b618be93ce |
| SANs: 43-135-4-66.sslip.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of 43-135-4-66.sslip.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| sslip.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://43-135-4-66.sslip.io/mcp | Verified | 200 | |
| http (plaintext) | http://43-135-4-66.sslip.io/mcp | HTTPS enforced | 308 | https://43-135-4-66.sslip.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_financial_report_risk Financial Report Risk Analysis / 财报风险体检 ~288
Paid full audit ($0.25 USDC): analyze financial-statement risk, earnings quality, cash-flow anomalies, accounting red flags, debt pressure, governance issues and data quality. Supply report text, or provide a US stock symbol to retrieve an official SEC filing automatically. Returns evidence-linked, machine-readable risk findings. / 收费完整体检（0.25 USDC）：识别财报风险、盈利质量、现金流异常、会计红旗、偿债压力、治理与数据质量问题；可提交原文，也可只提供美股代码自动获取 SEC 原始公告。
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Optional company name for text mode. |
| mode | string | – | Optional explicit mode. It is inferred from report_text or symbol when omitted. |
| period | string | – | latest, 2025/FY2025, 2025-Q4 or YYYY-MM-DD. |
| report_text | string | – | Plain text from a financial statement, annual report, quarterly report, SEC 10-K, 10-Q or 8-K filing. |
| report_type | string | – | Preferred filing/report type for symbol mode. |
| source_context | object | – | Optional provenance metadata for caller-supplied text. |
| symbol | string | – | US-listed ticker symbol, for example AAPL or BRK.B. The service fetches an official filing. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | – |
| error | object | – | – |
| mode | string | – | – |
| ok | boolean | yes | – |
| request_id | string | yes | – |
| scorecard | object | – | – |
| tool | string | – | – |
No examples provided.
get_author_track_record Author Track Record / 作者历史成绩 ~157
Paid lookup ($0.02 USDC): return a financial author's or stock commentator's resolved prediction history, sample size, hit rate, Wilson confidence interval, coverage, breakdowns and freshness. Useful for creator credibility, investment-influencer reputation and due-diligence workflows. / 收费查询（0.02 USDC）：返回财经作者或股票博主的历史观点成绩、命中率、样本量、置信区间、覆盖范围和数据新鲜度。
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | X/Twitter author handle, with or without @. |
| type | string | – | Filter claims by stock, industry or broad-market scope. |
| window_days | integer | – | Historical lookback window in days. |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | object | – | – |
| error | object | – | – |
| mode | string | – | – |
| ok | boolean | yes | – |
| request_id | string | yes | – |
| scorecard | object | – | – |
| tool | string | – | – |
No examples provided.
What is the Signal Ledger Financial Intelligence MCP server?
Signal Ledger Financial Intelligence is an MCP server listed in the public MCP registry as io.github.blf2097/signal-ledger-financial-intelligence. Paid bilingual MCP tools for evidence-linked SEC filing risk and finance-author track records. This page covers its hosted endpoint (https://43-135-4-66.sslip.io/mcp).
Is the Signal Ledger Financial Intelligence MCP server safe to use?
Signal Ledger Financial Intelligence scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Signal Ledger Financial Intelligence MCP server expose?
Signal Ledger Financial Intelligence exposes 2 tools: analyze_financial_report_risk, get_author_track_record. Their descriptions and schemas cost roughly 445 tokens of context every time the server is loaded.
Does the Signal Ledger Financial Intelligence MCP server require authentication?
No. We connected to Signal Ledger Financial Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Signal Ledger Financial Intelligence MCP server still maintained?
Signal Ledger Financial Intelligence is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.