High Performance MCP Server
NPM · HIGH-PERFORMANCE-MCP-SERVER · SCANNED SEP 21
High-performance, modular MCP v2 server with safe profiles, worker pool, caching, and stdio.
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 → Why this is hard to score →
Supply Chain Security100
- 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
- 0 of 6 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to AnIayana/high-performance-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 13 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 106 tokens (~53/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the High Performance MCP Server server?
High Performance MCP Server runs locally as an npm package, launched with npx -y high-performance-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · high-performance-mcp-server
claude mcp add aniayana-high-performance-mcp-server -- npx -y high-performance-mcp-server
{
"mcpServers": {
"aniayana-high-performance-mcp-server": {
"command": "npx",
"args": [
"-y",
"high-performance-mcp-server"
]
}
}
} {
"servers": {
"aniayana-high-performance-mcp-server": {
"command": "npx",
"args": [
"-y",
"high-performance-mcp-server"
]
}
}
} codex mcp add aniayana-high-performance-mcp-server -- npx -y high-performance-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aniayana-high-performance-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"high-performance-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add aniayana-high-performance-mcp-server --command npx --arg -y --arg high-performance-mcp-server
mcp_servers:
aniayana-high-performance-mcp-server:
command: "npx"
args: ["-y", "high-performance-mcp-server"] {
"McpServers": {
"aniayana-high-performance-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"high-performance-mcp-server"
]
}
}
} assistant mcp add aniayana-high-performance-mcp-server -t stdio -c npx -a -y high-performance-mcp-server
{
"mcpServers": {
"aniayana-high-performance-mcp-server": {
"command": "npx",
"args": [
"-y",
"high-performance-mcp-server"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 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.
- 8 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 7 Sept 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.17 ▲ functional
- Package version: 0.4.0 → 0.5.0 functional
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 21 Sept 2026 · Analysed npm/high-performance-mcp-server@0.5.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | AnIayana/high-performance-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/AnIayana/high-performance-mcp-server/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2749777654 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a934a575bb8896a5103064771738b0c5999f443ae23cd0b77c5faf6b4cb913b4d2849f6765f3d54a95a3e642c3ff955dc60d70739e0256c83d7c93a53 |
Background: How many MCP packages publish verified provenance →
Dependencies 6 packages
| Packages resolved | 6 |
|---|---|
| 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 →
echo Echo Tool ~26
Echoes back the provided message
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The message to echo back |
No output schema declared.
No examples provided.
ping Ping ~15
Checks whether the MCP server is responsive
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the High Performance MCP Server server?
High Performance MCP Server is listed in the public MCP registry as io.github.AnIayana/high-performance-mcp-server. High-performance, modular MCP v2 server with safe profiles, worker pool, caching, and stdio. This page covers its npm package (high-performance-mcp-server).
Is the High Performance MCP Server server safe to use?
High Performance MCP Server scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 High Performance MCP Server server expose?
High Performance MCP Server exposes 2 tools: echo, ping. Their descriptions and schemas cost roughly 41 tokens of context every time the server is loaded.
Is the High Performance MCP Server server still maintained?
High Performance MCP Server is still listed as active in the MCP registry. We last reached this channel on 21 September 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 High Performance MCP Server server under?
High Performance MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.