About FARPY
FARPY is a public-alpha GPU compute service for people, applications, and agents, currently offering asynchronous Blender Cycles GPU rendering. It returns downloadable outputs with SHA-256 verification and execution receipts.
Key features
- 01Asynchronous Blender Cycles rendering
- 02Submit .blend workloads
- 03Download completed artifacts
- 04SHA-256 artifact verification
- 05Execution receipts and public proofs
Use cases
- 01Render Blender Cycles frames on GPUs
- 02Track jobs and retrieve finished outputs
- 03Verify artifact integrity and execution
MCP support
FARPY offers a remote MCP endpoint and a local stdio MCP server for MCP clients. Its tools inspect and quote jobs, start execution, check status, download outputs, and retrieve receipts.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.farpy.com/mcpclaude mcp add --transport http farpy https://api.farpy.com/mcp{"mcpServers":{"farpy":{"type":"http","url":"https://api.farpy.com/mcp"}}}Open in Cursor{"servers":{"farpy":{"type":"http","url":"https://api.farpy.com/mcp"}}}Open in VS Code{"mcpServers":{"farpy":{"type":"http","url":"https://api.farpy.com/mcp"}}}{"mcpServers":{"farpy":{"serverUrl":"https://api.farpy.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEFARPY
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:
LIVE_PUBLIC_ALPHA
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 FARPY_AGENT_TOKEN.
Build and run
cd mcp
npm install
npm run build
npm test
node dist/mcp-server.js
Environment (see .env.example):
FARPY_AGENT_TOKEN— Job APIfarpy_agent_key. Required for every tool. The server fails closed if it is missing.FARPY_API_BASE— 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 legal_acceptance=FARPY_LEGAL_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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.