Remote MCP · Endpoint

Shop Nobi MCP server

No. Shop Nobi answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.nobi.ai/v1/shop/mcp

The last check completed an MCP handshake.

Registry name
ai.nobi/shop-nobi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search products from independent stores. Read-only remote MCP; no sign-in. Buy on merchant sites.
Website
https://nobi.ai/shop
Listing
From the official MCP registry (active).
Recent checks of Shop Nobi
CheckedResultHandshake
1 hour agoHandshake completed54 ms
14 hours agoHandshake completed198 ms
1 day agoHandshake completed82 ms
3 days agoHandshake completed59 ms
4 days agoHandshake completed211 ms
4 days agoHandshake completed66 ms
5 days agoHandshake completed55 ms
6 days agoHandshake completed80 ms
8 days agoHandshake completed659 ms
11 days agoHandshake completed75 ms
13 days agoHandshake completed84 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed77 ms
20 days agoHandshake completed102 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.

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