1000+ creative ways to say no. Polite, humorous, professional rejection responses.
{
"mcpServers": {
"noaas": {
"env": {
"API_BASE_URL": "https://api.mcp-for-no.com"
},
"args": [
"/YOUR/PATH/HERE/no-as-a-service/build/mcp-server.js"
],
"command": "node"
}
}
}1000+ creative ways to say no. Polite, humorous, professional rejection responses.
Is it safe?
No known CVEs for wrangler. 4 previously resolved.
No authentication — any process on your machine can connect.
License not specified.
Is it maintained?
Last commit 73 days ago. 5,720,675 weekly downloads.
Will it work with my client?
Transport: stdio, sse, http. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y wrangler 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationNo open vulnerabilities. 4 fixed CVEs.
CVE-2026-0933FixedWrangler affected by OS Command Injection in `wrangler pages deploy`
**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl
CVE-2023-7080FixedArbitrary remote code execution within `wrangler dev` Workers sandbox
### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
CVE-2023-7079FixedArbitrary remote file read in Wrangler dev server
### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr
CVE-2023-3348FixedCloudflare Wrangler directory traversal vulnerability
### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3