Skip to content

Tuper Site Check MCP server

app.tuper/site-checktuper.appstreamable-httpv1.3.0Scanned

Check a website in a real browser, or check if AI agents can use it: score, problems, report link.

3 tools: 2 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 3
  • Can send data out · 2
  • 2 findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Tuper Site Check MCP server can do

The Tuper Site Check MCP server is published by tuper.app, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: check_site and check_agent_ready), but cannot delete data. 1 tool only reads.

3 tools bring in text other people can write (check_site, check_agent_ready and get_report); 2 tools can send data out of your system (check_site and check_agent_ready).

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 2, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 2Claude Code: ask
  • check_agent_readyRun a free Tuper Agent-Ready Check on a public website: can AI agents reach, read and use it?Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "check_agent_ready" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a free Tuper Agent-Ready Check on a public website: can AI agents reach, read and use it? Checks robots.txt rules for 12 AI bots (answer bots scored, training bots info only), llms.txt (llmstxt.org format), bot walls and captchas on the sign-up/login/contact pages, text only after JavaScript, sitemap, JSON-LD and prices, MCP/A2A cards, OpenAPI. Returns a 0-100 score, a headline per group, every fail and warning with what to change, and the report URL. Takes 5-30 s. How 40 famous sites score: https://check.tuper.app/agent-ready/league/?src=mcp-league

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
  • check_siteRun a free Tuper Site Check on a public website (measured in a real browser): returns a 0-100 score, counts by severity, the top 5 problems (what, why it matters, where) and the fu…Reads text others writeCan send data out1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "check_site" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a free Tuper Site Check on a public website (measured in a real browser): returns a 0-100 score, counts by severity, the top 5 problems (what, why it matters, where) and the full report URL. Takes 20-90 s. If still running after wait_seconds, returns status "running" and an id for get_report.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true
Only reads 1Show 1 read-only tool
  • get_reportRead a Site Check report by id (from check_site): status (queued, running, done, error), and when done the score, the top findings (up to 20 with all=true) and the report URL.Reads text others writeNo findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "read" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Read a Site Check report by id (from check_site): status (queued, running, done, error), and when done the score, the top findings (up to 20 with all=true) and the report URL.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 17, 2026, 15:24 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
502
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 502.

Posture changes

  1. Nov 17, 2026
    • HTTP status of an anonymous initialize: 521 to 502
  2. Nov 10, 2026
    • HTTP status of an anonymous initialize: 200 to 521
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "check_site" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "check_agent_ready" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 521 -> 502.View diff
    • HTTP status of an anonymous initialize: 521 to 502
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 521; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 521
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
  3. Tools1 added.+1 addedView diff

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http site-check https://mcp-check.tuper.app/mcp
claude mcp add --transport http site-check https://mcp-check.tuper.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__site-check__get_report"
    ],
    "ask": [
      "mcp__site-check__check_site",
      "mcp__site-check__check_agent_ready"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as site-check. Review it before you use it.

Capability tags behind 3 rules
  • mcp__site-check__check_site untrusted-input, outbound
  • mcp__site-check__check_agent_ready untrusted-input, outbound
  • mcp__site-check__get_report untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.tuper/site-check/verify?hash=91518f4ea2c724a6a9650510d1b63dbe3cb8ee1aac9959866e701e257ef33d50" | jq -e '.changed == false'

Pinned hash 91518f4ea2c7, from Nov 2, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.tuper/site-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.tuper/site-check
[![Anlyon Radar](https://radar.anlyon.com/badge/app.tuper/site-check.svg)](https://radar.anlyon.com/servers/app.tuper/site-check)

Source: MCP Registry. Synced Nov 2, 2026, 14:17 UTC.

Tuper Site Check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Tuper Site Check MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Tuper Site Check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Tuper Site Check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Tuper Site Check MCP server have?

3 tools: 2 write, 1 read. check_site, check_agent_ready and get_report.

Does the Tuper Site Check MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Tuper Site Check MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_site and check_agent_ready.

Has the Tuper Site Check MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.