Remote MCP · Endpoint

BarterBanner MCP server

No. BarterBanner answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://barterbanner.com/mcp

The last check completed an MCP handshake.

Registry name
com.barterbanner/barterbanner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
556 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Traffic exchange for independent websites: network stats, members, campaigns and site reports.
Listing
From the official MCP registry (active).
Recent checks of BarterBanner
CheckedResultHandshake
1 hour agoHandshake completed556 ms
2 days agoHandshake completed551 ms
5 days agoHandshake completed566 ms
7 days agoHandshake completed532 ms
9 days agoHandshake completed531 ms
11 days agoHandshake completed1.17 s
13 days agoHandshake completed522 ms
15 days agoHandshake completed526 ms
18 days agoHandshake completed519 ms
19 days agoHandshake completed524 ms
21 days agoHandshake completed524 ms
21 days agoHandshake completed523 ms
23 days agoHandshake completed541 ms
25 days agoHandshake completed526 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 BarterBanner and makes no claim about it beyond what these checks measured.