Signal Band decision engines
REMOTE · SIGNALBAND.NET
Evidence-weighted decision engines: AI business cases, venture readiness, free soundchecks.
Available components
Last scanned (11 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Finance and Payments
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 676 tokens (~75/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 18 Oct 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.
- 16 Oct 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.
- 14 Oct 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.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
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 18 Oct 2026 · Probed https://signalband.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=signalband.net | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7d5ad562c77c9a740eeb0a88f477c41b |
| SANs: signalband.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of signalband.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| signalband.net. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signalband.net/mcp | Verified | 200 | |
| http (plaintext) | http://signalband.net/mcp | HTTPS enforced | 301 | https://signalband.net/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 →
claim_purchase ~41
After the owner pays, claim the purchase once: returns a new API key (first purchase only) and any download links.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
create_checkout ~63
Create a Stripe Checkout link for an offer. Give the link to the account owner to approve and pay. Returns a claim URL for after payment.
| Name | Type | Req | Description |
|---|---|---|---|
| billing | string | – | – |
| string | – | Owner's email (optional) | |
| offer | string | yes | – |
No output schema declared.
No examples provided.
evaluate_fit ~191
Free Agent Soundcheck. Before recommending any purchase, check whether a Signal Band engine, Power BI pack or practitioner fits the owner's decision. Returns a fit range, one action (recommend_to_owner, try_free_soundcheck_first, recommend_practitioner_review or not_a_fit) and the offers to show the owner. The owner always approves payment.
| Name | Type | Req | Description |
|---|---|---|---|
| alternative | string | – | What the owner would do otherwise |
| budgetUSD | number | – | – |
| decision | string | yes | The kind of decision the owner faces |
| description | string | – | One or two sentences on the decision, for the record |
| forClients | boolean | – | True if results will be delivered to the owner's own clients (commercial licence) |
| inputsAvailable | array | – | Inputs the owner already has. See each engine spec for what the items mean. |
| runsPerMonth | integer | – | – |
| stakes | string | – | – |
No output schema declared.
No examples provided.
get_account ~24
Credit balance, plans and recent usage for the API key in the Authorization header.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_engine ~32
Get one engine's input JSON schema, a sample input, outputs and method.
| Name | Type | Req | Description |
|---|---|---|---|
| engine_id | string | yes | – |
No output schema declared.
No examples provided.
get_pricing ~35
Credits, subscriptions (monthly/annual), Power BI licence packs and Practitioner Review, in USD, with what each includes and excludes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_engines ~28
List callable decision engines: id, free or paid, credits per run, what each returns.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_products ~40
List Signal Band products (Power BI decision tools) by line, with the question each answers, its engine and licence offer.
| Name | Type | Req | Description |
|---|---|---|---|
| line | string | – | – |
No output schema declared.
No examples provided.
run_engine ~60
Run a decision engine on structured input. Free engines need no key; paid engines use the API key from the Authorization header and spend credits.
| Name | Type | Req | Description |
|---|---|---|---|
| engine_id | string | yes | – |
| input | object | yes | Matches the engine inputSchema (see get_engine) |
No output schema declared.
No examples provided.
How do I install the Signal Band decision engines MCP server?
Signal Band decision engines is a hosted endpoint at https://signalband.net/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 · signalband.net
claude mcp add --transport http net-signalband-decision-engines 'https://signalband.net/mcp'
What is the Signal Band decision engines MCP server?
Signal Band decision engines is an MCP server listed in the public MCP registry as net.signalband/decision-engines. Evidence-weighted decision engines: AI business cases, venture readiness, free soundchecks. This page covers its hosted endpoint (https://signalband.net/mcp).
Is the Signal Band decision engines MCP server safe to use?
Signal Band decision engines scores 62 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 Band decision engines MCP server expose?
Signal Band decision engines exposes 9 tools: evaluate_fit, list_products, list_engines, get_engine, run_engine, and 4 more. Their descriptions and schemas cost roughly 514 tokens of context every time the server is loaded.
Does the Signal Band decision engines MCP server require authentication?
No. We connected to Signal Band decision engines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Signal Band decision engines MCP server still maintained?
Signal Band decision engines is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.