Other · Remote MCP server
Percher
MCP-native hosting: publish and operate AI-built web apps live at name.percher.run.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.percher/percher- Version
- 1.0.4
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- app.percher
- Namespace
- Namespace verified by the MCP Registry via the domain percher.app · how
- Website
- percher.app/docs/hosted-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.percher.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | @percher/mcp | 1.0.4 | stdio |
How to connect Percher
Percher is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.percher.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @percher/mcp version 1.0.4. 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 @percher/mcp@1.0.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"percher": {
"command": "npx",
"args": [
"-y",
"@percher/mcp@1.0.4"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 |
|---|---|
| PEP Estendida (Parentescos)Checks whether a person is Politically Exposed (PEP) or is related to a PEP, from the CPF. Platform-. | Remote · HTTPLive check: ✓ handshake |
| PepEvolution Peptide SourcesFind where to buy peptides from vetted, COA-tested vendors and check if a peptide vendor is legit. | Remote · HTTPLive check: ✓ handshake |
| 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 |
| PerfBenchmark, memory, Big O analysis for AI agents. | Local · stdio |
| Perf MCPFact-check and fix AI outputs. Hallucination detection, schema validation, auto-repair. | 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 |