BeeIMG MCP server
8 tools · Last check that passed 27 Oct 2026, 01:50 UTC
BeeIMG's own remote MCP server lets an agent upload images to BeeIMG's image hosting, from a URL or as file data, and delete them, and, with an API key, create and read albums and folders. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 8 tools
| Tool | Counted as |
|---|---|
delete_image | Deletes |
create_album | Changes things |
create_folder | Changes things |
upload_file | Changes things |
upload_url | Changes things |
beeimg_premium_info | Said to only read |
get_album | Said to only read |
list_albums | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
11 of the last 11 checks passed
A check passes when the server lists its tools. Checked at https://beeimg.com/mcp.
Recent changes
No change seen across the last 11 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when BeeIMG's tools change.
One email when BeeIMG's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its upload tools work with no credentials, so an agent with no BeeIMG account can still host images, fetched from a URL or sent as file data. BeeIMG's MCP setup page
- BeeIMG makes an uploaded image public unless the upload sets its privacy. Its private setting is unlisted: hidden from search, but open to anyone with the link. BeeIMG's API documentation
- The API key is passed to the tools as an apikey argument rather than set in the client's configuration, so the agent sees the key. BeeIMG's MCP setup page
- When an upload fails on a size, storage or rate limit, the server adds a hint pointing at BeeIMG Premium, a paid plan. BeeIMG's MCP setup page
How to limit it
With BeeIMG's own settings, as its documentation describes them. Stackduke has not tested them.
- Set privacy to truly-private on an upload that only its owner should see. BeeIMG says truly-private is a Premium feature, and that private only keeps an image out of search. BeeIMG's API documentation
- Leave the API key out when the agent only uploads, which BeeIMG says works anonymously, and keep the delete_key each anonymous upload returns, which BeeIMG says deleting it requires. BeeIMG's MCP setup page
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.