Sparka MCP server

• Registry nameio.sparka/sparkaverified in the MCP registry

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

• Stateanswerschecked 2026-11-02
• Tools8
• Server calls itselfsparka
• Server version0.1.0
• Protocol version2025-06-18

On 2026-11-02 the server answered initialize and tools/list without a sign-in. First answer in 386 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 2 of the 7 days it takes to judge reliability.

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.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
• Answeredmeasuring2 of the 7 daily checks it takes to print a share
• Median first answer1047 ms
• Space in an agent's context≈ 2,864 tokensthe definitions of all its tools (8), which an agent carries on every turn
• Tool definitionsB · 88 of 100
• Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 6 of 8

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 →

• sparka_account_get

  Returns the account's plan, limits (participants per session, sessions per month, presentations, concurrent live sessions), usage this period, a `summary` sentence with the same numbers, and `pricing_url`, the public page listing the…

• sparka_deck_guide

  Returns the rules and a reference JavaScript pattern for making an HTML presentation interactive with Sparka: Start/End buttons and their labels, a lobby with the QR code, PIN and join URL that can be opened from any slide, switching the…

• sparka_presentation_delete

  Permanently deletes a presentation and ends its live session if one is running. Results of past sessions stay readable with `sparka_results_get` by `session_id` until their retention ends. Decks using this `presentation_id` stop working…

• sparka_presentation_get

  Returns one presentation: title, settings, questions (with correct answers unless `include_answers` is false), the live session if one is running (PIN, participants), and the most recent sessions. Useful for editing an existing…

• sparka_presentation_list

  Lists the account's presentations, newest first, with title, question count, last update and last session time. Useful when the user refers to a presentation without giving its ID ("results from yesterday's talk"). Paginated with `cursor`.

• sparka_presentation_save

  Creates or fully replaces a presentation's interactive questions in one call. Each call carries the COMPLETE presentation: title, optional settings, and the ordered list of all questions including correct answers for scored types (valid…

• sparka_question_types_list

  Lists every interactive question type Sparka supports, with its JSON schema, a short guide on when to use it, and a valid example. `sparka_presentation_save` accepts only these types and fields; unknown fields are rejected. Each question…

• sparka_results_get

  Returns results for a session: per question, the counts or words, the correct answer and how many got it right for scored questions, participant count, and the final leaderboard. Takes `session_id`, or `presentation_id` for its most…