Uploadcare MCP by usefulapi
io.usefulapi/uploadcareusefulapi.iostreamable-httpv1.40.4Scanned
Manage Uploadcare files, groups and webhooks; upload and store files.
11 tools: 4 can delete or cancel things and 7 only read.
- Reads private data · 5
- Reads text others write · 1
- Can send data out · 0
- No findings
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Uploadcare MCP by usefulapi can do
The Uploadcare MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 11 tools. It can delete or cancel things (4 tools: uploadcare_upload_from_url, uploadcare_store_file, uploadcare_delete_file and uploadcare_create_webhook). 7 tools only read.
5 tools read private data (uploadcare_list_files, uploadcare_get_file, uploadcare_get_file_metadata and 2 more); 1 tool brings in text other people can write (uploadcare_get_file).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Oct 25, 2026, version 1.40.4.
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.
11 tools
Deletes or cancels 4Claude Code: deny
uploadcare_create_webhookCreates a webhook subscription (additive).No findings
Why it is in this group
- The name "uploadcare_create_webhook" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Creates a webhook subscription (additive). The project will POST to target_url when the chosen event fires. REST API: POST /webhooks/.
Annotations the server declares
- title: Create webhook
- destructiveHint: true
uploadcare_delete_filePermanently deletes a file from the project.No findings
Why it is in this group
- The name "uploadcare_delete_file" says "delete": a word for removing or ending something.
- The description says "Permanently deletes".
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Permanently deletes a file from the project. Destructive. REST API: DELETE /files/{uuid}/.
Annotations the server declares
- title: Delete file
- destructiveHint: true
uploadcare_store_fileMarks a file as permanently stored (otherwise unstored files are deleted after 24h).No findings
Why it is in this group
- The name "uploadcare_store_file" says "store": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Marks a file as permanently stored (otherwise unstored files are deleted after 24h). Additive. REST API: PUT /files/{uuid}/storage/.
Annotations the server declares
- title: Store file
- destructiveHint: true
uploadcare_upload_from_urlUploads a file into the project from a public URL (additive).No findings
Why it is in this group
- The name "uploadcare_upload_from_url" says "upload": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Uploads a file into the project from a public URL (additive). Uses the Upload API host with the public key. Returns { type: "token", token } for async ingestion (poll separately) or the file info. Upload API: POST /from_url/.
Annotations the server declares
- title: Upload file from URL
- destructiveHint: true
Only reads 7Show 7 read-only tools
uploadcare_get_fileGet full info for a single file: uuid, url, original_filename, size, mime_type, is_image, is_ready, timestamps, variations, content_info, metadata, tags.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "uploadcare_get_file" says "get": a word for reading.
What it can reach
- private-dataThe name "uploadcare_get_file" says "get" and "file": it reads files.
- private-dataThe description's first sentence says "get" and "file": it reads files.
- untrusted-inputThe description's first sentence says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Get full info for a single file: uuid, url, original_filename, size, mime_type, is_image, is_ready, timestamps, variations, content_info, metadata, tags. REST API: GET /files/{uuid}/.
Annotations the server declares
- title: Get file
- readOnlyHint: true
uploadcare_get_file_metadataGet all custom metadata key/value pairs for a file.Reads private dataNo findings
Why it is in this group
- The name "uploadcare_get_file_metadata" says "get": a word for reading.
What it can reach
- private-dataThe name "uploadcare_get_file_metadata" says "get" and "file": it reads files.
- private-dataThe description's first sentence says "get" and "file": it reads files.
Description, as the server wrote it Get all custom metadata key/value pairs for a file. REST API: GET /files/{uuid}/metadata/.
Annotations the server declares
- title: Get file metadata
- readOnlyHint: true
uploadcare_get_groupGet info for a single file group by its id.Reads private dataNo findings
Why it is in this group
- The name "uploadcare_get_group" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "file": it reads files.
Description, as the server wrote it Get info for a single file group by its id. REST API: GET /groups/{uuid}/.
Annotations the server declares
- title: Get group
- readOnlyHint: true
uploadcare_get_projectGet project details: name, public key, collaborators, and whether autostore is enabled.No findings
Why it is in this group
- The name "uploadcare_get_project" says "get": a word for reading.
Description, as the server wrote it Get project details: name, public key, collaborators, and whether autostore is enabled. REST API: GET /project/.
Annotations the server declares
- title: Get project
- readOnlyHint: true
uploadcare_list_filesList files in the project (paginated envelope: next, previous, total, per_page, results).Reads private dataNo findings
Why it is in this group
- The name "uploadcare_list_files" says "list": a word for reading.
What it can reach
- private-dataThe name "uploadcare_list_files" says "list" and "file": it reads files.
- private-dataThe description's first sentence says "list" and "file": it reads files.
Description, as the server wrote it List files in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /files/.
Annotations the server declares
- title: List files
- readOnlyHint: true
uploadcare_list_groupsList file groups in the project (paginated envelope: next, previous, total, per_page, results).Reads private dataNo findings
Why it is in this group
- The name "uploadcare_list_groups" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "file": it reads files.
Description, as the server wrote it List file groups in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /groups/.
Annotations the server declares
- title: List groups
- readOnlyHint: true
uploadcare_list_webhooksList all webhook subscriptions configured for the project.No findings
Why it is in this group
- The name "uploadcare_list_webhooks" says "list": a word for reading.
Description, as the server wrote it List all webhook subscriptions configured for the project. REST API: GET /webhooks/.
Annotations the server declares
- title: List webhooks
- readOnlyHint: true
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 outbound.
- Reads private data5
- 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 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: The server redirected a POST to a different request.
Posture changes
- Oct 29, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://uploadcare.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://uploadcare.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://uploadcare.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://uploadcare.usefulapi.io to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: no to not observed
Install
Pinned to version 1.40.4. Values in angle brackets are yours to fill in.
claude mcp add --transport http uploadcare https://uploadcare.usefulapi.io/mcpclaude mcp add --transport http uploadcare https://uploadcare.usefulapi.io/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__uploadcare__uploadcare_get_project",
"mcp__uploadcare__uploadcare_list_files",
"mcp__uploadcare__uploadcare_get_file",
"mcp__uploadcare__uploadcare_get_file_metadata",
"mcp__uploadcare__uploadcare_list_groups",
"mcp__uploadcare__uploadcare_get_group",
"mcp__uploadcare__uploadcare_list_webhooks"
],
"ask": [],
"deny": [
"mcp__uploadcare__uploadcare_upload_from_url",
"mcp__uploadcare__uploadcare_store_file",
"mcp__uploadcare__uploadcare_delete_file",
"mcp__uploadcare__uploadcare_create_webhook"
]
}
}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 uploadcare. Review it before you use it.
Capability tags behind 5 rules
- mcp__uploadcare__uploadcare_list_files private-data
- mcp__uploadcare__uploadcare_get_file private-data, untrusted-input
- mcp__uploadcare__uploadcare_get_file_metadata private-data
- mcp__uploadcare__uploadcare_list_groups private-data
- mcp__uploadcare__uploadcare_get_group private-data
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.usefulapi/uploadcare/verify?hash=d18853a64e0c49423efa1c06fd2e74563e838a5d1d6df5ccbb0ef618270e631a" | jq -e '.changed == false'Pinned hash d18853a64e0c, from Oct 25, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.usefulapi/uploadcare/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.usefulapi/uploadcare)Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.
Uploadcare MCP by usefulapi: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Uploadcare MCP by usefulapi safe?
- No scan can promise that. What its definitions show: 11 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Uploadcare MCP by usefulapi delete data?
- Yes. 4 tools can delete, cancel or revoke something: uploadcare_upload_from_url, uploadcare_store_file, uploadcare_delete_file and uploadcare_create_webhook.
Can the Uploadcare MCP by usefulapi 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 Uploadcare MCP by usefulapi have?
- 11 tools: 4 destructive, 7 read. uploadcare_upload_from_url, uploadcare_store_file, uploadcare_delete_file, uploadcare_create_webhook, uploadcare_get_project, uploadcare_list_files, uploadcare_get_file, uploadcare_get_file_metadata and 3 more.
Does the Uploadcare MCP by usefulapi need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Uploadcare MCP by usefulapi send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Uploadcare MCP by usefulapi changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.