Kinsta MCP by usefulapi
REMOTE · KINSTA.USEFULAPI.IO
Read Kinsta sites, environments, backups, logs and analytics; clear caches, restart PHP, back up.
Available components
Last scanned (4 hours ago)
Scores higher than 47% 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 Usability85
- 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
- Context-footprint check failed: tool/resource definitions use about 2521 tokens (~109/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 61
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://kinsta.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 kinsta.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://kinsta.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://kinsta.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://kinsta.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://kinsta.usefulapi.io/mcp |
| Authorisation server | https://kinsta.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://kinsta.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/kinsta/ |
| http (plaintext) | http://kinsta.usefulapi.io/mcp | Inconclusive | 302 | http://kinsta.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 →
kinsta_clear_cdn_cache Clear CDN cache ~132
WRITE: clear the CDN cache of one environment (nothing is lost; files are fetched from the origin again). Needs the environment's cdn_cache_id from kinsta_list_sites. Returns an operation_id. POST /sites/cdn/clear-cache.
| Name | Type | Req | Description |
|---|---|---|---|
| cdn_cache_id | string | yes | The environment's cdn_cache_id (from kinsta_list_sites / kinsta_list_site_environments). |
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_clear_edge_cache Clear edge cache ~140
WRITE: clear Kinsta's edge cache for one environment, optionally only for one URL (and its subdirectories). Nothing is lost; pages are cached again on the next visits. Returns an operation_id. POST /sites/edge-caching/clear.
| Name | Type | Req | Description |
|---|---|---|---|
| clear_subdirectories | boolean | – | With url: also clear the pages below it (default false). |
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
| url | string | – | Only clear this URL (leave empty to clear the whole environment). |
No output schema declared.
No examples provided.
kinsta_clear_site_cache Clear site cache ~96
WRITE: clear the page cache of one environment (the site is briefly slower while the cache warms up; nothing is lost). Returns an operation_id: check it with kinsta_get_operation_status. POST /sites/tools/clear-cache.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_create_manual_backup Create manual backup ~126
WRITE: start a manual backup of one environment, with an optional note. Kinsta limits the number of manual backups per environment; when the limit is reached the request fails and nothing is deleted. Returns an operation_id. POST /sites/environments/{env_id}/manual-backups.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
| tag | string | – | A short note for the backup (shown in MyKinsta). |
No output schema declared.
No examples provided.
kinsta_get_analytics Get environment analytics ~245
Traffic and resource analytics for one environment: visits, bandwidth, CDN bandwidth, disk space, response codes, visit dispersion, or the top countries, cities, browsers, hosts, referrers, user agents or ASNs. Choose a time_span or a from/to date range (yyyy-mm-dd). The company id is filled in automatically. GET /sites/environments/{env_id}/analytics/{metric}.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
| from | string | – | Range start, yyyy-mm-dd (use with to). |
| metric | string | yes | Which analytics report. |
| time_span | string | – | Period to report on: 24_hours, 7_days, 30_days or 60_days (default 7_days; disk space has no 24_hours). |
| time_zone | string | – | Only for metric diskspace: hour offset from UTC such as 02:00 or -05:00 (default 00:00). |
| to | string | – | Range end, yyyy-mm-dd. |
No output schema declared.
No examples provided.
kinsta_get_api_key_info Get API key info ~49
Details of the Kinsta API key in use: its name, status, expiry and the company id it belongs to. The key itself is never shown. GET /validate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kinsta_get_force_https_status Get force-HTTPS status ~84
Whether the environment forces HTTPS (ENABLED_FOR_ALL, ENABLED_REDIRECT_TO_PRIMARY or DISABLED). GET /sites/environments/{env_id}/force-https-status.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_get_logs Get environment logs ~210
Recent lines of an environment's error log, access log or Kinsta cache performance log, optionally within a time range and filtered by a search text. Returns the log as text (the newest lines the API gives). Access logs contain visitor IP addresses. GET /sites/environments/{env_id}/logs.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
| file_name | string | – | Which log (default error). |
| from | string | – | Only lines at or after this ISO 8601 date-time, e.g. 2026-10-01T00:00:00Z. |
| lines | integer | – | Number of lines, 1-2000 (default 200). |
| search | string | – | Only lines containing this text. |
| to | string | – | Only lines at or before this ISO 8601 date-time. |
No output schema declared.
No examples provided.
kinsta_get_operation_status Get operation status ~90
The status of an asynchronous operation (cache clear, PHP restart, manual backup, ...) by the operation_id the write tool returned. status 200 = finished, 202 = still running, other = failed. GET /operations/{operation_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | Operation id, e.g. sites:clear-cache-<uuid> (from the write tool's reply). |
No output schema declared.
No examples provided.
kinsta_get_site Get site ~52
One site by id, with its status and environments. GET /sites/{site_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Kinsta site id (a UUID; from kinsta_list_sites). |
No output schema declared.
No examples provided.
kinsta_get_site_usage Get site usage this month ~75
A site's usage for the current billing month: visits, bandwidth or CDN bandwidth. GET /sites/{site_id}/usage/{metric}/this-month.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | Which usage figure. |
| site_id | string | yes | Kinsta site id (a UUID; from kinsta_list_sites). |
No output schema declared.
No examples provided.
kinsta_list_activity_logs List activity logs ~140
The company's activity log (who did what: site actions, DNS, migrations, billing, notifications, user management), newest first, with type, status, time, initiator and a description. Page with limit and offset (the reply's total tells how many exist). GET /company/{id}/activity-logs.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only this category. |
| limit | integer | – | Entries to return, 1-100 (default 10). |
| offset | integer | – | Entries to skip (default 0). Use offset + limit to page. |
| site_id | string | – | Only entries for this site id. |
No output schema declared.
No examples provided.
kinsta_list_available_regions List data center regions ~39
The data center regions (name and region code) the company can host sites in. GET /company/{id}/available-regions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kinsta_list_backups List backups ~96
The backups of one environment (manual, scheduled and system): id, name, note, type and creation time (epoch ms). Backups cannot be restored or deleted from here. GET /sites/environments/{env_id}/backups.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_list_company_domains List company domains ~32
All domains the company has in Kinsta DNS / hosting, across sites. GET /domains.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kinsta_list_denied_ips List denied IPs ~69
The IP addresses and ranges blocked from the environment. GET /sites/tools/denied-ips.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_list_environment_domains List environment domains ~81
The domains attached to one environment (id, name, whether Kinsta DNS/Cloudflare is used). GET /sites/environments/{env_id}/domains.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_list_plugins List WordPress plugins ~90
The plugins of one environment: name, title, status (active/inactive), version, available update version, vulnerability flags and the auto-update type. GET /sites/environments/{env_id}/wp-plugins.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_list_redirect_rules List redirect rules ~129
The environment's redirect rules (from, to, type, domain, optional country/city targeting), paged. GET /sites/environments/{env_id}/redirect-rules.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
| limit | integer | – | Rules to return, 1-100 (default 10). |
| offset | integer | – | Rules to skip (default 0). |
| search | string | – | Only rules matching this text. |
No output schema declared.
No examples provided.
kinsta_list_site_environments List site environments ~79
The environments (live, staging, ...) of one site: id, name, PHP engine version, WordPress version, primary domain, edge cache and CDN ids. GET /sites/{site_id}/environments.
| Name | Type | Req | Description |
|---|---|---|---|
| site_id | string | yes | Kinsta site id (a UUID; from kinsta_list_sites). |
No output schema declared.
No examples provided.
kinsta_list_sites List sites ~86
List the company's WordPress sites (id, name, display name, status, labels). With include_environments the live/staging environment ids, primary domain, PHP version, WordPress version and SSH host/port come too: use those environment ids for the other tools. GET /sites.
| Name | Type | Req | Description |
|---|---|---|---|
| include_environments | boolean | – | Include each site's environments (default true). |
No output schema declared.
No examples provided.
kinsta_list_themes List WordPress themes ~82
The themes of one environment: name, title, status, version, available update version and vulnerability flags. GET /sites/environments/{env_id}/wp-themes.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
kinsta_restart_php Restart PHP engine ~86
WRITE: restart the PHP engine of one environment. Requests in flight fail and the site may be unavailable for a few seconds. Returns an operation_id. POST /sites/tools/restart-php.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_id | string | yes | Kinsta environment id (a UUID; from kinsta_list_sites with include_environments, or kinsta_list_site_environments). |
No output schema declared.
No examples provided.
How do I install the Kinsta MCP by usefulapi server?
Kinsta MCP by usefulapi is a hosted endpoint at https://kinsta.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 · kinsta.usefulapi.io
claude mcp add --transport http io-usefulapi-kinsta 'https://kinsta.usefulapi.io/mcp'
What is the Kinsta MCP by usefulapi server?
Kinsta MCP by usefulapi is listed in the public MCP registry as io.usefulapi/kinsta. Read Kinsta sites, environments, backups, logs and analytics; clear caches, restart PHP, back up. This page covers its hosted endpoint (https://kinsta.usefulapi.io/mcp).
Is the Kinsta MCP by usefulapi server safe to use?
Kinsta MCP by usefulapi scores 65 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 Kinsta MCP by usefulapi server expose?
Kinsta MCP by usefulapi exposes 23 tools: kinsta_get_api_key_info, kinsta_list_available_regions, kinsta_list_activity_logs, kinsta_list_sites, kinsta_get_site, and 18 more. Their descriptions and schemas cost roughly 2,308 tokens of context every time the server is loaded.
Does the Kinsta MCP by usefulapi server require authentication?
Yes. Kinsta 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 Kinsta MCP by usefulapi server still maintained?
Kinsta 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.