mcp-registry/io.github.mangomunchr/farpy · v0.3.0
Also listed as glama/mangomunchr/farpy
As of 2026-10-26 17:26 UTC, the Mangomunchr Farpy MCP server is up (it requires sign-in) with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 96.3% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 109.1 hours.
FARPY routes GPU workloads to qualified compute and returns verified artifacts and receipts.
Point your MCP client at this streamable-http endpoint: https://api.farpy.com/mcp
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Reachable 96.3% of the time over the last 30 days; median recovery 6545 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mangomunchr%2Ffarpy/fixes
{
"name": "farpy_download",
"description": "Return a short-lived authenticated FARPY artifact download URL.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": "string",
"description": "FARPY job id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "farpy_job_status",
"description": "Return one FARPY render job or recent render history.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"job_id": {
"type": "string",
"description": "Optional FARPY job id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "farpy_prepare_upload",
"description": "Create a short-lived one-time upload URL for a local Blender .blend file. Upload the file bytes directly with HTTP PUT; do not send file bytes through model context.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"filename"
],
"properties": {
"filename": {
"type": "string",
"description": "Filename only, ending in .blend"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mangomunchr/farpy"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mangomunchr/farpy"}) over MCP.
farpy_submit_render ~141 tokensfarpy_prepare_upload ~115 tokensfarpy_inspect_blend ~86 tokensfarpy_download ~79 tokensfarpy_job_status ~73 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mangomunchr%2Ffarpy?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mangomunchr%2Ffarpy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangomunchr%2Ffarpy.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangomunchr%2Ffarpy.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mangomunchr%2Ffarpy?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:72dcc22bb5d45f56…, first seen 2026-10-17, included at leaf 13694 of 74,410. Version history · verify what your client received.
Compare: most reliable ml servers · most reliable files servers · most reliable media servers · most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:26 UTC, the Mangomunchr Farpy MCP server is up (it requires sign-in) with a Glimind reliability score of 72/100 (grade C). Over the last 30 days it answered 96.3% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 109.1 hours.
Mangomunchr Farpy MCP server advertises 8 tools, including farpy_capabilities, farpy_download, farpy_inspect_blend, farpy_job_status, farpy_prepare_upload.
Point your MCP client at this streamable-http endpoint: https://api.farpy.com/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.