Skip to content

v0.1.2

Choose a tag to compare

@malkreide malkreide released this 31 Jul 15:39
1d2afe9

[0.1.2] — 2026-07-30

Fixed

  • The User-Agent reports the actual package version again. The published
    0.1.1 sent termdat-mcp/0.1.0 to every upstream — the version string was
    hardcoded and had been left behind by earlier bumps. The version now comes
    from the package metadata, so it can no longer drift from the package.

Documented

  • The public API exposes less than the website — a coverage limit of the
    source, not a scope setting on our side. Follow-up to #11: @dfch supplied the
    12 entry IDs the website lists for «Quellensteuer»; the API returns 7 at
    maximum recall (every language, all 11 fields, infix wildcard, all
    classifications and collections), and the two sets overlap in exactly one
    entry, 447912. Fetching the missing IDs directly via /v2/Entry returns
    HTTP 200 with an empty body — they are not served at all, so no query can
    reach them. The one exception, 1557, is served but carries status
    In Bearbeitung in a collection marked «(aufgehoben)», which suggests the
    search index covers validated entries while the website also shows drafts and
    repealed material.

    This corrects an earlier guess. The residual was described in #11 as probably
    a counting difference — the website listing designations where the API counts
    entries. The IDs disprove that: they are twelve distinct entries. Recorded
    here so the wrong explanation does not outlive the measurement.

    Documented in both READMEs, and in the search_terms docstring, where it
    matters most: a model told only that «a term may genuinely be absent» will
    conclude «absent from TERMDAT», which is false for entries the website shows.
    The docstring now distinguishes the two.

Fixed

  • Capped mcp at <2. mcp 2.0.0, published 2026-07-28, removed
    mcp.server.fastmcp — the module this server imports. With the previous
    unbounded >=1.28.1 every fresh resolve picked 2.0.0 and failed at import
    with ModuleNotFoundError, in CI and for anyone running pip install alike.
    Verified in both directions: 2.0.0 fails, <2 resolves to 1.29.0 and imports
    cleanly. Migrating to the 2.x API (mcp.server.mcpserver) stays a separate,
    deliberate piece of work.