Skip to content

v0.3.1 — published to the official MCP registry

Choose a tag to compare

View all tags
@musharna musharna released this 31 Jul 04:11
v0.3.1
2d3ab2a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Published to the official MCP registry via server.json and a GitHub Actions OIDC workflow, so this server is discoverable from MCP clients and directories rather than only from PyPI.

Why this needed a release

The registry proves PyPI ownership by finding an mcp-name: <server-name> marker in the package README as published to PyPI — and PyPI captures long_description at release time. A marker sitting on the default branch verifies nothing, so registering required a version that carries it.

Guarding it

tests/test_registry_metadata.py asserts what would otherwise only fail during a release, after the version is spent:

  • server.json states the version in three places, with nothing else making them agree with pyproject.toml
  • the README marker must match the name server.json declares — that exact string is what the registry greps for
  • the declared transport is stdio, which is what this server implements

All three were confirmed red against mutants before being kept.

Running the real mcp-publisher validate also caught a constraint no schema read surfaced: description is capped at 100 characters. That would otherwise have failed the publish after the version was already on PyPI and unreclaimable, so the workflow now validates before authenticating.

No functional change.

Assets 2
Loading