Remote MCP · Endpoint

BasePic MCP server

No. BasePic answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://basepic.com/mcp

The last check completed an MCP handshake.

Registry name
com.basepic/basepic
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
567 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Upload, edit and share images by link: free image hosting for AI agents, no API key.
Website
https://basepic.com/developers
Listing
From the official MCP registry (active).
Recent checks of BasePic
CheckedResultHandshake
1 hour agoHandshake completed567 ms
9 days agoHandshake completed400 ms
10 days agoHandshake completed384 ms
11 days agoHandshake completed399 ms
12 days agoHandshake completed378 ms
14 days agoHandshake completed380 ms
14 days agoHandshake completed392 ms
15 days agoHandshake completed423 ms
17 days agoHandshake completed403 ms
19 days agoHandshake completed391 ms
21 days agoHandshake completed385 ms
24 days agoHandshake completed537 ms
26 days agoHandshake completed409 ms
28 days agoHandshake completed408 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 BasePic and makes no claim about it beyond what these checks measured.