Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PicSee Short Link

REMOTE · API.PICSEE.IO · SCANNED SEP 27

Official PicSee MCP server for short links, link management, click analytics, and optional OAuth.

Available components

0 this week 72 Trust /100
Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 453 tokens (~453/item across 1 items; 1 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

How do I install the PicSee Short Link MCP server?

PicSee Short Link is a hosted endpoint at https://api.picsee.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 · api.picsee.io

# add to Claude Code
claude mcp add --transport http io-picsee-short-link 'https://api.picsee.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-picsee-short-link": {
      "url": "https://api.picsee.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-picsee-short-link": {
      "type": "http",
      "url": "https://api.picsee.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-picsee-short-link]
url = "https://api.picsee.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-picsee-short-link": {
      "type": "remote",
      "url": "https://api.picsee.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-picsee-short-link --url 'https://api.picsee.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-picsee-short-link:
    url: "https://api.picsee.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-picsee-short-link": {
      "Transport": "http",
      "Url": "https://api.picsee.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-picsee-short-link -t streamable-http -u 'https://api.picsee.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-picsee-short-link": {
      "type": "http",
      "url": "https://api.picsee.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 27 Sept 2026 · Probed https://api.picsee.io/mcp

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=picsee.io CN=Amazon RSA 2048 M01,O=Amazon,C=US 6 Feb 2026 6 Mar 2027 RSA 2048 SHA256-RSA cd34a40395289dfc2d3420eca6cdd2a
SANs: picsee.io, *.picsee.io
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.picsee.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
picsee.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.picsee.io/mcp Verified 200
http (plaintext) http://api.picsee.io/mcp Inconclusive 302 http://pics.ee/mcp/analytics
MCP tools · 1 exposed · ~357 tokens

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 →

Tool Tokens
create_short_link ~357

Create a new PicSee short link from a destination URL. `url` is required; every other field is optional. Anonymous callers are pinned to the `pse.is` domain — any `domain` value supplied is ignored. The response contains `picseeUrl`, the shortened link ready to share.

NameTypeReqDescription
domainstring–Domain to host the short link on (e.g. `pse.is` or one of the BSDs from `get_my_domains`). Falls back to the account default when omitted or invalid.
encodeIdstring–Custom slug (3-90 chars; English letters, digits, `_`, `-`, or Chinese). Must be globally unique on PicSee — conflicts return `PUB00503`. Omit to let PicSee auto-generate.
externalIdstring–Free-form identifier (1-100 chars) for grouping / attributing links. Surfaces in `list_short_links` filters and `get_api_usage_by_external_id`. When the user has not specified a value, you (the calli…
urlstringyesDestination URL the short link should redirect to. Required.
utmobject–UTM parameters appended to the destination URL. Pass `null` on edit to clear all previously set UTM values.

No output schema declared.

No examples provided.

Common questions

What is the PicSee Short Link MCP server?

PicSee Short Link is an MCP server listed in the public MCP registry as io.picsee/short-link. Official PicSee MCP server for short links, link management, click analytics, and optional OAuth. This page covers its hosted endpoint (https://api.picsee.io/mcp).

Is the PicSee Short Link MCP server safe to use?

PicSee Short Link scores 72 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 PicSee Short Link MCP server expose?

PicSee Short Link exposes 1 tool: create_short_link. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.

Does the PicSee Short Link MCP server require authentication?

No. We connected to PicSee Short Link without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PicSee Short Link MCP server still maintained?

PicSee Short Link is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.