Yumi PyPI Wheel Evidence MCP server
site.chatgpt.no-qt.noqt/yumi-pypi-wheel-evidencenoqt.no-qt.chatgpt.sitestreamable-httpv1.0.0Scanned
Batch PyPI wheel filenames and reported metadata; no downloads or compatibility checks.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- 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 Yumi PyPI Wheel Evidence MCP server can do
The Yumi PyPI Wheel Evidence MCP server is published by noqt.no-qt.chatgpt.site, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: pypi_wheel_evidence, network_set_evidence and python_import_layout_evidence), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (pypi_wheel_evidence and python_import_layout_evidence).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 21, 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
Changes things 3Claude Code: ask
network_set_evidenceCompares two bounded IPv4 and IPv6 CIDR sets.1 finding
Why it is in this group
- The name "network_set_evidence" says "set": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "network_set_evidence" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "network_set_evidence" says "set": a word for a change.
Description, as the server wrote it Compares two bounded IPv4 and IPv6 CIDR sets. before contains included ranges and after supplies the second set. For subtraction, put ranges to exclude in after and read removed for before minus after. added is after minus before. Reports canonical CIDR ranges, address counts, and witnesses. Address counts are exact decimal strings. Keep them as strings for display and use BigInt for arithmetic. A failed comparison is unavailable, not zero. A successful response can contain more CIDRs than a request accepts or include IPv4-mapped IPv6 ranges that requests reject. To reproduce a comparison, replay its original public before and after arrays. For a derived comparison with refused or oversized ranges, compare locally without dropping ranges. It does not assess reachability, routing, security policy, configuration, or host usability.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pypi_wheel_evidenceReports provider-reported filename/tag intersection for PyPI wheels; it does not perform compatibility, security, or digest verification.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Reports provider-reported filename/tag intersection for PyPI wheels; it does not perform compatibility, security, or digest verification.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
python_import_layout_evidenceCompares one exact PyPI artifact with public GitHub Python source and named consumer files pinned by a full commit or a caller-selected tag ref.Reads text others write1 finding
Why it is in this group
- The name "python_import_layout_evidence" says "import": a word for a change.
- The server marks it read-only (readOnlyHint: true), 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 "python_import_layout_evidence" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "python_import_layout_evidence" says "import": a word for a change.
Description, as the server wrote it Compares one exact PyPI artifact with public GitHub Python source and named consumer files pinned by a full commit or a caller-selected tag ref. Tag refs are resolved and rechecked before full-SHA static reads; results retain the original ref and resolved SHA, and unknown or ambiguous cases stay UNKNOWN.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: 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 private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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:31 UTC, unchanged since Nov 20, 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
- 3
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://noqt.no-qt.chatgpt.site/api/yumi/mcp: tools/list returned 3 tools to an anonymous client, including pypi_wheel_evidence (write), network_set_evidence (write), python_import_layout_evidence (write)
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
The server marks "network_set_evidence" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "network_set_evidence" says "set": a word for a change.
The server marks "python_import_layout_evidence" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "python_import_layout_evidence" says "import": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:python_import_layout_evidenceChanges things
- Changed:network_set_evidenceChanges thingstitledescriptioninputSchema
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http yumi-pypi-wheel-evidence https://noqt.no-qt.chatgpt.site/api/yumi/mcpclaude mcp add --transport http yumi-pypi-wheel-evidence https://noqt.no-qt.chatgpt.site/api/yumi/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": [],
"ask": [
"mcp__yumi-pypi-wheel-evidence__pypi_wheel_evidence",
"mcp__yumi-pypi-wheel-evidence__network_set_evidence",
"mcp__yumi-pypi-wheel-evidence__python_import_layout_evidence"
],
"deny": []
}
}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 yumi-pypi-wheel-evidence. Review it before you use it.
Capability tags behind 2 rules
- mcp__yumi-pypi-wheel-evidence__pypi_wheel_evidence untrusted-input
- mcp__yumi-pypi-wheel-evidence__python_import_layout_evidence 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/site.chatgpt.no-qt.noqt/yumi-pypi-wheel-evidence/verify?hash=8adc56e9a993c011faa56b0234b0950524745f294e348c3fb4b3ef3fee30272a" | jq -e '.changed == false'Pinned hash 8adc56e9a993, from Nov 21, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/site.chatgpt.no-qt.noqt/yumi-pypi-wheel-evidence/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/site.chatgpt.no-qt.noqt/yumi-pypi-wheel-evidence)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
Yumi PyPI Wheel Evidence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Yumi PyPI Wheel Evidence MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 2 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 Yumi PyPI Wheel Evidence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Yumi PyPI Wheel Evidence 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 Yumi PyPI Wheel Evidence MCP server have?
- 3 tools: 3 write. pypi_wheel_evidence, network_set_evidence and python_import_layout_evidence.
Does the Yumi PyPI Wheel Evidence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Yumi PyPI Wheel Evidence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Yumi PyPI Wheel Evidence MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.