io.github.rog0x/perf
NPM · @ROG0X/MCP-PERF-TOOLS
Benchmark, memory, Big O analysis for AI agents
Available components
Last scanned (10 hours ago)
Scores higher than 80% of npm 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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. 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 228 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 6 Nov 2026 · Analysed npm/@rog0x/mcp-perf-tools@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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.
How do I install the io.github.rog0x/perf MCP server?
io.github.rog0x/perf runs locally as an npm package, launched with npx -y @rog0x/mcp-perf-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @rog0x/mcp-perf-tools
claude mcp add rog0x-perf -- npx -y @rog0x/mcp-perf-tools
What is the io.github.rog0x/perf MCP server?
io.github.rog0x/perf is an MCP server listed in the public MCP registry as io.github.rog0x/perf. Benchmark, memory, Big O analysis for AI agents. This page covers its npm package (@rog0x/mcp-perf-tools).
Is the io.github.rog0x/perf MCP server safe to use?
io.github.rog0x/perf scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. 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 io.github.rog0x/perf MCP server expose?
io.github.rog0x/perf exposes 5 tools: benchmark, memory_analyze, big_o_estimate, bundle_analyze, load_test. Their descriptions and schemas cost roughly 475 tokens of context every time the server is loaded.
Is the io.github.rog0x/perf MCP server still maintained?
io.github.rog0x/perf is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.rog0x/perf MCP server under?
io.github.rog0x/perf declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.rog0x/perf MCP server?
VerifyMCP ran 16 checks on io.github.rog0x/perf, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.