Skip to content

MCP servers › io.pitchboom › pitchboom

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

io.pitchboom/pitchboom

by pitchboom.io · domain (the registry's namespace rule)repository owner on GitHub: arseneHuot (personal account)Source ↗Website ↗

Motion-design video ads from a product URL or brief: script, storyboard, voice-over, music, MP4. — the publisher's description

4 of 4 record checks metRead-only · tools listed 2026-10-27version 1.2.0JavaScriptstreamable HTTP18 tools

Summary

io.pitchboom/pitchboom is a remote MCP server listed in the official MCP registry at version 1.2.0, under the namespace of the domain pitchboom.io. Its linked repository is github.com/arseneHuot/pitchboom; GitHub reports its owner as arseneHuot, a personal account. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 18 tools, 0 resources and 0 prompts.

Record checks

4 of 4 record checks met · 4 do not apply · 1 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not checked: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
18
Last tested
2026-10-27

Tool list size

9,794 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (18 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (pitchboom.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.2.0).

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (create_project, confirm_operation, cancel_job, update_storyboard, approve_storyboard and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-27.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-27
Mode
read-only (no tool calls)
Latest version
1.2.0, published 2026-10-26 (registry, as of the 2026-10-27 snapshot)
First listed version
2026-10-25 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-10-25 to 2026-10-26; 3 in the 90 days before the 2026-10-27 snapshot.
Most recent 3 versions
  • 1.2.0 · 2026-10-26
  • 1.1.0 · 2026-10-25
  • 1.0.0 · 2026-10-25
(versions still listed in the registry only)
Registry data
snapshot 2026-10-27
Package and repository
checked 2026-10-27
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.1.0 (published 2026-10-25) → 1.2.0 (published 2026-10-26), between the registry lists of 2026-10-26 and 2026-10-27.

The publisher published no GitHub release note for version 1.2.0: the repository has no release tagged for it.

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27; release notes from the GitHub Releases API, checked 2026-10-27.

What it is

What does this server offer?

Observed inventory
18tools
0resources
0prompts

None of its 18 tools are described as changing anything. For 18 the reading was uncertain, so no mark is shown.

  • get_credit_balanceon 25 other servers

    “Your pitchboom credit balance (available and on hold), recent usage, plan, monthly grant and 4K policy, plus this API key's permissions.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Every accepted value for create_project / request_variant: goals (the seven presets, and custom: the user's own goal in one line), platforms, aspect ratios, durations (up to your plan's maximum), qua…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    8 inputs
    • languagestring“List the voices that speak this language (native speakers first, then multilingual voices), filtered by the voice_* fields and paged.”
    • voice_genderstring“With language: only voices of this gender.”
    • voice_agestring“With language: only voices of this age.”
    • voice_stylestring“With language: voices with any of these styles (comma-separated): narrator, advertising, conversational, energetic, calm, warm, authoritative, deep, bright, pl…”
    • voice_accentstring“With language: one accent (values in voice_filters.accent of a first call).”
    • voice_searchstring“With language: words to find in the name, description, accent or styles (any language, e.g.”
    • voice_cursorstring“With language: voices_next_cursor of the previous page.”
    • voice_limitinteger“With language: voices per page (default 24, at most 100).”
  • list_brand_kitson 2 other servers

    “Your Brand Kits (id, name, colors, fonts, tone, tagline, website, default flag).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • “Your projects, newest first: title, status, source URL, settings and video counts.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs
    • cursorstring“next_cursor of the previous page”
    • limitinteger
  • “One project: settings, site-analysis status, its videos with their status and latest job, and any open quote.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • project_idstringrequired
  • “Free (no credits; counts toward your plan's daily URL analyses).”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • urlstringrequired
    • project_idstring“A draft project to analyse into (default: a new draft project).”
    • languagestring
  • create_projecton 92 other servers

    “Step 1 of 2: nothing is charged.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    19 inputs, 1 required
    • urlstring“Website or product page to analyse (free).”
    • briefstring“What to say: product, audience, offer, angle.”
    • titlestring
    • goalstringrequired“sales, signups, app_installs, launch, awareness, explainer or retarget; or custom, with goal_description (the user's own goal).”
    • goal_descriptionstring“With goal custom (required then): the user's own goal in one line, ≤ 140 characters — what viewers should do after watching ("Book a free 15-minute call with o…”
    • platformstring“Where it runs; sets the default aspect and safe zones.”
    • aspectstring
    • duration_secondsinteger
    • qualitystring“standard (default) or studio: one rate per second each (get_options qualities).”
    • tierstring“Deprecated: use quality.”
    • resolutionstring
    • languagestring“The films' language (voice-over, on-screen text, title).”
    • voice_idstring“A voice id from get_options; default: one that suits the goal, a native speaker of the language where we have one.”
    • music_moodstring
    • captionsboolean“Burned-in subtitles of the voice-over (default off: the video already shows its key words on screen).”
    • quantityinteger“Independent variants of the same brief (plan maximum in get_options).”
    • brand_kit_idstring“From list_brand_kits; default: the account's default kit.”
    • visibilitystring“Default: the account setting (public in the gallery unless changed).”
    • lookstring“The film's look: auto (default, picked from your brand) or a style family: editorial-paper, dark-tech, playful, luxe-editorial, bold-retail, soft-gradient, bru…”
  • get_estimateon 4 other servers

    “Nothing is charged.”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world no

    3 inputs
    • quote_idstring“Read an existing quote.”
    • project_idstring“A fresh quote to launch this draft project.”
    • quantityinteger“With project_id: how many videos (default: the project's).”
  • confirm_operation

    “Step 2 of 2: holds the quoted credits and starts the work.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • quote_idstringrequired“From create_project, get_estimate, request_variant or edit_video.”
  • get_job_statuson 28 other servers

    “Status of a job (or of a video's latest job): steps, progress, credits held / used / released, whether it waits for storyboard approval, errors.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs
    • job_idstring
    • video_idstring“Instead of job_id: the video's latest job.”
    • wait_secondsinteger“Wait up to this long for the status or step to change.”
  • “Stops a queued, running or approval-waiting job.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    1 input, 1 required
    • job_idstringrequired
  • get_storyboardon 1 other server

    “A video's storyboard: scenes in order (scene_id, role, template, estimated timing, voice-over, on-screen texts with their ids), CTA, voice, music and spec_version (needed to edit).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input, 1 required
    • video_idstringrequired
Show 6 more tools
  • update_storyboardon 1 other server

    “Free.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 3 required
    • video_idstringrequired
    • base_spec_versionintegerrequired
    • opsarrayrequired
  • approve_storyboard

    “Resumes a video waiting for storyboard approval: voice-over, music and render run with the credits held at confirm.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world no

    3 inputs, 1 required
    • job_idstring
    • video_idstring“Instead of job_id: the video whose storyboard waits for approval.”
    • max_totalintegerrequired“The total (credits) the user accepted; nothing happens if the price is higher.”
  • “Your videos, newest first, optionally for one project or status (queued, storyboarding, storyboard_ready, rendering, ready, failed, canceled).”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs
    • project_idstring
    • statusstring
    • cursorstring“next_cursor of the previous page”
    • limitinteger
  • “One video: status, settings, visibility, public page, versions and, for rendered versions, signed download URLs (MP4 1080p / 4K, poster) valid 1 hour: download right away, never store or share them.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • video_idstringrequired
    • include_download_urlsboolean
  • request_variant

    “Step 1 of 2: nothing is charged.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    7 inputs, 2 required
    • video_idstringrequired
    • kindstringrequired
    • languagesarray“translate: target language codes (get_options).”
    • aspectsarray“reformat: target aspect ratios.”
    • countinteger“recreate: how many new takes.”
    • voice_idstring“translate: a voice from get_options (default: the video's voice when it is a native speaker of the language, else a native voice of the language).”
    • visibilitystring“Default: the same as the source video (recreate: the project's choice if it made one; a project made from code starts private).”
  • “Edits a rendered video with the same ops as update_storyboard.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world no

    3 inputs, 3 required
    • video_idstringrequired
    • base_spec_versionintegerrequired
    • opsarrayrequired

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
59% of 64
Tools with a description
100% of 18
Typical description length
295 characters

The tool set

Counted from the listing

Tools
18
Size of the list
about 5,884 tokens for an agent to load (characters ÷ 4)
Naming
18 of 18 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 18 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://pitchboom.io/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "pitchboom": {
      "url": "https://pitchboom.io/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "pitchboom": {
      "type": "http",
      "url": "https://pitchboom.io/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"pitchboom","type":"http","url":"https://pitchboom.io/api/mcp"}'
Claude Code
claude mcp add --transport http pitchboom https://pitchboom.io/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "pitchboom": {
      "type": "streamableHttp",
      "url": "https://pitchboom.io/api/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "pitchboom": {
      "httpUrl": "https://pitchboom.io/api/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.pitchboom]
url = "https://pitchboom.io/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "pitchboom": {
      "url": "https://pitchboom.io/api/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://pitchboom.io/api/mcp --transport http
  • Optional settings the entry also lists (left out above): Authorization.
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint pitchboom.io/api/mcpSession openedmatchesour test · 2026-10-27
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-27
Repository github.com/arseneHuot/pitchboomOpens publiclymatchesapi.github.com · 2026-10-27

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.pitchboom
GitHub owner
a personal account (arseneHuot)
Repository
github.com/arseneHuot/pitchboom
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no

Source: the registry entry and api.github.com · 2026-10-27.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint pitchboom.io/api/mcp

No change in the tool list across 2 reads (2026-10-26 to 2026-10-27; versions 1.1.0 to 1.2.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-10-27 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 4 record checks met · 4 do not apply · 1 not checked

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.pitchboom/pitchboom

Answered from the data above

Who publishes io.pitchboom/pitchboom?

The registry ties the namespace io.pitchboom to the domain pitchboom.io; only its owner can publish under it. Its linked repository is github.com/arseneHuot/pitchboom; GitHub reports its owner as arseneHuot, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.pitchboom/pitchboom safe to install?

We do not rate servers as safe or unsafe. 4 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.pitchboom/pitchboom need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.pitchboom/pitchboom been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Where is the source code of io.pitchboom/pitchboom?

In github.com/arseneHuot/pitchboom, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,149 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 18 tools, 0 resources, 0 prompts.
  4. 6,264 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-27; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
api.github.com · 2026-10-27
Hosting type
registry · 2026-10-27
MCP capability
tools
our test · 2026-10-27
Transport
streamable HTTP
registry · 2026-10-27
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-27
Lifecycle status
registry · 2026-10-27
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-27
Maintenance
api.github.com · 2026-10-27
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.pitchboom/pitchboom: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.pitchboom/pitchboom

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 4 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.pitchboom/pitchboom)](https://protocolprobe.com/mcp/servers/io.pitchboom/pitchboom)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology