mcpbeat

SSTV Decoder MCP Server

com.bonissystems/sstv-decoder
answering

SSTV Decoder is answering right now. Last checked 11 min ago. It exposes 2 tools.

Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
256 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add sstv-decoder --transport http https://bonissystems.com/api/knox/agents/sstv-decoder/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sstv-decoder": {
      "url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sstv-decoder]
url = "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sstv-decoder": {
      "url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sstv-decoder": {
      "url": "https://bonissystems.com/api/knox/agents/sstv-decoder/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

decode
decode_sstv
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.
verify
verify_sstv_decode
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>.

Endpoints

URLTransportStateLatencyChecked
https://bonissystems.com/api/knox/agents/sstv-decoder/mcp streamable-http answering 318 ms 11 min ago

SSTV Decoder — questions

Answers built from our own checks of this server.

What can SSTV Decoder do?
It exposes 2 tools, read directly from the server on our last check. Among them: decode_sstv, verify_sstv_decode. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SSTV Decoder working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 256 ms. The bar chart above shows every period we have measured.
How do I connect SSTV Decoder?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SSTV Decoder need an API key?
No. SSTV Decoder completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SSTV Decoder?
It answers our handshake in 256 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.