MCP servers › io.usefulapi › runcloud
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.usefulapi/runcloud
Read RunCloud servers, web apps, databases and logs; deploy, restart services, renew SSL. — the publisher's description
Summary
io.usefulapi/runcloud is a remote MCP server listed in the official MCP registry at version 1.3.4. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 36 tools, 0 resources and 1 prompt.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 36
- Described as changing data
- 7 of 36 toolsAI-classified
- Mainly works on
- cloud accounts, servers or DevOps tools; files and code on the machine it runs onAI-classified
- Topic
- cloud-and-devopsAI-classified
- Pricing
- freemiumAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 7 tools whose name or declaration suggests they change data (runcloud_control_service, runcloud_deploy_git, runcloud_force_deploy_atomic, runcloud_run_cronjob, runcloud_reload_supervisor and 2 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 7 tools are described as changing something (runcloud_control_service, runcloud_deploy_git, runcloud_force_deploy_atomic, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.3.4, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-11 to 2026-10-22; 3 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.3.4· 2026-10-221.3.3· 2026-10-211.0.0· 2026-10-11
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.3.4 (published 2026-10-22).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: cloud accounts, servers or DevOps tools; files and code on the machine it runs on.
7 of 36 tools are described as changing something (creating, editing, deleting, sending or running).
- runcloud_pingreads or searches
“Check that the API key works: RunCloud answers with a message ('pong').”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
- runcloud_list_serversreads or searches
“List the servers connected to the workspace: id, name, provider, IP address, OS, stack, online/connected state, agent and PHP CLI version, auto-update settings and tags.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_get_serverreads or searches
“One server by id: provider, IP, OS and version, stack, online state, agent version, update settings, tags.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_get_server_statsreads or searches
“How many web applications, databases, cron jobs and supervisor jobs a server has, and its country.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_get_server_hardwarereads or searches
“Kernel version, CPU model and cores, memory and disk totals/free, load average and uptime of a server.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_get_server_healthreads or searches
“The latest health sample of a server: total/available/used memory and disk space (MB) and load average.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_list_server_logsreads or searches
“The server's activity log (what was changed in RunCloud and when), newest first.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_servicesreads or searches
“The services on a server (nginx, php-fpm, mariadb, redis, supervisor...) with real name, running state, CPU, memory and version.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_list_system_usersreads or searches
“The system (Linux) users on a server: id, username, whether deletable.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_webappsreads or searches
“List the web applications on a server: id, name, root/public path, PHP version, stack, type (wordpress, custom...), default flag, alias.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”searchstring“Filter by web application name.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_get_webappreads or searches
“One web application by id (path, PHP version, stack, type, default flag).”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”
- runcloud_get_webapp_settingsreads or searches
“PHP and FPM/Nginx settings of a web application (disabled functions, timezone, memory and upload limits, process manager...).”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”
Show 24 more tools
- runcloud_list_webapp_logsreads or searches
“The activity log of a web application (settings changes, PHP version changes, deployments), newest first.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_domainsreads or searches
“The domain names of a web application: id, name, type (primary/alias), www, redirection, wildcard, DNS integration, status.”
Publisher declares: read-only yes · destructive no · open-world yes
4 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_get_domain_dnsreads or searches
“The DNS records (A, CNAME...) a domain name needs to point at the server.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 3 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”domain_idintegerrequired“Domain name id (see runcloud_list_domains).”
- runcloud_get_webapp_sslreads or searches
“The web application's SSL certificate (basic / web-app-level SSL): provider, validity, HTTPS settings.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”
- runcloud_get_ssl_methodreads or searches
“Whether the web application uses basic (one certificate for the app) or advanced (one per domain) SSL, and its AutoSSL status.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”
- runcloud_get_git_deploymentreads or searches
“The Git deployment configured on a web application: provider, branch, repository URL, auto-deploy flag, deployment script and whether it is an atomic deployment.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”
- runcloud_list_databasesreads or searches
“The databases on a server: id, name, collation.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_database_usersreads or searches
“The database users on a server (id, username).”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_cronjobsreads or searches
“The cron jobs of a server: id, label, user, schedule, command, enabled flag.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_supervisorsreads or searches
“The supervisor (background worker) jobs of a server: id, label, user, process count, auto start/restart, directory, command.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_get_supervisor_statusreads or searches
“The live status (RUNNING, FATAL, BACKOFF...), pid and uptime of every supervisor process, by job label.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_list_firewall_rulesreads or searches
“The firewall rules of a server: type (global/rich), port, protocol, IP address, action.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_blocked_ipsreads or searches
“The IP addresses Fail2Ban currently blocks on a server.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”
- runcloud_list_backupsreads or searches
“The backup instances of the workspace: label, what they cover (web app / database), storage, type, frequency, size, status.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs
server_idinteger“Only backups of this server id.”storagestring“Storage type, e.g.”statusstring“Backup status, e.g.”searchstring“Filter by backup name.”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_backup_snapshotsreads or searches
“The snapshots of one backup instance: run date, status, type and size.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
backup_idintegerrequired“Backup instance id (see runcloud_list_backups).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_atomic_projectsreads or searches
“The atomic Git deployment projects of the workspace: name, provider, repository, branch, auto-deploy, success/failure counts and the latest deployment.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs
pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_list_atomic_deploymentsreads or searches
“The deployments of an atomic project: commit hash, branch, message, committer, release name, status (DEPLOYING, COMPLETED, FAILED), start and end time.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
project_idintegerrequired“Atomic project id (see runcloud_list_atomic_projects).”pageinteger“Page number, from 1 (default 1).”per_pageinteger“Results per page, 1-40 (default 20).”
- runcloud_control_servicedescribed as changing data
“WRITE: run systemctl start, restart or reload on one service of a server (for example nginx-rc or php81rc-fpm).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 3 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”actionstringrequired“systemctl action.”real_namestringrequired“The service's realName from runcloud_list_services, e.g.”
- runcloud_deploy_gitdescribed as changing data
“WRITE: force a Git deployment of a web application now: RunCloud pulls the configured branch and runs the deployment script, which changes the live site's files.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
3 inputs, 3 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”git_idintegerrequired“Git deployment id (runcloud_get_git_deployment -> id).”
- runcloud_force_deploy_atomicdescribed as changing data
“WRITE: start an atomic deployment of a project now (builds a new release and switches the live symlink when it succeeds).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
1 input, 1 required
project_idintegerrequired“Atomic project id (runcloud_list_atomic_projects).”
- runcloud_run_cronjobruns code or commandsdescribed as changing data
“WRITE: force-run one cron job of a server once, right now, outside its schedule.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”cronjob_idintegerrequired“Cron job id (runcloud_list_cronjobs).”
- runcloud_reload_supervisordescribed as changing data
“WRITE: reload one supervisor job so its worker processes restart (running processes are interrupted).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 2 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”supervisor_idintegerrequired“Supervisor job id (runcloud_list_supervisors).”
- runcloud_renew_ssldescribed as changing data
“WRITE: redeploy (renew) the Let's Encrypt certificate of a web application, which re-issues it and reloads the web server.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 3 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”ssl_idintegerrequired“SSL certificate id (runcloud_get_webapp_ssl -> id).”domain_idinteger“Only for advanced (per-domain) SSL mode (see runcloud_get_ssl_method): the domain's id.”
- runcloud_install_letsencrypt_ssldescribed as changing data
“WRITE: issue and install a free Let's Encrypt certificate for a web application (basic SSL) or for one domain of it (advanced SSL, pass domain_id; this requires advanced SSL mode, see runcloud_get_ss…”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
8 inputs, 5 required
server_idintegerrequired“RunCloud server id (see runcloud_list_servers).”webapp_idintegerrequired“Web application id (see runcloud_list_webapps).”domain_idinteger“Only for advanced (per-domain) SSL mode (see runcloud_get_ssl_method): the domain's id.”authorization_methodstringrequired“Let's Encrypt challenge: http-01, or dns-01 (needs external_api, a Cloudflare DNS integration).”external_apiinteger“Id of the Cloudflare DNS integration; required for dns-01.”environmentstring“live (default, trusted certificate) or staging (test certificate).”enable_httpbooleanrequired“Keep plain HTTP enabled alongside HTTPS.”enable_hstsbooleanrequired“Send the HSTS header (browsers will insist on HTTPS).”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 36 tools
- Says what it returns
- 81% of 36 tools
- States limits, defaults or errors
- 43% of 35 tools
- Says when to use it
- 19% of 36 tools
- Items covered per tool
- 2.4 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 92
- Tools with a description
- 100% of 36
- Typical description length
- 176 characters
The tool set
Counted from the listing
- Tools
- 36
- Size of the list
- about 7,820 tokens for an agent to load (characters ÷ 4)
- Naming
- 36 of 36 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 36 of 36 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://runcloud.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"runcloud": {
"url": "https://runcloud.usefulapi.io/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"runcloud": {
"type": "http",
"url": "https://runcloud.usefulapi.io/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"runcloud","type":"http","url":"https://runcloud.usefulapi.io/mcp"}'Claude Code
claude mcp add --transport http runcloud https://runcloud.usefulapi.io/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://runcloud.usefulapi.io/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint runcloud.usefulapi.io/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
| Repository github.com/m190/usefulapi-mcp | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.usefulapi · 341 servers
- GitHub owner
- a personal account (m190)
- Repository
- github.com/m190/usefulapi-mcp
- Stars
- 0
- Repository age
- 91–180 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.usefulapi/runcloud
Answered from the data aboveIs io.usefulapi/runcloud safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 7 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is io.usefulapi/runcloud free to use?
Its website (usefulapi.io/runcloud/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Does io.usefulapi/runcloud need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.usefulapi/runcloud been security tested?
Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
What can io.usefulapi/runcloud do?
It lists 36 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and run code or commands. We did not call any tool, so this describes the text, not the behaviour.
Can io.usefulapi/runcloud change or delete data?
7 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.usefulapi/runcloud publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.usefulapi/runcloud?
In github.com/m190/usefulapi-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.TencentCloudBase/cloudbase-mcpCloudBasealso has tools that runs code or commands, reads or searchescompare with this one
- io.github.Higangssh/homebutleralso has tools that runs code or commands, reads or searchescompare with this one
- io.github.wiresage/mikrotik-mcpalso has tools that runs code or commands, reads or searchescompare with this one
- io.github.hostinger/hostinger-api-mcpalso has tools that runs code or commands, reads or searchescompare with this one
- io.github.Dave-London/dockeralso has tools that runs code or commands, reads or searchescompare with this one
- io.github.Dave-London/pare-dockeralso has tools that runs code or commands, reads or searchescompare with this one
Active servers whose topic is also “cloud-and-devops” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not run · an error was returned
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
3 exercised13 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 259 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 36 tools, 0 resources, 1 prompt.
- 1,086 msFinished: 3 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Free $0 50 tool calls / month”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.usefulapi/runcloud: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.usefulapi/runcloud
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.usefulapi/runcloud)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology