Skip to content

Releases

v0.1.5 — the release the registry would accept

Choose a tag to compare

@jiawei686 jiawei686 released this 20 Sep 04:50

0.1.5 — the release the registry would accept

The release that makes the registry entry submittable. 0.1.4 could not be: the registry proves
ownership of a PyPI package by finding a marker line in the package's README, and a published PyPI
description cannot be edited, so the marker had to arrive with a new version.

Added

  • mcp-name: io.github.jiawei686/jev-ultrafast-mcp in README.md — the line the registry looks
    for to prove the package is ours. It is hidden in an HTML comment, which is the form the registry
    documents for PyPI (and which crates.io strips, hence the note there). tests/test_docs.py asserts
    it matches name in server.json, because a validator's token is invisible to a reader and fatal
    to forget.
  • The MCP registry entry is submitted by the release workflow —
    .github/workflows/registry.yml, which publish.yml calls with
    needs: publish. It authenticates over GitHub OIDC (mcp-publisher login github-oidc), so the
    namespace is proved by the workflow's own identity and there is no token to store. It is a separate
    workflow rather than a job so it can be dispatched on its own: a job that only exists on a tag push
    can only be tested by cutting a release, and the registry — still in preview, and warning about
    data resets — is exactly the thing that needs re-submitting without one. It runs
    mcp-publisher validate before publishing, which is the only place the registry's real limits are
    enforced.

Fixed

  • server.json's description was over the registry's limit, so the entry would have been
    rejected.
    The registry caps description at 100 characters and answers with 422 expected length <= 100; the file carried 309 — a paragraph written for a README, in a field that stores one
    sentence. mcp-publisher validate against the live service is what found it, and
    tests/test_docs.py now asserts the caps so a local pytest catches it first. The replacement is
    capability-focused, which is what the schema asks for: "Hand browser work off to a server-side
    agent: read the page as a table, act, then verify."
  • Both READMEs said the registry submission was "the step still outstanding". It is wired to happen
    on every tag now, so they say that instead of describing a manual step nobody had run.
  • The registry rejected the submission for a missing marker, which only a real submission could
    reveal.
    mcp-publisher validate checks the schema and passed; publish then failed with
    400 ... must appear as 'mcp-name: io.github.jiawei686/jev-ultrafast-mcp' in the package README,
    because ownership is verified against the published description and not the file. The workflow
    and the marker are the two halves of that fix, and neither was visible from inside the repository.

Install: uvx jev-ultrafast-mcp · pip install jev-ultrafast-mcp

Package: https://pypi.org/project/jev-ultrafast-mcp/