MCP.Market

genpark-jitter-buffer MCP server

by Alpha-Park·io.github.Alpha-Park/genpark-jitter-buffer·v1.0.1·7 stars

Packet ordering simulation and inter-arrival jitter telemetry.

A90/100grade A
What users say
No reviews yet
Be the first
Safety scan
A90/100

full report

Adoption
Growing

7 stars

Reviews

Write one

Nobody has reviewed genpark-jitter-buffer yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

genpark-jitter-buffer tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 90/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How genpark-jitter-buffer compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
90/100
higher than 83% of 48,255 servers
GitHub stars
7
more than 86% of 28,688 servers

Install genpark-jitter-buffer in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the genpark-jitter-buffer repository's README, as published. We do not edit it. Read it on GitHub

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; targetdelayms 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.

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

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

MCP stdio configuration

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

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

If the command is not on PATH, use its absolute path or python -m genparkjitterbuffer 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: ingestpacket, extractplayoutframe, getjittertelemetry, runbenchmarkjittersimulation. tools/list returns required arguments and JSON schemas. Each MCP process holds its own state. Benchmark tools use isolated instances.

Development

python -m unittest discover -s tests
python -m pip install mcp
python tests/check_mcp.py
python -m pip install build twine
python -m build
python -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.

<!-- mcp-name: io.github.Alpha-Park/genpark-jitter-buffer -->

Nothing above is checked by us. What we check is on the safety report.

genpark-jitter-buffer: common questions

Is genpark-jitter-buffer MCP server safe?
Yes, by our scan: it is graded A (90/100). Read the genpark-jitter-buffer safety report
Does genpark-jitter-buffer need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is genpark-jitter-buffer maintained?
The last commit was 38 days ago (2026-09-27). The latest release is v1.0.1.
How does genpark-jitter-buffer compare with other MCP servers?
safety score 90/100 (higher than 83% of 48,255 servers); github stars 7 (more than 86% of 28,688 servers). Full comparison.

More from Alpha-Park →