FARPY
Related Servers
Alternatives to FARPY
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenancePaid remote MCP for rendering hyperframe videos with structured receipts and audit logs. Enables rendering, status checking, artifact fetching, and receipt export.-
- AlicenseAqualityBmaintenanceProvides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.416 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceCross-pool compute auction grid with a 15-agent fleet that bids on compute from io.net, Akash, Render, and more. Verify compute with Groth16 proofs and settle in USDC.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents and shells to quote, start, monitor and fetch cloud GPU renders of saved Blender scenes, returning hash-checked PNG frames and a QA report, with jobs paid for by Loopcut credits.67 PyPI3GPL 3.0
- FlicenseBqualityAmaintenanceEnables agents to run heavy computation—heat-equation solves, matrix exponentials, linear algebra, FFTs, compression, and arbitrary dispatched workloads—on their own machine while routing jobs through an automatic chooser and returning verifiable result digests with CPU-seconds and credit accounting.1977 PyPI-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access decentralized GPU compute over stdio/JSON-RPC, query network status and pricing, estimate job costs, and run verified distributed matrix multiplication, similarity search, and PCA/SVD.Apache 2.0
TDQS
Scored across 6 tools
Most tools are distinct, but inspect and quote both create quote-like objects and both explicitly do not spend, making their boundary fuzzy. Status, download, start, and receipt are clearly separated.
Names are simple, lowercase, and single-word, but they mix imperative verbs (inspect, start, download) with noun-style actions (status, receipt). There is no consistent verb_noun pattern, though the names remain readable.
Six tools is well-scoped for the quote-to-receipt rendering workflow. Each tool represents a meaningful stage in the process without redundant or unnecessary surface area.
The core lifecycle is covered: inspect, quote, start, status, download, and receipt. Minor gaps exist such as no explicit cancel/refund flow and upload is only referenced via upload_id, but agents can work around these for typical jobs.