mcp-registry/com.fadehost/mcp · v1.0.0
As of 2026-10-22 19:34 UTC, the Fadehost MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.
Manage FadeHost game servers, Discord bots and VPS: console, stats, backups, logs, lifecycle.
Claude Code
claude mcp add --transport http fadehost-mcp-server https://api.fadehost.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"fadehost-mcp-server": {
"type": "http",
"url": "https://api.fadehost.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
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 →
1 of 38 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 →
In the last 30 days: 0 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.fadehost%2Fmcp/fixes
{
"name": "create_app",
"description": "Deploy a Discord bot or a web app from a public or private GitHub/GitLab repository. The language is detected from the repo (Node.js, Python, Bun, Deno, Go, Java, PHP, Ruby, Rust, C# on .NET, or a static site); the app is cloned, built and started, and every push to the branch redeploys it. A Discord bot needs DISCORD_TOKEN in env. With web_address (a name), the app also gets https://<name>.fadehost.app pointing at the port it listens on (the PORT variable, 8080 by default); every app has one wi",
"inputSchema": {
"type": "object",
"required": [
"name",
"repo_url"
],
"properties": {
"env": {
"type": "object",
"description": "Environment variables as a map of NAME to value (DISCORD_TOKEN for bots, API keys, ...)."
},
"kind": {
"enum": [
"discord",
"telegram",
"whatsapp",
"web",
"static",
"worker",
"app"
],
"type": "string",
"description": "\"discord\" for a Discord bot (needs DISCORD_TOKEN), \"telegram\" or \"whatsapp\" for those bots, \"web\" for a web app or API, \"static\" for a static site, \"worker\" for anything else that keeps running. Default discord."
},
"name": {
"type": "string",
"description": "A name for the app (3 to 60 characters)."
},
"port": {
"type": "integer",
"description": "The port the app listens on for its web address; default 8080 (the PORT variable)."
},
"tier": {
"enum": [
"free",
"starter",
"standard",
"pro"
],
"type": "string",
"description": "free (default when the account still has its free app), starter, standard or pro."
},
"branch": {
"type": "string",
"description": "Branch to deploy; default is the repository default branch."
},
"region": {
"type": "string",
"description": "Part of a region name, e.g. \"Europe\" or \"USA\". Default Europe."
},
"runtime": {
"enum": [
"node",
"python",
"bun",
"deno",
"go",
"java",
"php",
"ruby",
"rust",
"dotnet",
"static"
],
"type": "string",
"description": "The language to run the repository as; leave empty to detect it from the files in the repo."
},
"repo_url": {
"type": "string",
"description": "The repository, e.g. https://github.com/owner/repo."
},
"git_token": {
"type": "string",
"description": "A token for a private repository (a GitHub fine-grained token or the GitHub App connection is preferred)."
},
"build_mode": {
"enum": [
"runtime",
"dockerfile",
"railpack"
],
"type": "string",
"description": "\"runtime\" (default) installs and starts the repository in a shared runtime. \"dockerfile\" builds the repository's own Dockerfile into an image first. \"railpack\" works out how to build a repository that has no Dockerfile. Both build modes are paid tiers only."
},
"web_address": {
"type": "string",
"description": "A name for a public web address, e.g. \"my-dashboard\" for https://my-dashboard.fadehost.app. Included with every app."
},
"build_command": {
"type": "string",
"description": "A build step to run after install (e.g. \"npm run build\")."
},
"start_command": {
"type": "string",
"description": "Override the start command (e.g. \"node dist/index.js\")."
}
}
},
"annotations": {
"openWorldHint": true,
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create App"
}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/com.fadehost/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.fadehost/mcp"}) over MCP.
create_app ~800 tokenscreate_server ~555 tokensset_app_firewall ~411 tokenscreate_app_schedule ~302 tokensset_app_variables ~299 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%2Fcom.fadehost%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.fadehost%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fadehost%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.fadehost%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.fadehost%2Fmcp?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:16f0670b531fb718…, first seen 2026-10-19, included at leaf 28885 of 47,723. Version history · verify what your client received.
Compare: most reliable devops servers · most reliable security servers · most reliable analytics servers · most reliable other servers · most reliable data 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-22 19:34 UTC, the Fadehost MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 9 outages in 90 days, with a median recovery of 7 minutes.
Fadehost MCP server advertises 38 tools, including create_app, create_app_schedule, create_backup, create_server, delete_app_schedule.
Point your MCP client at this streamable-http endpoint: https://api.fadehost.com/mcp
Glimind scanned all 38 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.