SpinupWP MCP by usefulapi
REMOTE · SPINUPWP.USEFULAPI.IO
Read SpinupWP servers, sites and events; purge caches, restart services, run git deploys.
Available components
Last scanned (13 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Cloud Infrastructure
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 → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1813 tokens (~95/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.0.0 → 1.1.0 functional
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 62
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 17 Oct 2026 · Probed https://spinupwp.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spinupwp.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://spinupwp.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://spinupwp.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://spinupwp.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://spinupwp.usefulapi.io/mcp |
| Authorisation server | https://spinupwp.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spinupwp.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/spinupwp/ |
| http (plaintext) | http://spinupwp.usefulapi.io/mcp | Inconclusive | 302 | http://spinupwp.usefulapi.io/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
spinupwp_correct_file_permissions Correct file permissions ~81
WRITE: reset a site's files and folders to the permissions and ownership SpinupWP recommends (usually after a manual upload as the wrong user). Can take a while on big sites. Asynchronous: returns an event_id. POST /sites/{id}/file-permissions/correct.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | yes | SpinupWP site id. |
No output schema declared.
No examples provided.
spinupwp_deploy_site_git Run site git deploy ~94
WRITE: pull the latest commit of the site's connected git branch and run its deploy script on the server. This changes the live site's files (and may run build/migration commands); it fails if git is not connected. Asynchronous: returns an event_id. POST /sites/{id}/git/deploy.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | yes | SpinupWP site id (a site with git connected). |
No output schema declared.
No examples provided.
spinupwp_get_event Get event ~73
One event by id, with status and command output. Use it to see whether a purge, restart or deploy (which reply with an event_id) has finished or failed. GET /events/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | integer | yes | SpinupWP event id (the event_id a write tool returned). |
No output schema declared.
No examples provided.
spinupwp_get_server Get server ~64
One server by id: provider, size, disk usage, database server, connection status, reboot/upgrade-required flags and install notes. GET /servers/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id (from spinupwp_list_servers). |
No output schema declared.
No examples provided.
spinupwp_get_site Get site ~100
One site by id with its full settings: domains, PHP version, page cache, HTTPS, nginx options, database reference, backup schedule and storage, WordPress update counts, git repo/branch/deploy script, basic-auth username, cron and SpinupWP subdomain. The git deploy-trigger URL is hidden. GET /sites/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | yes | SpinupWP site id (from spinupwp_list_sites). |
No output schema declared.
No examples provided.
spinupwp_list_events List events ~115
List recent events (the activity log: provisioning, restarts, deploys, cache purges) with who started them, status (queued, creating, updating, deleting, deployed, failed) and timestamps. Long command output is shortened; read one event for its full output. GET /events.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
spinupwp_list_servers List servers ~96
List the servers in your SpinupWP team: name, provider, region, size, IP, Ubuntu version, disk space, connection status and whether a reboot or upgrade is required. GET /servers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
spinupwp_list_site_domains List site domains ~95
The additional domains of a site, with their redirect settings (enabled, type, destination). GET /sites/{id}/domains.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| site_id | integer | yes | SpinupWP site id. |
No output schema declared.
No examples provided.
spinupwp_list_site_path_redirects List site path redirects ~99
The path redirects configured on a site (from, to, type permanent/redirect). GET /sites/{id}/path-redirects.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| site_id | integer | yes | SpinupWP site id. |
No output schema declared.
No examples provided.
spinupwp_list_sites List sites ~119
List sites across your servers (or one server): domain, PHP version, WordPress flag, HTTPS, page cache, backups, pending WordPress core/theme/plugin updates, git deploy settings and status. Deploy-trigger URLs are hidden. GET /sites.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| server_id | integer | – | Only sites on this server id. |
No output schema declared.
No examples provided.
spinupwp_list_storage_providers List backup storage providers ~78
The backup storage providers connected to the team (id, service, name). GET /storage-providers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
spinupwp_list_team_ssh_keys List team SSH keys ~87
The team's saved SSH public keys (id, name, fingerprint, public key). Public keys only; read-only. GET /ssh-keys.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-100 (default 25). |
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
No output schema declared.
No examples provided.
spinupwp_purge_object_cache Purge object cache ~70
WRITE: flush the Redis object cache of one site (the site must have object caching). The cache refills on demand. Asynchronous: returns an event_id. POST /sites/{id}/object-cache/purge.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | yes | SpinupWP site id. |
No output schema declared.
No examples provided.
spinupwp_purge_page_cache Purge page cache ~78
WRITE: purge the nginx page cache of one site. Pages are rebuilt on the next visit, so the site may be slower for a moment; nothing is lost. Asynchronous: returns an event_id. POST /sites/{id}/page-cache/purge.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | integer | yes | SpinupWP site id. |
No output schema declared.
No examples provided.
spinupwp_reboot_server Reboot server ~77
WRITE: reboot a whole server. Every site on it is offline for the duration (typically a minute or two). Use it when spinupwp_get_server shows reboot_required. Asynchronous: returns an event_id. POST /servers/{id}/reboot.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id. |
No output schema declared.
No examples provided.
spinupwp_restart_mysql Restart mysql ~73
WRITE: restart MySQL (database) on one server. All sites on the server lose database access for a short time; running queries are interrupted. Asynchronous: returns an event_id. POST /servers/{id}/services/mysql/restart.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id. |
No output schema declared.
No examples provided.
spinupwp_restart_nginx Restart nginx ~64
WRITE: restart nginx (web server) on one server. Visitors may see a brief interruption. Asynchronous: returns an event_id. POST /servers/{id}/services/nginx/restart.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id. |
No output schema declared.
No examples provided.
spinupwp_restart_php Restart php ~72
WRITE: restart PHP-FPM (every PHP version) on one server. Running PHP requests can fail or be cut off while it restarts. Asynchronous: returns an event_id. POST /servers/{id}/services/php/restart.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id. |
No output schema declared.
No examples provided.
spinupwp_restart_redis Restart redis ~66
WRITE: restart Redis (object cache) on one server. Cached objects are lost and rebuilt on demand. Asynchronous: returns an event_id. POST /servers/{id}/services/redis/restart.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | integer | yes | SpinupWP server id. |
No output schema declared.
No examples provided.
How do I install the SpinupWP MCP by usefulapi server?
SpinupWP MCP by usefulapi is a hosted endpoint at https://spinupwp.usefulapi.io/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 · spinupwp.usefulapi.io
claude mcp add --transport http io-usefulapi-spinupwp 'https://spinupwp.usefulapi.io/mcp'
What is the SpinupWP MCP by usefulapi server?
SpinupWP MCP by usefulapi is listed in the public MCP registry as io.usefulapi/spinupwp. Read SpinupWP servers, sites and events; purge caches, restart services, run git deploys. This page covers its hosted endpoint (https://spinupwp.usefulapi.io/mcp).
Is the SpinupWP MCP by usefulapi server safe to use?
SpinupWP MCP by usefulapi scores 66 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.
What tools does the SpinupWP MCP by usefulapi server expose?
SpinupWP MCP by usefulapi exposes 19 tools: spinupwp_list_servers, spinupwp_get_server, spinupwp_list_sites, spinupwp_get_site, spinupwp_list_site_domains, and 14 more. Their descriptions and schemas cost roughly 1,601 tokens of context every time the server is loaded.
Does the SpinupWP MCP by usefulapi server require authentication?
Yes. SpinupWP MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SpinupWP MCP by usefulapi server still maintained?
SpinupWP MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.