get_neighborhood_noise — decibel shield MCP Tool Read-only
get_neighborhood_noise
(get neighborhood noise) is one of 10 tools on the
decibel shield
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_neighborhood_noise from your client
- Claude Code decibel shield get_neighborhood_noise run in your project directory
- Claude Desktop decibel shield get_neighborhood_noise ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor decibel shield get_neighborhood_noise ~/.cursor/mcp.json
- VS Code decibel shield get_neighborhood_noise .vscode/mcp.json
- Zed decibel shield get_neighborhood_noise ~/.config/zed/settings.json
- Windsurf decibel shield get_neighborhood_noise ~/.codeium/windsurf/mcp_config.json
- Cline decibel shield get_neighborhood_noise ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI decibel shield get_neighborhood_noise ~/.gemini/settings.json
- Grok decibel shield get_neighborhood_noise .mcp.json (in your project root)
- ChatGPT decibel shield get_neighborhood_noise Settings → Connectors → Advanced → Developer mode
- Claude.ai decibel shield get_neighborhood_noise Settings → Connectors → Add custom connector
- LangChain decibel shield get_neighborhood_noise pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http decibel-shield https://decibelshield.app/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.