MCP.Market

Snipzr MCP server

online · 100% uptime
by snipzr.com·com.snipzr/mcp·v1.32.0

Short links with branded domains, cookie-less analytics and QR codes. Sign in with OAuth or a token

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Snipzr yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Snipzr tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 202ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Snipzr compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,243 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
694 ms
faster than 22% of 30,027 servers

Release history: 2 versions in the registry since 2026-09-06, latest 2026-10-10, typically one every 34 days.

Install Snipzr in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.snipzr.com/mcp
Add to Cursor

What the publisher says

From the Snipzr repository's README, as published. We do not edit it. Read it on GitHub

Snipzr MCP Server

The official Snipzr MCP server. One hosted endpoint gives any MCP client thirteen tools to create, manage and measure short links: branded domains, batch creation, cookie-less analytics, campaign reports, UTM building and QR codes.

https://mcp.snipzr.com/mcp

There is nothing to install or run. The server is remote (Streamable HTTP), stateless and available on every paid Snipzr plan. This repository is its public home: setup, the tool reference and the registry metadata. The server itself is part of the Snipzr platform, and its tools are thin adapters over the same handlers that serve the public REST API, so the two surfaces always behave identically.

Quick start

1. Connect with sign-in (recommended). Most clients need no token at all: point them at the server address and they open a Snipzr sign-in. The consent screen shows exactly which permissions the application gets and which of your workspaces it may act in; untick anything you do not want, and disconnect it later from Settings.

Claude Code, two commands:

claude mcp add --transport http snipzr https://mcp.snipzr.com/mcp
claude mcp login snipzr

Claude on the web, desktop and mobile: open Settings, then Connectors, then Add custom connector, enter the server address and select Connect. ChatGPT connects the same way in developer mode. Smithery, Glama and other directories connect through the same sign-in.

2. Or use a token. In Settings, create a token and copy the secret (it is shown exactly once):

  • User API tokens act as you. Pick the workspaces the token may act in and what it may do in each one.
  • Workspace API tokens belong to one workspace and act as that workspace. The right choice for a shared team assistant or a client without a browser.

Cursor, VS Code and any other MCP client take the generic remote config:

{
  "mcpServers": {
    "snipzr": {
      "url": "https://mcp.snipzr.com/mcp",
      "headers": { "Authorization": "Bearer YOUR_TOKEN" }
    }
  }
}

A client that only speaks stdio can bridge with npx mcp-remote https://mcp.snipzr.com/mcp --header "Authorization: Bearer YOUR_TOKEN".

3. Confirm it worked. Ask your assistant to list the Snipzr tools. Thirteen names starting with snipzr_ means you are connected.

The thirteen tools

Every tool carries read-only or destructive annotations, so well-behaved clients ask before a delete and never before a read, and every tool publishes an output schema and returns structured content beside the text, so agents read fields instead of parsing prose.

Access model

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Snipzr: common questions

Is Snipzr MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Snipzr safety report
How do I install Snipzr?
It runs remotely at mcp.snipzr.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Snipzr need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Snipzr maintained?
The last commit was 21 days ago (2026-10-15). The latest release is v1.32.0.
Is Snipzr up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Snipzr compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 694 ms (faster than 22% of 30,027 servers). Full comparison.