Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.usefulapi/uploadcare

REMOTE · UPLOADCARE.USEFULAPI.IO · SCANNED SEP 20

Manage Uploadcare files, groups and webhooks; upload and store files.

Available components

remote · uploadcare.usefulapi.io 73
+55 this week 73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 758 tokens (~68/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.usefulapi/uploadcare MCP server?

io.usefulapi/uploadcare is a hosted endpoint at https://uploadcare.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · uploadcare.usefulapi.io

# add to Claude Code
claude mcp add --transport http io-usefulapi-uploadcare 'https://uploadcare.usefulapi.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "io-usefulapi-uploadcare": {
      "url": "https://uploadcare.usefulapi.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-usefulapi-uploadcare": {
      "type": "http",
      "url": "https://uploadcare.usefulapi.io/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.io-usefulapi-uploadcare]
url = "https://uploadcare.usefulapi.io/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-uploadcare": {
      "type": "remote",
      "url": "https://uploadcare.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-usefulapi-uploadcare --url 'https://uploadcare.usefulapi.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  io-usefulapi-uploadcare:
    url: "https://uploadcare.usefulapi.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-usefulapi-uploadcare": {
      "Transport": "http",
      "Url": "https://uploadcare.usefulapi.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add io-usefulapi-uploadcare -t streamable-http -u 'https://uploadcare.usefulapi.io/mcp'
// mcp.json
{
  "mcpServers": {
    "io-usefulapi-uploadcare": {
      "type": "http",
      "url": "https://uploadcare.usefulapi.io/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 18 Sept 26 +54
    • Authorization: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Destructive annotations: 100 functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: pass → unverified ▼ security
    • Stability: 0.20 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 2 Aug 26 0
    • Authorization: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.20 ▲ functional
  • 1 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.13 → unverified ▼ security
    • Authorization: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://uploadcare.usefulapi.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=usefulapi.io CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 ccc61b1f9a359c560e66c6b8c23760df
SANs: usefulapi.io, uploadcare.usefulapi.io, *.uploadcare.usefulapi.io
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of uploadcare.usefulapi.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
usefulapi.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://uploadcare.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token" 

Bearer realm="OAuth", resource_metadata="https://uploadcare.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"

Protected resource metadata

Document https://uploadcare.usefulapi.io/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://uploadcare.usefulapi.io/mcp
Authorisation server https://uploadcare.usefulapi.io

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://uploadcare.usefulapi.io/mcp Verified 200
http (plaintext) http://uploadcare.usefulapi.io/mcp Inconclusive 401
MCP tools · 11 exposed · ~758 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
uploadcare_create_webhook ~87

Creates a webhook subscription (additive). The project will POST to target_url when the chosen event fires. REST API: POST /webhooks/.

NameTypeReqDescription
eventstring–Event to subscribe to. Default "file.uploaded".
is_activeboolean–Whether the webhook is active. Default true.
target_urlstringyesURL the webhook will POST to.

No output schema declared.

No examples provided.

uploadcare_delete_file ~43

Permanently deletes a file from the project. Destructive. REST API: DELETE /files/{uuid}/.

NameTypeReqDescription
uuidstringyesFile UUID to delete.

No output schema declared.

No examples provided.

uploadcare_get_file ~66

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}/.

NameTypeReqDescription
uuidstringyesFile UUID.

No output schema declared.

No examples provided.

uploadcare_get_file_metadata ~42

Get all custom metadata key/value pairs for a file. REST API: GET /files/{uuid}/metadata/.

NameTypeReqDescription
uuidstringyesFile UUID.

No output schema declared.

No examples provided.

uploadcare_get_group ~63

Get info for a single file group by its id. REST API: GET /groups/{uuid}/.

NameTypeReqDescription
uuidstringyesGroup id in the form "<uuid>~<count>", e.g. "badfc9f7-...~2".

No output schema declared.

No examples provided.

uploadcare_get_project ~36

Get project details: name, public key, collaborators, and whether autostore is enabled. REST API: GET /project/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

uploadcare_list_files ~136

List files in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /files/.

NameTypeReqDescription
fromstring–Pagination cursor taken from a previous response's `next` URL.
limitinteger–Files per page (max 1000). Default 100.
orderingstring–Sort order, e.g. datetime_uploaded or -datetime_uploaded (descending).
removedboolean–Filter by removed status (true = removed, false = present).
storedboolean–Filter by stored status (true = stored, false = not stored).

No output schema declared.

No examples provided.

uploadcare_list_groups ~79

List file groups in the project (paginated envelope: next, previous, total, per_page, results). REST API: GET /groups/.

NameTypeReqDescription
limitinteger–Groups per page (max 1000). Default 100.
orderingstring–Sort order, e.g. datetime_created or -datetime_created (descending).

No output schema declared.

No examples provided.

uploadcare_list_webhooks ~28

List all webhook subscriptions configured for the project. REST API: GET /webhooks/.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

uploadcare_store_file ~53

Marks a file as permanently stored (otherwise unstored files are deleted after 24h). Additive. REST API: PUT /files/{uuid}/storage/.

NameTypeReqDescription
uuidstringyesFile UUID to store.

No output schema declared.

No examples provided.

uploadcare_upload_from_url ~125

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/.

NameTypeReqDescription
filenamestring–Override the stored filename.
source_urlstringyesPublic URL of the file to ingest.
storestring–Store the file: "1" = store, "0" = don't store, "auto" = project default. Default "auto".

No output schema declared.

No examples provided.

Common questions

What is the io.usefulapi/uploadcare MCP server?

io.usefulapi/uploadcare is an MCP server listed in the public MCP registry as io.usefulapi/uploadcare. Manage Uploadcare files, groups and webhooks; upload and store files. This page covers its hosted endpoint (https://uploadcare.usefulapi.io/mcp).

Is the io.usefulapi/uploadcare MCP server safe to use?

io.usefulapi/uploadcare scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.usefulapi/uploadcare MCP server expose?

io.usefulapi/uploadcare exposes 11 tools: uploadcare_get_project, uploadcare_list_files, uploadcare_get_file, uploadcare_get_file_metadata, uploadcare_list_groups, and 6 more. Their descriptions and schemas cost roughly 758 tokens of context every time the server is loaded.

Does the io.usefulapi/uploadcare MCP server require authentication?

Yes. io.usefulapi/uploadcare asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the io.usefulapi/uploadcare MCP server still maintained?

io.usefulapi/uploadcare is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.