Remote MCP · Endpoint

Content Moderation API MCP server

Yes, as of 7 hours ago: the server returned an HTTP error.

DownLast checked 7 hours ago

Server URL

https://content-moderation-api-hhy1.onrender.com/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.cmondillo/content-moderation-api
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
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.
Listing
From the official MCP registry (active).
Recent checks of Content Moderation API
CheckedResultHandshake
7 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoHandshake completed236 ms
5 days agoHandshake completed412 ms
7 days agoHandshake completed305 ms
8 days agoHandshake completed376 ms
9 days agoHandshake completed380 ms
12 days agoHandshake completed464 ms
13 days agoHandshake completed368 ms
15 days agoFailed - the server returned an HTTP error—
16 days agoFailed - the server returned an HTTP error—
17 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoFailed - the server returned an HTTP error—
21 days agoFailed - the server returned an HTTP error—
22 days agoFailed - the server returned an HTTP error—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 7 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 Content Moderation API and makes no claim about it beyond what these checks measured.