Skip to content

Link in Seconds MCP server

com.linkinseconds/mcplinkinseconds.comstreamable-httpv1.0.0Scanned

Upload a file and get a shareable link. List your links and see their view stats.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Link in Seconds MCP server can do

The Link in Seconds MCP server is published by linkinseconds.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: upload_file, create_upload_url and finish_upload), but cannot delete data. 3 tools only read.

3 tools bring in text other people can write (upload_file, create_upload_url and finish_upload).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • create_upload_urlFor files too big to send inline: returns a short-lived upload URL (valid 10 minutes).Reads text others writeNo findings

    Why it is in this group

    • The name "create_upload_url" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. HTML pages (.html, .htm) need a Pro or Lifetime account that is at least 24 hours old, and are uploaded one at a time: on a Free account the upload is refused with code html_pro_required (html_account_too_new for a newer paid account), so tell the user instead of retrying.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • finish_uploadCall after PUTting the file to the URL from create_upload_url.Reads text others writeNo findings

    Why it is in this group

    • The name "finish_upload" says "upload": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Call after PUTting the file to the URL from create_upload_url. Checks and scans the file, then returns its public link.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • upload_fileUse this when the user wants to share a file, document, image or HTML page as a link.Reads text others writeNo findings

    Why it is in this group

    • The name "upload_file" says "upload": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. HTML pages (.html, .htm) need a Pro or Lifetime account that is at least 24 hours old, and are uploaded one at a time: on a Free account the upload is refused with code html_pro_required (html_account_too_new for a newer paid account), so tell the user instead of retrying.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_account_analyticsRead-only.No findings

    Why it is in this group

    • The name "get_account_analytics" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://linkinseconds.com/.well-known/oauth-protected-resource/api/mcp
Authorization servers
https://linkinseconds.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://linkinseconds.com/api/mcp: tools/list returned 6 tools to an anonymous client, including upload_file (write), create_upload_url (write), finish_upload (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http linkinseconds https://linkinseconds.com/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http linkinseconds https://linkinseconds.com/api/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__linkinseconds__list_links",
      "mcp__linkinseconds__get_link_analytics",
      "mcp__linkinseconds__get_account_analytics"
    ],
    "ask": [
      "mcp__linkinseconds__upload_file",
      "mcp__linkinseconds__create_upload_url",
      "mcp__linkinseconds__finish_upload"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as linkinseconds. Review it before you use it.

Capability tags behind 3 rules
  • mcp__linkinseconds__upload_file untrusted-input
  • mcp__linkinseconds__create_upload_url untrusted-input
  • mcp__linkinseconds__finish_upload untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.linkinseconds/mcp/verify?hash=2c5b8e1447c81c1e2dd95dbe35bdeeae36a1c40bc284dd6f21b674650ac281b2" | jq -e '.changed == false'

Pinned hash 2c5b8e1447c8, from Nov 13, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.linkinseconds/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.linkinseconds/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.linkinseconds/mcp.svg)](https://radar.anlyon.com/servers/com.linkinseconds/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

Link in Seconds MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Link in Seconds MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Link in Seconds MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Link in Seconds MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Link in Seconds MCP server have?

6 tools: 3 write, 3 read. upload_file, create_upload_url, finish_upload, list_links, get_link_analytics and get_account_analytics.

Does the Link in Seconds MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Link in Seconds MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Link in Seconds MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.