Link in Seconds
REMOTE · LINKINSECONDS.COM
Upload a file and get a shareable link. List your links and see their view stats.
Available components
Last scanned (1 hour ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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 Security94
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1173 tokens (~195/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 Management73
- Stability observed for 22 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 0
- Tool “upload_file” rewrote its description, which is the text the model reads security
- “upload_file” added an optional parameter “file” cosmetic
- “upload_file” reworded the description of “filename” cosmetic
- “upload_file” made “filename” optional cosmetic
- 22 Oct 26 +2
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “create_upload_url” rewrote its description, which is the text the model reads security
- Tool “get_link_analytics” rewrote its description, which is the text the model reads security
- Tool “upload_file” rewrote its description, which is the text the model reads security
- Schema quality: 134 → 185 ▼ functional
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 5 Nov 2026 · Probed https://linkinseconds.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=linkinseconds.com | CN=YR2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | RSA 2048 | SHA256-RSA | 5201225b89a35e28aed27d66708ea90eedd |
| SANs: linkinseconds.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of linkinseconds.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| linkinseconds.com. | 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 | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://linkinseconds.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://linkinseconds.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(self), geolocation=(), browsing-topics=() |
Protected resource metadata
| Document | https://linkinseconds.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://linkinseconds.com/api/mcp |
| Authorisation server | https://linkinseconds.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://linkinseconds.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://linkinseconds.com/api/mcp | HTTPS enforced | 308 | https://linkinseconds.com/api/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 →
create_upload_url Start a large upload ~187
For files too big to send inline: returns a short-lived upload URL (valid 10 minutes). PUT the raw file bytes to it with the given Content-Type header (for example with curl), then call finish_upload with the returned path. Per-file limit: 250 MB on the Free plan, 500 MB on Pro and Lifetime. A bigger file is refused, so tell the user it is over the limit instead of asking for it. Programs and scripts (.exe, .msi, .dmg, .apk, .app, .bat, .sh, .jar, .dll and similar) are always blocked: say so and do not try to upload them.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | MIME type. Optional: guessed from the extension. |
| filename | string | yes | File name with extension. |
| size_bytes | integer | yes | Exact file size in bytes. |
No output schema declared.
No examples provided.
finish_upload Finish a large upload ~132
Call after PUTting the file to the URL from create_upload_url. Checks and scans the file, then returns its public link.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | The same content type used for the PUT. Optional. |
| filename | string | yes | The same file name passed to create_upload_url. |
| path | string | yes | The path returned by create_upload_url. |
| slug | string | – | Optional custom link name, the last part of the link address (letters, numbers and dashes). It must be free; reserved words are refused. |
| title | string | – | Optional link title shown on the page. |
No output schema declared.
No examples provided.
get_account_analytics Analytics across all links ~79
Read-only. The whole account's analytics over a UTC window: views, unique visitors, time on files, countries, devices, traffic sources, busiest hour and the top links.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | Time window, UTC days: 7d, 14d, 30d (default), 90d or all. |
No output schema declared.
No examples provided.
get_link_analytics Analytics for one link ~151
Read-only. Use this when the user asks whether someone opened a link, or how it did. How one of the account's links performed: views, unique visitors, time on the file, how far readers got (pages for PDFs, watch-through for video and audio, scroll depth for pages), countries, devices, traffic sources and the busiest hour, over a UTC window. Pass the slug or the full link URL.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | Time window, UTC days: 7d, 14d, 30d (default), 90d or all. |
| slug | string | yes | The link's slug (the last part of its address), or its full URL. |
No output schema declared.
No examples provided.
list_links List my links ~42
List the links on this Link in Seconds account, newest first, with their URLs and status.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return (default 20). |
No output schema declared.
No examples provided.
upload_file Upload a file and get a link ~393
Use this when the user wants to share a file, document, image or HTML page as a link. Publish a file and get a public Link in Seconds URL that opens in any browser (no sign-in for the viewer). If the user attached a file in the chat, pass it in `file` (any size the plan allows). Otherwise pass the file as text in `content` (HTML, Markdown, CSV, SVG, JSON...) or as base64 in `content_base64` (PDF, images, ZIP...), up to 3 MB; for bigger files use create_upload_url. The account's plan limits apply. Per-file limit: 250 MB on the Free plan, 500 MB on Pro and Lifetime. A bigger file is refused, so tell the user it is over the limit instead of asking for it. Programs and scripts (.exe, .msi, .dmg, .apk, .app, .bat, .sh, .jar, .dll and similar) are always blocked: say so and do not try to upload them.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The file content as UTF-8 text. Use this OR content_base64. |
| content_base64 | string | – | The file content, base64-encoded. Use this OR content. |
| content_type | string | – | MIME type. Optional: guessed from the extension. |
| file | object | – | A file the user attached in ChatGPT. ChatGPT fills this in; do not invent it. |
| filename | string | – | File name with extension, e.g. report.pdf or index.html. Optional with `file` (its own name is used). |
| slug | string | – | Optional custom link name, the last part of the link address (letters, numbers and dashes). It must be free; reserved words are refused. |
| title | string | – | Optional link title shown on the page. |
No output schema declared.
No examples provided.
How do I install the Link in Seconds MCP server?
Link in Seconds is a hosted endpoint at https://linkinseconds.com/api/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 · linkinseconds.com
claude mcp add --transport http com-linkinseconds-mcp 'https://linkinseconds.com/api/mcp'
What is the Link in Seconds MCP server?
Link in Seconds is an MCP server listed in the public MCP registry as com.linkinseconds/mcp. Upload a file and get a shareable link. List your links and see their view stats. This page covers its hosted endpoint (https://linkinseconds.com/api/mcp).
Is the Link in Seconds MCP server safe to use?
Link in Seconds scores 88 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 Link in Seconds MCP server expose?
Link in Seconds exposes 6 tools: upload_file, create_upload_url, finish_upload, list_links, get_link_analytics, get_account_analytics. Their descriptions and schemas cost roughly 984 tokens of context every time the server is loaded.
Does the Link in Seconds MCP server require authentication?
Yes. Link in Seconds 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 Link in Seconds MCP server still maintained?
Link in Seconds is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.