Remote MCP · Endpoint

101 Soundboards MCP server

No. 101 Soundboards answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://www.101soundboards.com/mcp/search

The last check completed an MCP handshake.

Registry name
com.101soundboards/search
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Search millions of sound and soundboards on 101soundboards.com
Listing
From the official MCP registry (active).
Recent checks of 101 Soundboards
CheckedResultHandshake
1 day agoHandshake completed54 ms
3 days agoHandshake completed61 ms
5 days agoHandshake completed62 ms
6 days agoHandshake completed94 ms
8 days agoHandshake completed56 ms
9 days agoHandshake completed76 ms
10 days agoHandshake completed53 ms
13 days agoHandshake completed58 ms
14 days agoHandshake completed51 ms
16 days agoHandshake completed63 ms
17 days agoHandshake completed51 ms
18 days agoHandshake completed336 ms
19 days agoHandshake completed51 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed69 ms
22 days agoHandshake completed66 ms
23 days agoHandshake completed46 ms

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

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 101 Soundboards and makes no claim about it beyond what these checks measured.