SSTV Decoder
REMOTE · BONISSYSTEMS.COM
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.
Available components
Last scanned (7 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Design and Media
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 call this server, and 2 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
- 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 Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 519 tokens (~259/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 Management73
- Stability observed for 22 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
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
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 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 | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d0f95770f49dd11e184ecfd671219da122 |
| 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' blob: 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 ~317
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 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.
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'
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 72 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 414 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.