GenPark Audio Packet Jitter Resilience Buffer
MCPB · GENPARK-JITTER-BUFFER.MCPB
Adaptive WebRTC jitter buffer simulation and inter-arrival jitter telemetry
Available components
Last scanned (18 hours ago)
Scores higher than 74% of MCPB servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability47
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 93 tokens (~23/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 33
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed mcpb/https://github.com/Alpha-Park/genpark-audio-packet-jitter-resilience-buffer-skill/releases/download/v1.0.1/genpark-jitter-buffer.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
extract_playout_frame ~15
extract playout frame
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_jitter_telemetry ~16
get jitter telemetry
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ingest_packet ~44
ingest packet
| Name | Type | Req | Description |
|---|---|---|---|
| arrival_ms | number | yes | – |
| payload_bytes | integer | yes | – |
| rtp_timestamp | number | yes | – |
| seq_num | integer | yes | – |
No output schema declared.
No examples provided.
run_benchmark_jitter_simulation ~18
run benchmark jitter simulation
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the GenPark Audio Packet Jitter Resilience Buffer MCP server?
GenPark Audio Packet Jitter Resilience Buffer ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 32d68852b0eb13fb98ee1e0dc279f729893d9c2e7546ab2b51ea9401af58d79c; the commands to do that are on this page. If it does not match, do not open it.
mcpb · genpark-jitter-buffer.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
32d68852b0eb13fb98ee1e0dc279f729893d9c2e7546ab2b51ea9401af58d79c
macOS / Linux
echo "32d68852b0eb13fb98ee1e0dc279f729893d9c2e7546ab2b51ea9401af58d79c genpark-jitter-buffer.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\genpark-jitter-buffer.mcpb).Hash -eq "32d68852b0eb13fb98ee1e0dc279f729893d9c2e7546ab2b51ea9401af58d79c"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the GenPark Audio Packet Jitter Resilience Buffer MCP server?
GenPark Audio Packet Jitter Resilience Buffer is an MCP server listed in the public MCP registry as io.github.alphaparkinc/genpark-audio-packet-jitter-resilien…. Adaptive WebRTC jitter buffer simulation and inter-arrival jitter telemetry. This page covers its MCPB bundle (https://github.com/Alpha-Park/genpark-audio-packet-jitter-resilience-buffer-skill/releases/download/v1.0.1/genpark-jitt…).
Is the GenPark Audio Packet Jitter Resilience Buffer MCP server safe to use?
GenPark Audio Packet Jitter Resilience Buffer scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the GenPark Audio Packet Jitter Resilience Buffer MCP server expose?
GenPark Audio Packet Jitter Resilience Buffer exposes 4 tools: ingest_packet, extract_playout_frame, get_jitter_telemetry, run_benchmark_jitter_simulation. Their descriptions and schemas cost roughly 93 tokens of context every time the server is loaded.
What licence is the GenPark Audio Packet Jitter Resilience Buffer MCP server under?
GenPark Audio Packet Jitter Resilience Buffer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.