Remote MCP · Endpoint

Avocado AI MCP server

Yes, as of 2 hours ago: the response was not JSON-RPC.

DownLast checked 2 hours ago

Server URL

https://mcp.avocadoai.co/

The last check failed: the response was not JSON-RPC.

Registry name
io.github.Wandersonjack/avocado
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
Not measured yet
Uptime, last 30 days
4 checks from 4 checks
Described by its publisher as
Generate AI images, videos, music, SFX & speech in any AI assistant. Results appear inline in chat.
Website
https://avocadoai.co/
Repository
https://github.com/Wandersonjack/avocado-ai-app
Listing
From the official MCP registry (active).
Recent checks of Avocado AI
CheckedResultHandshake
2 hours agoFailed - the response was not JSON-RPC—
10 hours agoFailed - the response was not JSON-RPC—
1 day agoFailed - the response was not JSON-RPC—
2 days agoFailed - the response was not JSON-RPC—

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Avocado AI and makes no claim about it beyond what these checks measured.