WebUpCheck Protect — API abuse controls for your own API

com.webupcheckPublished by webupcheck.comOfficial publisherv1.1.0Updated Oct 25, 2026

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

The publisher's own server: WebUpCheck — DNS, Website & Provider Diagnostics

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant read events and manage abuse controls — blocking, releasing callers and tuning route limits — for your own verified,

What you can do
Read events recorded for your own verified API, such as caller activity and abuse signals, to see what is happening on your routes. Block or release callers, so the assistant can act on suspicious traffic rather than only report it. Tune route limits to adjust how much traffic each route allows. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you already have an API registered with WebUpCheck Protect and want an assistant to review abuse events or apply blocking, releasing and rate-limit changes without opening the dashboard. Less relevant if you do not use this service or do not control the API being protected.
Requirements
A remote streamable HTTP endpoint at app.webupcheck.com; no local package or runtime is needed. OAuth authentication is required, so you need a WebUpCheck account with access to the API you want to protect. No environment variables or headers are declared.
Before you install
The server can change live traffic controls: blocking or releasing callers and tuning route limits affect real users and clients, so review actions before they are applied. It only covers APIs you have verified as your own. Access is granted through OAuth, so treat that authorization as sensitive. No further details on data handling are provided.

Installation

In SourceWeft

  1. Open WebUpCheck Protect — API abuse controls for your own API in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.webupcheck%2Fprotect/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "webupcheck-protect-api-abuse-controls-fo": {
      "type": "http",
      "url": "https://app.webupcheck.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestOct 25, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Webupcheck integrations