Other · Local MCP server
Perf MCP
Fact-check and fix AI outputs. Hallucination detection, schema validation, auto-repair.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Perf-AI/perf-mcp- Version
- 0.1.1
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-19
- Updated
- 2026-02-19
- Publisher
- Perf-AI (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Perf-AI) · how
- Repository
- github.com/Perf-Technology/perf-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | perf-mcp | 0.1.1 | stdio |
How to connect Perf MCP
Perf MCP runs locally from a Node.js package published to the npm registry: perf-mcp version 0.1.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y perf-mcp@0.1.1. It reads the environment variable PERF_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"perf-mcp": {
"command": "npx",
"args": [
"-y",
"perf-mcp@0.1.1"
],
"env": {
"PERF_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| pepitaRead, edit, publish, and preview your pepita websites from Claude. | Remote · HTTPLive check: sign-in required |
| Pequod MCPComplete US ETF holdings from SEC N-PORT filings + ticker/CUSIP/FIGI crosswalk. Primary source. | Local · stdio |
| PercherMCP-native hosting: publish and operate AI-built web apps live at name.percher.run. | Remote & Local · HTTP, stdioLive check: sign-in required |
| PerfBenchmark, memory, Big O analysis for AI agents. | Local · stdio |
| Perfonext Build MCPMCP server for Next.js build stats, chunk attribution, and bundle optimization advice. | Local · stdio |
| Perfonext Profiler MCPMCP server for analyzing V8/Chrome CPU profiles with line-level tick attribution. | Local · stdio |
| Perfonext Render MCPMCP server for analyzing React Profiler exports: rerenders, commit spikes, slow components. | Local · stdio |
| Perforce P4 MCP ServerPerforce P4 MCP server for version control and P4 DAM digital asset management. | Local · stdio |