Remote MCP · Endpoint
Content Moderation API MCP server
No. Content Moderation API answered an MCP handshake 2 days ago.
UpLast checked 2 days 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
- 390 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 41.2% from 17 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 |
|---|---|---|
| 2 days ago | Handshake completed | 390 ms |
| 3 days ago | Handshake completed | 703 ms |
| 4 days ago | Handshake completed | 560 ms |
| 5 days ago | Handshake completed | 549 ms |
| 7 days ago | Handshake completed | 388 ms |
| 7 days ago | Handshake completed | 341 ms |
| 8 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Failed - the server returned an HTTP error | — |
| 14 days ago | Failed - the server returned an HTTP error | — |
| 16 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 | Failed - the server returned an HTTP error | — |
| 27 days ago | Failed - the server returned an HTTP error | — |
| 29 days ago | Handshake completed | 236 ms |
| 30 days ago | Handshake completed | 412 ms |
| 32 days ago | Handshake completed | 305 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 Content Moderation API and makes no claim about it beyond what these checks measured.