Remote MCP · Endpoint

Pechincha.ai MCP server

No. Pechincha.ai answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pechincha.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.pechincha/deals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Brazilian deals: search active promos, coupons and price history from Brazilian online stores.
Listing
From the official MCP registry (active).
Recent checks of Pechincha.ai
CheckedResultHandshake
1 hour agoHandshake completed185 ms
2 days agoHandshake completed242 ms
5 days agoHandshake completed337 ms
7 days agoHandshake completed194 ms
9 days agoHandshake completed188 ms
11 days agoHandshake completed192 ms
13 days agoHandshake completed203 ms
15 days agoHandshake completed319 ms
17 days agoHandshake completed182 ms
19 days agoHandshake completed384 ms
20 days agoHandshake completed212 ms
21 days agoHandshake completed342 ms
22 days agoHandshake completed188 ms
25 days agoHandshake completed228 ms

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

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