graphql-dos-shield
Cloudflare Workers MCP server: graphql-dos-shield
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": {
"graphql-dos-shield": {
"url": "https://api.lazy-mac.com/graphql-dos-shield/mcp"
}
}
}Remote endpoints
https://api.lazy-mac.com/graphql-dos-shield/mcpstreamable-httpWhat it can do
Tool inventory
Tools (3)
🟢complexity_meter(query)
Analyze GraphQL query complexity. Returns depth, field count, list multipliers, and a risk level (LOW/MEDIUM/HIGH/CRITICAL). CRITICAL means the query should be rejected.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "GraphQL query string to analyze"
}
},
"required": [
"query"
]
}🟢rate_limiter(client_id, limit, window_ms)
Check and enforce rate limiting for a client. In-memory sliding window — state resets on cold start.
Input Schema
{
"type": "object",
"properties": {
"client_id": {
"type": "string",
"description": "Unique client identifier"
},
"limit": {
"type": "integer",
"description": "Max requests per window (default: 100)"
},
"window_ms": {
"type": "integer",
"description": "Window in ms (default: 60000)"
}
},
"required": [
"client_id"
]
}🟢query_rewriter(query, max_depth, max_fields)
Text-level rewrite of an overly complex GraphQL query: strips excess nesting depth and truncates too many fields.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "GraphQL query to simplify"
},
"max_depth": {
"type": "integer",
"description": "Max nesting depth (default: 3)"
},
"max_fields": {
"type": "integer",
"description": "Max fields (default: 10)"
}
},
"required": [
"query"
]
}Community
Evidence