mcpbeat Sign in

LickityClick MCP Server

answering

LickityClick is answering right now. Last checked 14 min ago. 178 installs a week from npm.

Create, edit and track LickityClick short links, campaigns and click stats from your AI assistant.

Installs per day peak 178 · avg 5
a month agotoday
Uptime history 26 hours of history
26 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
432 ms
Response time
average over 24h
178
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check LickityClick every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp --transport http https://app.lickity.click/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.lickity.click/api/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://app.lickity.click/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://app.lickity.click/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://app.lickity.click/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.lickity.click/api/mcp streamable-http sign-in 405 ms 14 min ago

Alternatives to LickityClick

same job, measured the same way
Rus.sh
by rus

Make, find, pause and track short links and QR codes from your AI assistant.

answering
QRSalt
by qrsalt

Make, re-point and track QR codes and short links, and read QR images, from your AI assistant.

answering
Linkonda
by linkonda

Create and manage Linkonda short links from an AI assistant, with no per-visitor tracking.

83 installs/wk local only
Whooshly MCP
by whooshly

Create short links, QR codes, UTM templates, vCards, and landing pages from your AI assistant.

88 installs/wk answering
Naano
by naano

B2B LinkedIn creator campaigns from your AI assistant: find creators, run campaigns, read results.

answering
LotsLink
by lots

Free, unlimited short links, QR codes and click analytics your AI agent can create and track.

answering
LISTN
by listnlive

Music promotion from your AI assistant: analyze tracks, prepare radio and creator campaign drafts.

answering
MindMeister
by mindmeister

Create, edit, and organize MindMeister mind maps from your AI assistant.

answering

LickityClick — questions

Answers built from our own checks of this server.

Why is there no tool list for LickityClick?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is LickityClick working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 432 ms. The bar chart above shows every period we have measured.
How do I connect LickityClick?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to LickityClick?
No API key is involved. LickityClick answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is LickityClick?
It answers our handshake in 432 ms on average, which is faster than 29% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use LickityClick?
The npm package @lickityclick/mcp was installed 178 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.