Remote MCP · Endpoint

Traffic Parrot MCP server

No. Traffic Parrot answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.trafficparrot.com/

The last check completed an MCP handshake.

Registry name
com.trafficparrot/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
161 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Traffic Parrot simulates APIs and messaging. Request or withdraw a trial, read docs, send feedback.
Listing
From the official MCP registry (active).
Recent checks of Traffic Parrot
CheckedResultHandshake
2 hours agoHandshake completed161 ms
1 day agoHandshake completed189 ms
4 days agoHandshake completed160 ms
6 days agoHandshake completed170 ms
9 days agoHandshake completed165 ms
11 days agoHandshake completed185 ms
13 days agoHandshake completed239 ms
15 days agoHandshake completed163 ms
17 days agoHandshake completed200 ms
19 days agoHandshake completed252 ms
20 days agoHandshake completed172 ms
22 days agoHandshake completed172 ms
23 days agoHandshake completed226 ms

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

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