Remote MCP · Endpoint

app.decibelshield/decibel-shield MCP server

No. app.decibelshield/decibel-shield answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://decibelshield.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.decibelshield/decibel-shield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Noise data tools: city noise rankings, decibel levels of common sounds, NIOSH safe-exposure math.
Listing
From the official MCP registry (active).
Recent checks of app.decibelshield/decibel-shield
CheckedResultHandshake
1 hour agoHandshake completed134 ms
10 hours agoHandshake completed310 ms
1 day agoHandshake completed139 ms
2 days agoHandshake completed122 ms
4 days agoHandshake completed119 ms
4 days agoHandshake completed207 ms
5 days agoHandshake completed151 ms
6 days agoHandshake completed141 ms
8 days agoHandshake completed124 ms
11 days agoHandshake completed143 ms
13 days agoHandshake completed144 ms
16 days agoHandshake completed145 ms
18 days agoHandshake completed154 ms
20 days agoHandshake completed432 ms
22 days agoHandshake completed149 ms
24 days agoHandshake completed148 ms
26 days agoHandshake completed155 ms
27 days agoHandshake completed142 ms
29 days agoHandshake completed132 ms

The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with app.decibelshield/decibel-shield and makes no claim about it beyond what these checks measured.