BackGone Background Removal MCP server
io.github.oogwaaay/backgoneoogwaaaystreamable-httpv1.0.0Scanned
Remove image backgrounds (transparent PNG/WebP) and look up passport photo rules.
3 tools: 1 can delete or cancel things, 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the BackGone Background Removal MCP server can do
The BackGone Background Removal MCP server is published by the GitHub account oogwaaay. It has 3 tools. It can delete or cancel things (1 tool: remove_background) and create or change data (1 tool: check_photo_requirements). 1 tool only reads.
1 tool brings in text other people can write (remove_background).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Deletes or cancels 1Claude Code: deny
remove_backgroundRemoves the background from one image with BackGone’s production engine and returns a transparent PNG (or WebP) inline.Reads text others write1 finding
Why it is in this group
- The name "remove_background" says "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "remove_background" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "remove_background" says "remove": a word for removing or ending something.
Description, as the server wrote it Removes the background from one image with BackGone’s production engine and returns a transparent PNG (or WebP) inline. Costs 1 API credit on success; failed calls are not charged. Requires an API key sent as "Authorization: Bearer sk_..." — create one at https://backgone.com/settings/apikeys and top up API credits at https://backgone.com/pricing. Provide exactly one of image_url or image_base64.
Annotations the server declares
- title: Remove an image background
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
check_photo_requirementsFree.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Free. Returns the official passport or ID photo requirements for a country (printed size, head height, background, digital file rules, whether editing is allowed, the official source URL and the date we verified it). Call without a country to list the countries covered. No API key needed.
Annotations the server declares
- title: Passport / ID photo requirements
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_pricingFree.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it Free. Returns the current BackGone prices: API credit top-up packs (one image = one API credit, credits never expire) and the website subscription/credit-pack tiers. No API key needed.
Annotations the server declares
- title: BackGone pricing
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://backgone.com/mcp: tools/list returned 3 tools to an anonymous client, including remove_background (destructive), check_photo_requirements (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "remove_background" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "remove_background" says "remove": a word for removing or ending something.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http backgone https://backgone.com/mcpclaude mcp add --transport http backgone https://backgone.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__backgone__get_pricing"
],
"ask": [
"mcp__backgone__check_photo_requirements"
],
"deny": [
"mcp__backgone__remove_background"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as backgone. Review it before you use it.
Capability tags behind 1 rule
- mcp__backgone__remove_background untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.oogwaaay/backgone/verify?hash=abded83e4ae318c0136a1674f564c390f90ebce9d0698f2b4a98a4d1d2670bf6" | jq -e '.changed == false'Pinned hash abded83e4ae3, from Nov 15, 2026, 13:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.oogwaaay/backgone/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.oogwaaay/backgone)Source: MCP Registry. Synced Nov 2, 2026, 08:17 UTC.
BackGone Background Removal MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the BackGone Background Removal MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the BackGone Background Removal MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: remove_background.
Can the BackGone Background Removal MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the BackGone Background Removal MCP server have?
- 3 tools: 1 destructive, 1 write, 1 read. remove_background, check_photo_requirements and get_pricing.
Does the BackGone Background Removal MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the BackGone Background Removal MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the BackGone Background Removal MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.