Remote MCP · Endpoint

com.seoapi/bingbot MCP server

No. com.seoapi/bingbot answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bingbot.seoapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.seoapi/bingbot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
50 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Validate whether an IP address belongs to Bingbot. Remote MCP server exposing a validate_ip tool.
Website
https://seoapi.com/bingbot/
Listing
From the official MCP registry (active).
Recent checks of com.seoapi/bingbot
CheckedResultHandshake
1 hour agoHandshake completed50 ms
2 days agoHandshake completed48 ms
4 days agoHandshake completed24 ms
5 days agoHandshake completed59 ms
7 days agoHandshake completed59 ms
8 days agoHandshake completed323 ms
9 days agoHandshake completed117 ms
12 days agoHandshake completed32 ms
13 days agoHandshake completed74 ms
15 days agoHandshake completed58 ms
16 days agoHandshake completed61 ms
17 days agoHandshake completed27 ms
19 days agoHandshake completed32 ms
20 days agoHandshake completed28 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed47 ms
22 days agoHandshake completed50 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with com.seoapi/bingbot and makes no claim about it beyond what these checks measured.