Skip to content
DAX Foundation logo

DAX Foundation MCP server

Which MCP servers are DAX Foundation's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to DAX Foundation

Whose server it is
  • Registry nameorg.daxfoundation.signal/delta-signalverified in the MCP registry

The registry name sits under daxfoundation.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools5
  • Server calls itselfdelta-signal
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 296 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: make a personalised lesson set for one learner; quiz a learner and assess what they have reached; keep a learner's record of concepts reached.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 2 of 5 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer321 ms
  • Space in an agent's context≈ 919 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 93 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 5

What an agent can do with it

  • cannot · make a personalised lesson set for one learner
  • cannot · quiz a learner and assess what they have reached
  • cannot · keep a learner's record of concepts reached

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-29
  • describe_engine

    Free. Describe Delta Signal: layers, stings, defaults, limits and prices.

  • preview_card

    Free. Render the SSTV signature card image for a message (PNG) so you can see what the picture sting will carry.

  • render_signature

    Render a Delta Signal audio signature (WAV, 48 kHz) that hides your message: in the heartbeat rhythm, as text in the spectrogram, as an inaudible watermark, and optionally as an SSTV picture, a ggwave data chirp or modem tones. Returns a…

  • decode_audio

    Decode every Delta Signal layer from a WAV, MP3 or M4A (AAC) file at an https URL: heartbeat cipher, spectral glyph, prime count, watermark (needs the seed used to render), ggwave, modem text and SSTV pictures (returned as PNG).

  • verify_signature

    Verify a Delta Signal audio signature at an https WAV URL: returns which hidden layers are present (found_layers) and whether the audio matches an expected message (matches: true/false, or null if no expected_message given). Cheaper than…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "delta-signal": {
      "type": "http",
      "url": "https://signal.daxfoundation.org/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http daxfoundation https://signal.daxfoundation.org/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://signal.daxfoundation.org/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.