genpark-jitter-buffer

io.github.Alpha-ParkPublished by GitHub account Alpha-Parkv1.0.1Updated Oct 24, 2026

Packet ordering simulation and inter-arrival jitter telemetry.

VerifiedSTDIODesktop onlyData & AnalyticsMedia & Design

Overview

AI-generated overview

A local stdio MCP server that simulates audio packet ordering and reports inter-arrival jitter telemetry, with tools to ingest packets, extract playout frames,

What you can do
Ingest packet metadata into a jitter buffer simulation and extract playout frames from it, with missing packets marked rather than synthesized. Read inter-arrival jitter telemetry from the buffer state. Run an isolated benchmark jitter simulation for comparison. Each MCP process keeps its own state, and benchmark tools use separate instances.
When to use it
Useful when you want an assistant to explore packet reordering and jitter behavior on already-prepared packet metadata, or to run a quick benchmark simulation, without a real WebRTC stack or audio codec.
Requirements
Python 3.9 or newer on the local machine; the library and stdio server have no runtime dependencies. Install the wheel from the GitHub release, then point the MCP client at the installed command or python -m genpark_jitter_buffer. The .mcpb desktop bundle also needs a Python 3.9+ interpreter on PATH. PyPI publication is pending, so the plain package name may not be installable yet.
Before you install
This is a packet metadata simulation, not a WebRTC implementation or audio codec: timestamps must already be in milliseconds and sequence numbers monotonically extended, missing packets yield markers, and target_delay_ms is telemetry rather than an enforced timer. The caller controls playout timing. Install from the GitHub release rather than assuming the PyPI package exists.

Installation

In SourceWeft

  1. Open genpark-jitter-buffer in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

genpark-jitter-buffer

Packet ordering simulation and inter-arrival jitter telemetry.

This is a packet metadata simulation, not a WebRTC implementation or audio codec. Timestamps must already be converted to milliseconds, and sequence numbers must be monotonically extended (no RTP wraparound). Missing packets produce markers, not synthesized audio. The caller controls playout timing; target_delay_ms is telemetry, not an enforced timer.

Install from the GitHub release

Python 3.9 or newer. The library and stdio MCP server have no runtime dependencies.

sh
python -m pip install https://github.com/Alpha-Park/genpark-audio-packet-jitter-resilience-buffer-skill/releases/download/v1.0.1/genpark_jitter_buffer-1.0.1-py3-none-any.whl

PyPI publication is pending account setup. The intended PyPI project is genpark-jitter-buffer; do not assume pip install genpark-jitter-buffer is available until the project is published.

Python usage

python
from genpark_jitter_buffer import AudioPacketJitterResilienceBufferclient = AudioPacketJitterResilienceBuffer()print(client.run_benchmark_jitter_simulation())

MCP stdio configuration

After installing the wheel, configure your MCP client with the installed command:

json
{  "mcpServers": {    "genpark-jitter-buffer": {      "command": "genpark-jitter-buffer",      "args": []    }  }}

If the command is not on PATH, use its absolute path or python -m genpark_jitter_buffer with the same interpreter where you installed the wheel. The GitHub release also contains a .mcpb bundle for clients supporting desktop extensions. That bundle requires a Python 3.9+ interpreter on PATH; it bundles the server source.

Available tools: ingest_packet, extract_playout_frame, get_jitter_telemetry, run_benchmark_jitter_simulation. tools/list returns required arguments and JSON schemas. Each MCP process holds its own state. Benchmark tools use isolated instances.

Development

sh
python -m unittest discover -s testspython -m pip install mcppython tests/check_mcp.pypython -m pip install build twinepython -m buildpython -m twine check dist/*

python mcp_server.py --test runs the deterministic example; it is not a protocol conformance test. The MCP client check exercises initialize, tools/list, tools/call and ping over stdio.

Distribution

GitHub source and release artifacts are the primary distribution until PyPI is configured. Registry submissions are tracked separately; a manifest is not proof of registry acceptance. See PUBLISHING.md for the repeatable PyPI workflow.

MIT license. Maintained by GenPark.

Source: README.md at commit b674446

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 27, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.