Back to Browse

Farpy Public MCP Server

Developer ToolsModerate5.2MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

FARPY routes GPU workloads to qualified compute and returns verified artifacts and receipts.

About

FARPY routes GPU workloads to qualified compute and returns verified artifacts and receipts.

Remote endpoints: streamable-http: https://api.farpy.com/mcp

Security Report

5.2
Moderate5.2Moderate Risk

FARPY is a Next.js web frontend for a distributed GPU compute platform. The codebase is clean, well-structured, and contains no authentication vulnerabilities, malicious patterns, or dangerous code execution risks. Permissions are appropriate for a web application (network_http for API calls, env_vars for configuration). Minor code quality findings do not materially affect security. Supply chain analysis found 12 known vulnerabilities in dependencies (0 critical, 5 high severity).

7 files analyzed · 16 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub 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.

Reviews

No reviews yet

Be the first to review this server!