Benchmark JavaScript code execution. Run a snippet N times and measure min/max/avg/p95/p99 time and ops/sec. Optionally compare two implementations.
memory_analyze
Analyze Node.js memory usage: heap used/total, RSS, external, array buffers. Tracks snapshots over time and detects potential memory leaks via growth
big_o_estimate
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
bundle_analyze
Analyze a JavaScript bundle file: raw size, gzip estimate, detected modules, largest modules, and tree-shaking opportunities.
load_test
Run a simple HTTP load test: send N concurrent requests to a URL, measure response times, error rate, throughput (req/sec), and percentile latencies.
Spec / packaging20%100
✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 5 tool(s) detected in source
Security (OWASP MCP)30%70
uses eval/exec/child_process (review for unsanitized input)
scanned 6 source files
Maintenance / popularity20%92
published within 90 days
3 published versions
Tool hygiene15%95
✓ ships TypeScript types
1 runtime deps
Transparency / provenance15%90
✓ public repository linked
✓ MIT license
Findings
INFO Static analysis of npm package @rog0x/mcp-perf-tools@1.0.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:@rog0x/mcp-perf-tools on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://www.wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.