TinyURL MCP by usefulapi
REMOTE · TINYURL.USEFULAPI.IO
Create and manage TinyURL short links: aliases, destinations, tags, archive, click analytics.
Available components
Last scanned (2 hours ago)
Scores higher than 47% 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 Usability79
- 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 1595 tokens (~199/item across 8 items; 8 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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 +3
- 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 60
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://tinyurl.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 tinyurl.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://tinyurl.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://tinyurl.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://tinyurl.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://tinyurl.usefulapi.io/mcp |
| Authorisation server | https://tinyurl.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tinyurl.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/tinyurl/ |
| http (plaintext) | http://tinyurl.usefulapi.io/mcp | Inconclusive | 302 | http://tinyurl.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 →
tinyurl_change_destination Change a short link's destination URL ~117
WRITE: point an existing short link at a new destination. DESTRUCTIVE: everyone who opens the short link is sent to the new URL from now on and the old destination is overwritten. The new URL must be http(s). PATCH /change.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The link's alias. |
| domain | string | – | The short link's domain: tinyurl.com (default) or one of the account's branded domains. |
| url | string | yes | The new destination URL (absolute, http:// or https://). |
No output schema declared.
No examples provided.
tinyurl_count_links Count short links ~116
How many short links the account has (active or archived), optionally within a creation date range or filtered by alias or tag. GET /urls/{type}/count.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only links created after this ISO 8601 date or date-time. |
| search | string | – | Filter: alias:<text> or tag:<text>. |
| to | string | – | Only links created before this ISO 8601 date or date-time. |
| type | string | – | available = active links, archived = archived links. |
No output schema declared.
No examples provided.
tinyurl_create_link Create a short link ~215
WRITE: create ONE new short link for an http(s) destination URL. Optional custom alias (5-30 characters on tinyurl.com), domain (tinyurl.com or a branded domain), tags, expiry and description. Not idempotent: calling it again without an alias creates another link. Returns the new tiny_url. POST /create.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | Custom alias (5-30 characters on tinyurl.com, 1+ on a branded domain). A random one is generated when omitted. |
| description | – | – | Internal description of the link (3-1000 characters). |
| domain | string | – | Domain for the new link: tinyurl.com (default) or one of the account's branded domains. |
| expires_at | – | – | ISO 8601 expiry; omit or null for a link that never expires. |
| tags | array | – | Tags to group the link (each up to 45 characters). |
| url | string | yes | The long destination URL (absolute, http:// or https://). |
No output schema declared.
No examples provided.
tinyurl_get_analytics Get click analytics ~253
Aggregated click analytics for the account, or for one link (alias) or one tag, from a start date. report: timeline (clicks over time; interval minute/hour/day/week/month), general (browsers, operating systems, devices), weekday and hour (popularity), top_sources (referrers), top_languages, location (countries, or the regions of one country via region = ISO 3166 alpha-2 code). Which reports are available depends on the account's TinyURL plan. Visitor-level raw logs are not exposed. GET /analytics/*.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | Only this short link, written domain/alias, e.g. tinyurl.com/myalias. |
| from | string | yes | Start of the report, ISO 8601 date or date-time (required). |
| interval | string | – | Bucket size, timeline report only. |
| region | string | – | location report only: world (default, lists countries) or a country code such as US (lists its regions). |
| report | string | yes | Which analytics report. |
| tag | string | – | Only links with this tag. |
| to | string | – | End of the report (default: now). |
No output schema declared.
No examples provided.
tinyurl_get_link Get a short link ~100
Details of one short link: destination URL, tiny_url, tags, created/expires dates, archived/deleted flags, analytics settings, total hits and owner. GET /alias/{domain}/{alias}.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The alias, the part after the domain: https://tinyurl.com/<alias>. |
| domain | string | – | The short link's domain: tinyurl.com (default) or one of the account's branded domains. |
No output schema declared.
No examples provided.
tinyurl_list_links List short links ~176
List the account's short links (type available = active, archived = archived), optionally created within a date range or filtered by alias or tag. The TinyURL API does not page this list: at most `limit` items (default 50, max 200) are returned together with the total, so narrow with from/to/search when truncated is true. GET /urls/{type}.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Only links created after this ISO 8601 date or date-time. |
| limit | integer | – | Maximum links to return (default 50). |
| search | string | – | Filter: alias:<text> or tag:<text>. |
| to | string | – | Only links created before this ISO 8601 date or date-time. |
| type | string | – | available = active links, archived = archived links. |
No output schema declared.
No examples provided.
tinyurl_set_link_archived Archive or unarchive a short link ~183
WRITE: archive an active short link (archived = true) or restore an archived one (archived = false). Archiving moves the link to the archived list; nothing is deleted and it can be restored. The API's archive endpoint is a toggle, so the link's current state is read first and nothing is changed when it already matches, and the state afterwards is checked. Do not run two archive calls for the same link at once. GET /alias/{domain}/{alias}, then PATCH /archive.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The alias, the part after the domain: https://tinyurl.com/<alias>. |
| archived | boolean | yes | true = archive the link, false = unarchive it. |
| domain | string | – | The short link's domain: tinyurl.com (default) or one of the account's branded domains. |
No output schema declared.
No examples provided.
tinyurl_update_link Update a short link's alias, tags or settings ~228
WRITE: change an existing short link's alias, tags, expiry, description or click-analytics switch. At least one new_* field is required. DESTRUCTIVE for what it replaces: new_tags REPLACES all existing tags, and renaming the alias (new_alias) makes the old short URL stop working. The destination URL is changed with tinyurl_change_destination. PATCH /update.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The link's current alias. |
| domain | string | – | The short link's domain: tinyurl.com (default) or one of the account's branded domains. |
| new_alias | string | – | New alias (5-30 characters on tinyurl.com). The old short URL stops working. |
| new_description | – | – | New description (null clears it). |
| new_expires_at | – | – | New ISO 8601 expiry; null = never expires. |
| new_stats | boolean | – | true/false = turn click-analytics collection on/off. |
| new_tags | array | – | The complete new tag list; replaces the existing tags (an empty list removes them). |
No output schema declared.
No examples provided.
How do I install the TinyURL MCP by usefulapi server?
TinyURL MCP by usefulapi is a hosted endpoint at https://tinyurl.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 · tinyurl.usefulapi.io
claude mcp add --transport http io-usefulapi-tinyurl 'https://tinyurl.usefulapi.io/mcp'
What is the TinyURL MCP by usefulapi server?
TinyURL MCP by usefulapi is listed in the public MCP registry as io.usefulapi/tinyurl. Create and manage TinyURL short links: aliases, destinations, tags, archive, click analytics. This page covers its hosted endpoint (https://tinyurl.usefulapi.io/mcp).
Is the TinyURL MCP by usefulapi server safe to use?
TinyURL 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 TinyURL MCP by usefulapi server expose?
TinyURL MCP by usefulapi exposes 8 tools: tinyurl_get_link, tinyurl_list_links, tinyurl_count_links, tinyurl_get_analytics, tinyurl_create_link, and 3 more. Their descriptions and schemas cost roughly 1,388 tokens of context every time the server is loaded.
Does the TinyURL MCP by usefulapi server require authentication?
Yes. TinyURL 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 TinyURL MCP by usefulapi server still maintained?
TinyURL 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.