io.github.Mangomunchr/farpy
REMOTE · API.FARPY.COM · SCANNED AUG 22
Verified GPU compute for Blender rendering with signed receipts and proof.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 521, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.Mangomunchr/farpy MCP server?
io.github.Mangomunchr/farpy is a hosted endpoint at https://api.farpy.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.farpy.com
claude mcp add --transport http mangomunchr-farpy 'https://api.farpy.com/mcp'
{
"mcpServers": {
"mangomunchr-farpy": {
"url": "https://api.farpy.com/mcp"
}
}
} {
"servers": {
"mangomunchr-farpy": {
"type": "http",
"url": "https://api.farpy.com/mcp"
}
}
} [mcp_servers.mangomunchr-farpy] url = "https://api.farpy.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mangomunchr-farpy": {
"type": "remote",
"url": "https://api.farpy.com/mcp",
"enabled": true
}
}
} openclaw mcp add mangomunchr-farpy --url 'https://api.farpy.com/mcp' --transport streamable-http
mcp_servers:
mangomunchr-farpy:
url: "https://api.farpy.com/mcp" {
"McpServers": {
"mangomunchr-farpy": {
"Transport": "http",
"Url": "https://api.farpy.com/mcp"
}
}
} assistant mcp add mangomunchr-farpy -t streamable-http -u 'https://api.farpy.com/mcp'
{
"mcpServers": {
"mangomunchr-farpy": {
"type": "http",
"url": "https://api.farpy.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Aug 26 −5
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- Transport: Transport check failed: declared sse, but the endpoint returned HTTP 404. security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- 20 Aug 26 0
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared sse, but we couldn't connect to verify it. security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- 13 Aug 26 23
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Aug 2026 · Probed https://api.farpy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=farpy.com | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 30e189c6590d50ca13630926b0b7f4c4 |
| SANs: farpy.com, *.farpy.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.farpy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| farpy.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://api.farpy.com/mcp | HTTP error | 404 | |
| http (plaintext) | http://api.farpy.com/mcp | Inconclusive | 521 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
No tool schema has been captured from this endpoint yet.
What is the io.github.Mangomunchr/farpy MCP server?
io.github.Mangomunchr/farpy is an MCP server listed in the public MCP registry as io.github.Mangomunchr/farpy. Verified GPU compute for Blender rendering with signed receipts and proof. This page covers its hosted endpoint (https://api.farpy.com/mcp).
Is the io.github.Mangomunchr/farpy MCP server safe to use?
io.github.Mangomunchr/farpy scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the io.github.Mangomunchr/farpy MCP server require authentication?
No. We connected to io.github.Mangomunchr/farpy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Mangomunchr/farpy MCP server still maintained?
io.github.Mangomunchr/farpy is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.