Remote MCP · Endpoint

createavataaars MCP server

No. createavataaars answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://createavataaars.com/mcp

The last check completed an MCP handshake.

Registry name
com.createavataaars/avatars
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
393 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Make avatars in seven illustrated styles, like Avataaars and Notionists, as PNG, SVG or share link.
Listing
From the official MCP registry (active).
Recent checks of createavataaars
CheckedResultHandshake
7 hours agoHandshake completed393 ms
3 days agoHandshake completed208 ms
12 days agoHandshake completed1.06 s
12 days agoHandshake completed259 ms
14 days agoHandshake completed1.08 s
15 days agoHandshake completed1.75 s
16 days agoHandshake completed941 ms
17 days agoHandshake completed951 ms
18 days agoHandshake completed867 ms
20 days agoHandshake completed842 ms
22 days agoHandshake completed242 ms
25 days agoHandshake completed241 ms
27 days agoHandshake completed929 ms
29 days agoHandshake completed284 ms

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

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