Cuttly MCP by usefulapi
REMOTE · CUTTLY.USEFULAPI.IO
Shorten links with Cuttly, read click stats, and edit, expire, redirect or delete short links.
Available components
Last scanned (5 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Marketing and SEO
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 Usability77
- 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 1387 tokens (~231/item across 6 items; 6 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 59
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://cuttly.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 cuttly.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://cuttly.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://cuttly.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://cuttly.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://cuttly.usefulapi.io/mcp |
| Authorisation server | https://cuttly.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cuttly.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/cuttly/ |
| http (plaintext) | http://cuttly.usefulapi.io/mcp | Inconclusive | 302 | http://cuttly.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 →
cuttly_delete_link Delete link ~127
WRITE, IRREVERSIBLE: permanently delete a short link and its statistics. Anyone who opens the short link afterwards gets an error, and Cuttly cannot restore it. Ask the user to confirm the exact link before you call this. Needs the Single plan or higher. The call is sent once and never retried. GET https://cutt.ly/api/api.php?edit=...&delete=1
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | The Cuttly short link, e.g. https://cutt.ly/abc123 (or a link on your branded domain). |
No output schema declared.
No examples provided.
cuttly_get_link_stats Get link stats ~168
Click statistics of one short link: total clicks, clicks by source (Facebook, Twitter, LinkedIn, other, bots), top referrers, countries, device types, operating systems, browsers, device brands and languages. The date range filter needs the Team plan or higher. Counts as one API call (Free plan 3 per 60 seconds). GET https://cutt.ly/api/api.php?stats=...
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start of the range (Team plan and up). |
| date_to | string | – | End of the range (Team plan and up). May be used alone. |
| link | string | yes | The Cuttly short link, e.g. https://cutt.ly/abc123 (or a link on your branded domain). |
No output schema declared.
No examples provided.
cuttly_set_device_redirect Set device redirect ~190
WRITE: send visitors on one device type to another destination (an app store page or a deep link): Android, iOS or Windows Mobile. platform 'redirect' sets the destination for all other devices. Set `remove: true` instead of a destination to delete the rule. Needs the Single plan or higher. The call is sent once and never retried. GET https://cutt.ly/api/api.php?edit=...&mobile=...
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | – | URL or deep link for that device type. |
| link | string | yes | The Cuttly short link, e.g. https://cutt.ly/abc123 (or a link on your branded domain). |
| platform | string | yes | Device type. 'redirect' = every other device. |
| remove | boolean | – | true = remove the rule of this device type (then do not pass a destination). |
No output schema declared.
No examples provided.
cuttly_set_link_expiration Set link expiration ~219
WRITE: set or remove the expiration of a short link. The link expires after a number of clicks or on a date, and can then redirect to another URL. mode 'none' removes an existing expiration. Needs the Single plan or higher. The call is sent once and never retried. GET https://cutt.ly/api/api.php?edit=...&expire=...
| Name | Type | Req | Description |
|---|---|---|---|
| clicks | integer | – | Click threshold (mode 'clicks'). |
| count_unique_clicks | boolean | – | Count only unique clicks toward a click threshold. |
| date | string | – | Expiration date (mode 'date'). |
| link | string | yes | The Cuttly short link, e.g. https://cutt.ly/abc123 (or a link on your branded domain). |
| mode | string | yes | 'clicks' = expire after `clicks` clicks, 'date' = expire on `date`, 'none' = remove the expiration. |
| redirect_url | string | – | Where visitors go after the link expired. |
No output schema declared.
No examples provided.
cuttly_shorten_link Shorten link ~207
WRITE: create a Cuttly short link for a long URL, optionally with a custom alias (the part after the slash). Returns the short link, the full link and the page title. It counts against the monthly link limit of the plan. Cuttly rate limit: Free 3 calls per 60 seconds, Starter 6, Single 60. The call is sent once and never retried. GET https://cutt.ly/api/api.php?short=...
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | Custom alias (back-half), e.g. 'spring-sale'. Fails if it is taken. |
| public_stats | boolean | – | Make the click statistics of this link readable through the API without the owner's key (Single plan and up). |
| url | string | yes | The long URL to shorten (full http or https URL). |
| use_branded_domain | boolean | – | Use the active branded domain of the account instead of cutt.ly (any paid plan). |
No output schema declared.
No examples provided.
cuttly_update_link Update link ~259
WRITE: change a short link: its alias, destination URL, title, tag or unique-click window. Send only what you want to change. Changing the alias makes the old short link stop working; changing the destination redirects every visitor to the new URL at once. Link editing needs the Single plan or higher. Cuttly sends no previous values back, so ask the user before you change a live link. The call is sent once and never retried. GET https://cutt.ly/api/api.php?edit=...
| Name | Type | Req | Description |
|---|---|---|---|
| destination_url | string | – | New destination URL the short link redirects to. |
| link | string | yes | The Cuttly short link, e.g. https://cutt.ly/abc123 (or a link on your branded domain). |
| new_alias | string | – | New alias. The old short link stops working. Fails if the alias is taken. |
| tag | string | – | A tag to add to the link. |
| title | string | – | New link title. |
| unique_clicks_minutes | integer | – | Unique-click counting: 0 = off, 1 = 15-minute window (Single plan), 15-1440 = custom window in minutes (Team plan and up). |
No output schema declared.
No examples provided.
How do I install the Cuttly MCP by usefulapi server?
Cuttly MCP by usefulapi is a hosted endpoint at https://cuttly.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 · cuttly.usefulapi.io
claude mcp add --transport http io-usefulapi-cuttly 'https://cuttly.usefulapi.io/mcp'
What is the Cuttly MCP by usefulapi server?
Cuttly MCP by usefulapi is listed in the public MCP registry as io.usefulapi/cuttly. Shorten links with Cuttly, read click stats, and edit, expire, redirect or delete short links. This page covers its hosted endpoint (https://cuttly.usefulapi.io/mcp).
Is the Cuttly MCP by usefulapi server safe to use?
Cuttly MCP by usefulapi scores 64 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 Cuttly MCP by usefulapi server expose?
Cuttly MCP by usefulapi exposes 6 tools: cuttly_shorten_link, cuttly_get_link_stats, cuttly_update_link, cuttly_set_link_expiration, cuttly_set_device_redirect, cuttly_delete_link. Their descriptions and schemas cost roughly 1,170 tokens of context every time the server is loaded.
Does the Cuttly MCP by usefulapi server require authentication?
Yes. Cuttly 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 Cuttly MCP by usefulapi server still maintained?
Cuttly 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.