Yumi Wheel Evidence

site.chatgpt.no-qt.noqtv1.0.0Updated Oct 26, 2026

Batch PyPI wheel filenames and reported metadata; no downloads or compatibility checks.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that takes batches of PyPI wheel filenames and returns reported metadata, without downloading files or checking compatibility.

What you can do
  • Submit batches of PyPI wheel filenames for lookup.
  • Receive the metadata reported for those wheels.
  • No file downloads and no compatibility checks are performed, so results are limited to reported metadata.
When to use it
Useful when you have a list of wheel filenames and want their reported metadata in bulk, for example while auditing or cataloguing Python packages. Not suitable when you need the actual files or a verdict on whether a wheel installs on a given platform.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared, and no authentication is declared.
Before you install
The endpoint is third-party hosted and the manifest declares no authentication, so treat submitted filenames as visible to that operator. Metadata is only as reported and is not verified by downloads or compatibility checks.

Installation

In SourceWeft

  1. Open Yumi Wheel Evidence in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/site.chatgpt.no-qt.noqt%2Fyumi-wheel-evidence/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "yumi-wheel-evidence": {
      "type": "http",
      "url": "https://noqt.no-qt.chatgpt.site/api/yumi/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 18, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.