status403
The status403 site as MCP tools: services, technical write-ups, and any page as markdown.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"site": {
"url": "https://status403.com/mcp"
}
}
}Remote endpoints
https://status403.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (4)
🟢list_services(query)
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".
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Optional keyword to filter by. Omit to list every service."
}
},
"additionalProperties": false
}🟢answer_common_question(query)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Optional keyword, such as \"support\" or \"feasibility\". Omit for everything."
}
},
"additionalProperties": false
}🟢search_blog(query, limit)
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.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Words to search for in titles, tags, excerpts, and post bodies."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 20,
"default": 5,
"description": "How many posts to return, most relevant first."
}
},
"additionalProperties": false
}🟢read_page(path)
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`.
Input Schema
{
"type": "object",
"properties": {
"path": {
"type": "string",
"description": "Site path, such as \"/\" or \"/blog/<slug>\". A full status403.com URL works too."
}
},
"required": [
"path"
],
"additionalProperties": false
}Community
Evidence