Remote MCP · Endpoint

Remover Fundo MCP server

No. Remover Fundo answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_removebg

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/removebg-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
48 ms
Tools exposed
7 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Removes the background from an image by URL, cutting out the foreground person or object with AI and
Listing
From the official MCP registry (active).
Recent checks of Remover Fundo
CheckedResultHandshake
1 day agoHandshake completed48 ms
3 days agoFailed - the request timed out—
5 days agoHandshake completed36 ms
7 days agoHandshake completed50 ms
8 days agoHandshake completed69 ms
9 days agoHandshake completed62 ms
12 days agoHandshake completed61 ms
13 days agoHandshake completed83 ms
15 days agoHandshake completed352 ms
16 days agoHandshake completed3.70 s
18 days agoHandshake completed110 ms
19 days agoHandshake completed103 ms
20 days agoHandshake completed220 ms
20 days agoHandshake completed71 ms
21 days agoHandshake completed66 ms
23 days agoHandshake completed34 ms

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

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