WebUpCheck Protect — API abuse controls for your own API MCP Server

by webupcheck Your server? Claim it

answering

WebUpCheck Protect — API abuse controls for your own API is answering right now. Last checked 4 min ago.

Controls for your own verified API: read events, block or release callers, tune route limits.

Uptime history 15 days of history

15 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

227 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check WebUpCheck Protect — API abuse controls for your own API every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add protect --transport http https://app.webupcheck.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://app.webupcheck.com/mcp

~/.codex/config.toml

[mcp_servers.protect]
url = "https://app.webupcheck.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "protect": {
      "url": "https://app.webupcheck.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "protect": {
      "type": "http",
      "url": "https://app.webupcheck.com/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

URL	Transport	State	Latency	Checked
https://app.webupcheck.com/mcp	streamable-http	sign-in	545 ms	4 min ago

Alternatives to WebUpCheck Protect — API abuse controls for your own API

same job, measured the same way

pretix MCP by usefulapi

by usefulapi

Read pretix events, tickets and orders; check attendees in or out with your own account.

18 tools answering

Proctor

by louissarvin

Human oversight for AI agents: block a tool call on a verified human, with on-chain proof.

42 installs/wk local only

Fetch Router

by fetchrouter

Verified web fetch for agents: detects blocks and empty JS pages, falls back, bills only on success.

421 installs/wk 2 tools answering

Pit Officer

by openpitkit

Pre-trade risk limits for AI trading agents: every order is checked before it reaches your broker.

local only

UpFork

by upfork

Verified lessons for your project's packages and versions, and free React components to install.

8 tools answering

Sensefold

by sensefold

Personal context for every AI: search, read, and write back to your private Markdown library.

answering

Proxlane

by proxlane

Web fetch for agents through your own Proxlane gateway. Block pages come back as failures.

230 installs/wk local only

SML Risk Firewall

by scriptmasterlabs

Pre-trade risk checks for agent trades: orders vs your limits, signed receipts.

2 tools answering

WebUpCheck Protect — API abuse controls for your own API — questions

Answers built from our own checks of this server.

Why is there no tool list for WebUpCheck Protect — API abuse controls for your own API?

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 WebUpCheck Protect — API abuse controls for your own API 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 227 ms. The bar chart above shows every period we have measured.

How do I connect WebUpCheck Protect — API abuse controls for your own API?

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 WebUpCheck Protect — API abuse controls for your own API?

No API key is involved. WebUpCheck Protect — API abuse controls for your own API 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 WebUpCheck Protect — API abuse controls for your own API?

It answers our handshake in 227 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.