status403 MCP server
com.status403/sitestatus403.comstreamable-httpv1.0.0Scanned
The status403 site as MCP tools: services, technical write-ups, and any page as markdown.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the status403 MCP server can do
The status403 MCP server is published by status403.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: answer_common_question), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (list_services and read_page).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.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.
4 tools
Changes things 1Claude Code: ask
answer_common_questionAnswer the questions clients ask status403 before booking — what the discovery call covers, how feasibility is assessed, what to prepare, whether delivery is production-ready or pr…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Answer the questions clients ask status403 before booking — what the discovery call covers, how feasibility is assessed, what to prepare, whether delivery is production-ready or prototype, blocked and protected targets, and post-launch support. Also returns how a project runs, from first call to handoff. Pass a query to narrow it to the relevant answers.
Annotations the server declares
- readOnlyHint: true
Only reads 3Show 3 read-only tools
list_servicesList the engineering services status403 offers — web scraping, reverse engineering, web3 and dApp engineering, and backend, frontend, and infrastructure engineering for new builds …Reads text others writeNo findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "web": it reads web pages, which anyone can write.
Description, as the server wrote it List the engineering services status403 offers — web scraping, reverse engineering, web3 and dApp engineering, and backend, frontend, and infrastructure engineering for new builds or existing systems — with what each one covers and the anchor link to its section on the page. Pass a query to keep only the services matching a keyword such as "scraping" or "anti-bot".
Annotations the server declares
- readOnlyHint: true
read_pageRead any page of status403 as markdown: "/" for the homepage (services, process, booking, FAQ), "/blog" for the post index, or "/blog/<slug>" for a post in full.Reads text others writeNo findings
Why it is in this group
- The name "read_page" says "read": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "post": it reads posts, which other people can write.
Description, as the server wrote it Read any page of status403 as markdown: "/" for the homepage (services, process, booking, FAQ), "/blog" for the post index, or "/blog/<slug>" for a post in full. This is the same document the site serves to clients that ask for it with `Accept: text/markdown`.
Annotations the server declares
- readOnlyHint: true
search_blogSearch the status403 technical write-ups on antibot systems, TLS fingerprinting, reverse engineering, scraping, and automation architecture.No findings
Why it is in this group
- The name "search_blog" says "search": a word for reading.
Description, as the server wrote it Search the status403 technical write-ups on antibot systems, TLS fingerprinting, reverse engineering, scraping, and automation architecture. Returns matching posts with their title, date, tags, excerpt, and URL — pass a returned path to read_page for the full text. Omit the query to get the most recent posts.
Annotations the server declares
- readOnlyHint: 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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://status403.com/mcp: tools/list returned 4 tools to an anonymous client, including answer_common_question (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http site https://status403.com/mcpclaude mcp add --transport http site https://status403.com/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__site__list_services",
"mcp__site__search_blog",
"mcp__site__read_page"
],
"ask": [
"mcp__site__answer_common_question"
],
"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. Review it before you use it.
Capability tags behind 2 rules
- mcp__site__list_services untrusted-input
- mcp__site__read_page 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/com.status403/site/verify?hash=31ed9cfc82f9c83debd7e7d3a8b0f2c82836cd2c72a2228038c038d883e6eebb" | jq -e '.changed == false'Pinned hash 31ed9cfc82f9, from Nov 18, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.status403/site/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.status403/site)Source: MCP Registry. Synced Nov 18, 2026, 18:17 UTC.
status403 MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the status403 MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 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 status403 MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the status403 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 status403 MCP server have?
- 4 tools: 1 write, 3 read. answer_common_question, list_services, search_blog and read_page.
Does the status403 MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the status403 MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the status403 MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.