PicSee Short Link MCP

endpoint

https://api.picsee.io/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is PicSee Short Link MCP live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is PicSee Short Link MCP free to use?

Not measured yet.

What tools does PicSee Short Link MCP have?

1 tool: create_short_link.

Is PicSee Short Link MCP safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• create_short_link changes data unknown never probed

  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.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "format": "uri",
        "maxLength": 2048,
        "description": "Destination URL the short link should redirect to. Required."
      },
      "utm": {
        "type": "object",
        "properties": {
          "term": {
            "type": "string",
            "description": "utm_term"
          },
          "medium": {
            "type": "string",
            "description": "utm_medium"
          },
          "source": {
            "type": "string",
            "description": "utm_source"
          },
          "content": {
            "type": "string",
            "description": "utm_content"
          },
          "campaign": {
            "type": "string",
            "description": "utm_campaign"
          }
        },
        "description": "UTM parameters appended to the destination URL. Pass `null` on edit to clear all previously set UTM values.",
        "additionalProperties": false
      },
      "domain": {
        "type": "string",
        "description": "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."
      },
      "encodeId": {
        "type": "string",
        "maxLength": 90,
        "minLength": 3,
        "description": "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."
      },
      "externalId": {
        "type": "string",
        "maxLength": 100,
        "minLength": 1,
        "description": "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 calling AI agent) SHOULD default this to your own product name so the account owner can attribute API usage back to the agent that created the link — e.g. `Claude Code`, `Codex`, `Cursor`, `ChatGPT`, `Gemini CLI`, `Copilot`. Use the canonical product name only; do not include version numbers or session IDs. If the user explicitly provides an `externalId`, always honor their value instead."
      }
    },
    "additionalProperties": false
  }

  arguments 59 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.