mcp server
SSTV Decoder
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.
Description as published by the maintainer. Source
- version 1.0.0
- active
active — Registry entry last updated 2026-06-24.
What this server can do
2 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
decode_sstv(name, capture, sampleRate, audioBase64, audioFormat)- 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. Required: name, audioBase64.
verify_sstv_decode(hash)- 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>. Required: hash.
Last successful function declaration observed on . Source: https://bonissystems.com/api/knox/agents/sstv-decoder/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://bonissystems.com/api/knox/agents/sstv-decoder/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-24 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-24 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 2 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | bonissystems.com | |
| mcp endpoint status | ok | The server listed 2 functions when asked. | as of probe | bonissystems.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json