io.github.rog0x/perf
NPM · @ROG0X/MCP-PERF-TOOLS · SCANNED AUG 3
Benchmark, memory, Big O analysis for AI agents
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
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 133 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 475 tokens (~95/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @rog0x/mcp-perf-tools
claude mcp add rog0x-perf -- npx -y @rog0x/mcp-perf-tools
codex mcp add rog0x-perf -- npx -y @rog0x/mcp-perf-tools
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"rog0x-perf": {
"type": "local",
"command": [
"npx",
"-y",
"@rog0x/mcp-perf-tools"
],
"enabled": true
}
}
} openclaw mcp add rog0x-perf --command npx --arg -y --arg @rog0x/mcp-perf-tools
mcp_servers:
rog0x-perf:
command: "npx"
args: ["-y", "@rog0x/mcp-perf-tools"] {
"mcpServers": {
"rog0x-perf": {
"command": "npx",
"args": [
"-y",
"@rog0x/mcp-perf-tools"
]
}
}
} 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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 30 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/@rog0x/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
benchmark ~103
Benchmark JavaScript code execution. Run a snippet N times and measure min/max/avg/p95/p99 time and ops/sec. Optionally compare two implementations.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | JavaScript code to benchmark |
| compareCode | string | — | Optional second implementation to compare against |
| iterations | integer | — | Number of iterations to run |
| labelA | string | — | Label for the first implementation |
| labelB | string | — | Label for the second implementation |
No output schema declared.
No examples provided.
big_o_estimate ~122
Estimate Big O complexity from empirical data. Provide input sizes and corresponding execution times to get the best-fit complexity class (O(1), O(log n), O(n), O(n log n), O(n^2), O(n^3), O(2^n)) with confidence scores and growth curve.
| Name | Type | Req | Description |
|---|---|---|---|
| executionTimesMs | array | yes | Array of execution times in milliseconds, corresponding to each input size |
| inputSizes | array | yes | Array of input sizes (e.g., [100, 500, 1000, 5000]) |
No output schema declared.
No examples provided.
bundle_analyze ~52
Analyze a JavaScript bundle file: raw size, gzip estimate, detected modules, largest modules, and tree-shaking opportunities.
| Name | Type | Req | Description |
|---|---|---|---|
| filePath | string | yes | Absolute path to the JavaScript bundle file to analyze |
No output schema declared.
No examples provided.
load_test ~131
Run a simple HTTP load test: send N concurrent requests to a URL, measure response times, error rate, throughput (req/sec), and percentile latencies.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | — | Optional request body |
| concurrency | integer | — | Number of concurrent requests |
| headers | object | — | Optional HTTP headers as key-value pairs |
| method | string | — | HTTP method (GET, POST, PUT, DELETE, etc.) |
| timeoutMs | integer | — | Request timeout in milliseconds |
| totalRequests | integer | — | Total number of requests to send |
| url | string | yes | Target URL to test |
No output schema declared.
No examples provided.
memory_analyze ~67
Analyze Node.js memory usage: heap used/total, RSS, external, array buffers. Tracks snapshots over time and detects potential memory leaks via growth trend analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | snapshot: take a single reading; analyze: full analysis with trend detection; clear: reset history |
No output schema declared.
No examples provided.