SSTV Decoder
REMOTE · BONISSYSTEMS.COM · SCANNED SEP 20
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.
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 Security63
- 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 connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- 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 Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the SSTV Decoder MCP server?
SSTV Decoder is a hosted endpoint at https://bonissystems.com/api/knox/agents/sstv-decoder/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 · bonissystems.com
claude mcp add --transport http com-bonissystems-sstv-decoder 'https://bonissystems.com/api/knox/agents/sstv-decoder/mcp'
{
"mcpServers": {
"com-bonissystems-sstv-decoder": {
"url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
}
}
} {
"servers": {
"com-bonissystems-sstv-decoder": {
"type": "http",
"url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
}
}
} [mcp_servers.com-bonissystems-sstv-decoder] url = "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-bonissystems-sstv-decoder": {
"type": "remote",
"url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp",
"enabled": true
}
}
} openclaw mcp add com-bonissystems-sstv-decoder --url 'https://bonissystems.com/api/knox/agents/sstv-decoder/mcp' --transport streamable-http
mcp_servers:
com-bonissystems-sstv-decoder:
url: "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp" {
"McpServers": {
"com-bonissystems-sstv-decoder": {
"Transport": "http",
"Url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
}
}
} assistant mcp add com-bonissystems-sstv-decoder -t streamable-http -u 'https://bonissystems.com/api/knox/agents/sstv-decoder/mcp'
{
"mcpServers": {
"com-bonissystems-sstv-decoder": {
"type": "http",
"url": "https://bonissystems.com/api/knox/agents/sstv-decoder/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.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: 0.37 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 20 Sept 2026 · Probed https://bonissystems.com/api/knox/agents/sstv-decoder/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bonissystems.com | CN=YE1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 587c48f979e17617481499e75f1aca84203 |
| SANs: *.bonissystems.com, bonissystems.com | ||||||
| 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 bonissystems.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bonissystems.com. | 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; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.gstatic.com https://images.dmca.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://res.cloudinary.com https://utfs.io https://uploadthing.com https://lh3.googleusercontent.com https://storage.googleapis.com https://blockstream.info https://images.dmca.com https://*.tile.openstreetmap.org; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://api.anthropic.com https://bonissystems.com https://cloudflareinsights.com https://*.cloudinary.com https://*.polyhaven.org https://www.gstatic.com https://storage.googleapis.com https://blockstream.info https://*.livekit.cloud wss://*.livekit.cloud wss: ws:; media-src 'self' blob: https://res.cloudinary.com https://storage.googleapis.com; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bonissystems.com/api/knox/agents/sstv-decoder/mcp | Verified | 200 | |
| http (plaintext) | http://bonissystems.com/api/knox/agents/sstv-decoder/mcp | HTTPS enforced | 302 | https://bonissystems.com/api/knox/agents/sstv-decoder/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 →
decode_sstv ~321
Demodulate a presented slow-scan-television (SSTV) audio recording, anchor the audio fingerprint and the decoded image hash to the Knox event chain, and return a self-authenticating receipt bundle (Knox anchor + C2PA-aligned envelope + FRE 902(13)/(14)-shape affidavit). Audio bytes are NOT retained — only the SHA-256 fingerprint and the decoded image are anchored. Bonis Systems does not capture audio on its own; the audio must be presented by the caller (a public WebSDR recording, a customer-controlled SDR capture they consent to submit, or audio they own). Phase 1 supports Martin M1 (VIS code 0x2C, 320×256 RGB). Other VIS codes return mode = 'unsupported' with detected hex. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| audioBase64 | string | yes | Base64-encoded audio. Either a complete WAV file (RIFF/WAVE, 8/16/24-bit PCM or 32-bit IEEE float, mono or stereo, 4-192 kHz) or raw 16-bit signed little-endian mono PCM samples. |
| audioFormat | string | – | Audio container ('wav' default, or 'pcm16-mono'). |
| capture | object | – | Optional capture-context metadata. |
| name | string | yes | Display name for the recording (max 256 chars). |
| sampleRate | integer | – | Required when audioFormat = 'pcm16-mono'. |
No output schema declared.
No examples provided.
verify_sstv_decode ~97
Verify a previously anchored SSTV-decode record. Given a SHA-256 anchor hash (the payload_hash from a prior decode_sstv call), return the anchor record, predecessor hash, sequence number, and timestamp. Public — no authentication required. The verification path itself is also accessible at GET /api/knox/verify?hash=<hash>.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | SHA-256 anchor hash (64 lowercase hex chars). |
No output schema declared.
No examples provided.
What is the SSTV Decoder MCP server?
SSTV Decoder is an MCP server listed in the public MCP registry as com.bonissystems/sstv-decoder. Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain. This page covers its hosted endpoint (https://bonissystems.com/api/knox/agents/sstv-decoder/mcp).
Is the SSTV Decoder MCP server safe to use?
SSTV Decoder scores 35 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 SSTV Decoder MCP server expose?
SSTV Decoder exposes 2 tools: decode_sstv, verify_sstv_decode. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.
Does the SSTV Decoder MCP server require authentication?
No. We connected to SSTV Decoder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SSTV Decoder MCP server still maintained?
SSTV Decoder is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.