mcpField
F
FARPY

FARPY

VerifiedFeaturedRemote
farpy.comDeveloper Tools1Updated 8w ago

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

  1. 01Asynchronous Blender Cycles rendering
  2. 02Submit .blend workloads
  3. 03Download completed artifacts
  4. 04SHA-256 artifact verification
  5. 05Execution receipts and public proofs

Use cases

  1. 01Render Blender Cycles frames on GPUs
  2. 02Track jobs and retrieve finished outputs
  3. 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.

Endpointhttps://api.farpy.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

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 README

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: LIVE_PUBLIC_ALPHA

Additional workloads are under development and are not currently public.

Agent / API access

Typical lifecycle:

discover → price → submit → JOB-ID → execute → download → verify receipt

Agent discovery

Public surfaces

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 API farpy_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

Markdown supported

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.