Remote MCP · Endpoint
Content Moderation API MCP server
No. Content Moderation API answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://content-moderation-api-hhy1.onrender.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cmondillo/content-moderation-api
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 560 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 44.4% from 18 checks
- Described by its publisher as
- Pay-per-call profanity/explicit-content detection for AI agents. $0.005 USDC per call, no signup.
- Repository
- https://github.com/cmondillo/tools
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 560 ms |
| 1 day ago | Handshake completed | 549 ms |
| 3 days ago | Handshake completed | 388 ms |
| 3 days ago | Handshake completed | 341 ms |
| 4 days ago | Failed - the server returned an HTTP error | — |
| 5 days ago | Failed - the server returned an HTTP error | — |
| 7 days ago | Failed - the server returned an HTTP error | — |
| 10 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Failed - the server returned an HTTP error | — |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 23 days ago | Failed - the server returned an HTTP error | — |
| 25 days ago | Handshake completed | 236 ms |
| 26 days ago | Handshake completed | 412 ms |
| 28 days ago | Handshake completed | 305 ms |
| 29 days ago | Handshake completed | 376 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 29.
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 Content Moderation API and makes no claim about it beyond what these checks measured.