Qiniu MCP Server

qiniu-mcp-server PyPI v1.4.1

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A MCP server project of Qiniu.

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Unconstrained URL/host parameter "url" on "fetch_object"MTC-CAP-007

Tool "fetch_object" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool fetch_object · inputSchema.properties.url

Tools 24

Each tool and what it can reach — statically extracted from the published source.

  • cdn_prefetch_urlsingests untrusted input
  • cdn_refreshingests untrusted input
  • fetch_objectingests untrusted input
  • get_object_urlingests untrusted input
  • live_streaming_query_live_traffic_statsingests untrusted input
  • get_fop_statusno sensitive capability
  • get_objectno sensitive capability
  • image_infono sensitive capability
  • image_round_cornerno sensitive capability
  • image_scale_by_percentno sensitive capability
Show 14 more tools ↓
  • image_scale_by_sizeno sensitive capability
  • list_bucketsno sensitive capability
  • list_objectsno sensitive capability
  • live_streaming_bind_play_domainno sensitive capability
  • live_streaming_bind_push_domainno sensitive capability
  • live_streaming_create_bucketno sensitive capability
  • live_streaming_create_streamno sensitive capability
  • live_streaming_get_play_urlsno sensitive capability
  • live_streaming_get_push_urlsno sensitive capability
  • live_streaming_list_bucketsno sensitive capability
  • live_streaming_list_streamsno sensitive capability
  • upload_local_fileno sensitive capability
  • upload_text_datano sensitive capability
  • versionno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.4.1 latest A 95/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/qiniu-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/qiniu-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/qiniu-mcp-server"><img src="https://mcptrustchecker.com/registry/qiniu-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/qiniu-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan qiniu-mcp-server --online --registry pypi

Use the free API → How scoring works

More in AI, Memory & Reasoning