Remote MCP · Endpoint

Miss Yera: IA para empresas MCP server

No. Miss Yera: IA para empresas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://missyera.com/mcp

The last check completed an MCP handshake.

Registry name
com.missyera/missyera
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
149 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
IA para empresas y cursos de Miss Yera, y su kit para conseguir clientes, cobrar, datos y talleres.
Listing
From the official MCP registry (active).
Recent checks of Miss Yera: IA para empresas
CheckedResultHandshake
1 hour agoHandshake completed149 ms
10 days agoHandshake completed124 ms
10 days agoHandshake completed134 ms
11 days agoHandshake completed123 ms
12 days agoHandshake completed133 ms
14 days agoHandshake completed174 ms
14 days agoHandshake completed125 ms
15 days agoHandshake completed131 ms
17 days agoHandshake completed123 ms
19 days agoHandshake completed139 ms
21 days agoHandshake completed125 ms
24 days agoHandshake completed176 ms
26 days agoHandshake completed255 ms
28 days agoHandshake completed136 ms

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

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 Miss Yera: IA para empresas and makes no claim about it beyond what these checks measured.