Farpy MCP server
online · 100% uptimeio.github.Mangomunchr/farpy·v1.1.0·1 starsFARPY routes GPU workloads to qualified compute and returns verified artifacts and receipts.
1 stars
Reviews
Write oneNobody has reviewed Farpy yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Farpy tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 792ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 43 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Farpy compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 223 ms
- faster than 60% of 30,031 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Install Farpy in Claude Code, Cursor or VS Code
claude mcp add --transport http farpy https://api.farpy.com/mcp
What the publisher says
From the Farpy repository's README, as published. We do not edit it. Read it on GitHub
FARPY
Verified GPU compute for humans, applications, and agents.
FARPY accepts bounded GPU workloads, executes them asynchronously, delivers completed artifacts, and issues verifiable execution receipts.
Public workload
Blender Cycles GPU rendering — $0.01 per completed frame.
Current public contract:
- Workload: Blender Cycles GPU
- Input: .blend
- Execution: asynchronous
- Output: downloadable artifact
- Integrity: SHA-256 artifact verification
- Evidence: FARPY execution receipt
- Transparency: public proof surfaces
- Status: LIVEPUBLICALPHA
Additional workloads are under development and are not currently public.
Agent / API access
- MCP: https://api.farpy.com/mcp
- API: https://api.farpy.com/v1
- OpenAPI 3.1: https://farpy.com/openapi.json
- Quickstart: https://farpy.com/api/quickstart/
- Capabilities: https://api.farpy.com/v1/capabilities
- Pricing: https://api.farpy.com/v1/pricing
- Limits: https://api.farpy.com/v1/limits
Typical lifecycle:
discover → price → submit → JOB-ID → execute → download → verify receipt
Agent discovery
- Official MCP Registry: https://registry.modelcontextprotocol.io/
- Smithery: https://smithery.ai/servers/mangomunchr/farpy
- Glama: https://glama.ai/mcp/servers/Mangomunchr/farpy-public
- PulseMCP: https://www.pulsemcp.com/servers
- Agent manifest: https://farpy.com/agents.json
- LLM context: https://farpy.com/llms.txt
Public surfaces
- Website: https://farpy.com
- Proof: https://farpy.com/proof/
- BenchMork: https://farpy.com/benchmark
- Research: https://farpy.com/labs/research
- Security: SECURITY.md
Local MCP / Glama
A local stdio MCP server for Cursor, Claude Desktop, Glama, and other MCP clients lives in mcp/.
It is a thin public client over FARPY's existing Job API. It does not include production server code and never logs FARPYAGENTTOKEN.
Build and run
cd mcp
npm install
npm run build
npm test
node dist/mcp-server.jsEnvironment (see .env.example):
- FARPYAGENTTOKEN — Job API farpyagent key. Required for every tool. The server fails closed if it is missing.
- FARPYAPIBASE — API origin. Default: https://api.farpy.com
Example local client config:
{
"mcpServers": {
"farpy": {
"command": "node",
"args": ["/absolute/path/to/farpy-public/mcp/dist/mcp-server.js"],
"env": {
"FARPY_AGENT_TOKEN": "farpy_agent_..."
}
}
}
}Public MCP V1 tools: inspect, quote, start, status, download, receipt. inspect and quote do not spend. start is the spend boundary and requires legalacceptance=FARPYLEGAL_V1.
Scope
FARPY is currently a public-alpha service.
Public capabilities, pricing, and limits are authoritative. Historical research, internal tests, and experimental workloads do not imply current public availability.
Nothing above is checked by us. What we check is on the safety report.
Farpy: common questions
- Is Farpy MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Farpy safety report
- How do I install Farpy?
- It runs remotely at api.farpy.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Farpy need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Farpy maintained?
- The last commit was 62 days ago (2026-09-03). The latest release is v1.1.0.
- Is Farpy up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Farpy compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 223 ms (faster than 60% of 30,031 servers). Full comparison.