GenPark Tool Call Latency Profiler Metrics

io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Oct 26, 2026

High-resolution MCP tool call latency profiler and P50/P90/P95/P99 telemetry metrics collector

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.github.alphaparkinc/genpark-tool-call-latency-profiler-metrics-skill
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account alphaparkinc for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.alphaparkinc%2Fgenpark-tool-call-latency-profiler-metrics-skill.svg)](https://sourceweft.com/mcp/io.github.alphaparkinc%2Fgenpark-tool-call-latency-profiler-metrics-skill?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that profiles MCP tool call latency and collects P50/P90/P95/P99 telemetry metrics at high resolution.

What you can do: Profiles tool call latency for MCP servers at high resolution.
Collects percentile telemetry metrics (P50, P90, P95, P99) from those measurements.
No individual tools are listed in the manifest, so the exact operations the assistant can invoke are not documented here.
When to use it: Worth considering when you want to measure how long MCP tool calls take and keep percentile latency statistics for comparison or tuning. It is a niche diagnostics add-on rather than a general-purpose tool.
Requirements: Runs as a local process on the user's machine over stdio, installed from an .mcpb package; desktop client only, no web execution. No authentication, environment variables or headers are declared.

Before you install

The manifest lists no tools, instructions or README, so what it records and where any collected metrics go cannot be verified before installing. Review the package contents and confirm whether latency data leaves your machine.

Installation

In SourceWeft

Open GenPark Tool Call Latency Profiler Metrics in the dashboard and add it to a workspace.
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

This repository has no README.

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

v1.0.1LatestOct 21, 2026

Score

25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.