Repository navigation
Releases
v3.7.0
v3.6.1
Fixed
- The container installed its dependencies with
pip install ., which reads
onlypyproject.toml's floor-pins and resolves fresh at build time instead
of installing the committed, Dependabot-maintaineduv.lock. That let the
shipped image carry a dependency set no test had ever run against — the same
bug that took mcp-gemini down in production (google-genai3.0.0 shipped
vs. 2.34.0 CI actually tested; RT #1564). A newlockstage runs
uv export --frozento turnuv.lockinto a requirements file, and both the
locked requirements and the project itself install with--no-depsso pip
cannot re-resolve anything the lock already decided.
v3.6.0 — the callback read had no limit, and the error said nothing
RT #1601, the fleet's outbound HTTP contract. Two outbound paths here, and they needed different things.
The gather callback had no size limit at all. client.post read whatever answered on the alert URL whole into the process before raise_for_status() looked at it, so an SSO interstitial or a proxy error page on that URL was an unbounded read. It now streams under a 1MB cap, measured before each chunk is copied in.
A failed dispatch said nothing actionable. raise_for_status() names neither the URL nor the body — the RT #1596 shape. A failure now names the method, the requested endpoint, the status, the content-type and a bounded snippet, and a transport failure names the request too.
The URL an error names carries no credential. It comes from TRENTINA_ALERT_URL, so it holds whatever an operator configured. Review took three rounds to get this right, and the end state is: scheme, host, port and the final path segment — the one this module appends — and nothing else. The query, the fragment and the configured path segments are elided, because a by-name list of credential parameters misses api_key and client_secret, and a webhook URL whose path is the credential is an ordinary pattern.
Found while writing the test for that: /alert was concatenated onto the configured string, so it landed wherever that string happened to end. An alert URL with a query made the endpoint ?...=.../alert and the request went to / — silently. It goes in the path now.
The Trentina gateway is the other path, and its body is read inside fastmcp's own httpx2 client. What this code owns there is the header and the SSE event ceiling; both are now set explicitly and pinned by a test, so a fastmcp release that moves its default cannot move what this server accepts without a diff saying so.
Both paths send the same agent string, read from installed package metadata: mcp-metsuke-crunchtools/<version> (+<repo>).
Constitution pin v1.31.0 → v1.36.0.
v3.5.1
Security
- Upgraded locked dependencies within their declared ranges to clear the
advisories the fleet dependency audit found (authlib, certifi, dnspython, fastmcp, joserfc, opentelemetry-api, pyjwt).
v3.5.0
Added
jira_issuesrecords carrylabels, and a query can set
description: falseto skip the intake form, so the customer's free text
can't get a whole result flagged. The daily briefing builds its HUM groups
from labels.jira_issuesrecords carryupdated, Jira's last-update time, so the daily
briefing can list triaged HUM requests by when they were last triaged.nagios_healthreads scheduled downtime (mcp-nagios 0.8.0): each record
carriesin_downtime, the section's stats carryplanned_eventsand
planned_objects(problem events the roll-up set aside as planned) and
downtimes, the week's downtime windows from
nagios_downtime_history_toolwith times local and the comment withheld
when flagged. A failed downtime call marks the section partial and leaves
the rest.
Fixed
- A current problem in scheduled downtime no longer drops out of the
infrasection: the problems parser now accepts the ", in downtime"
suffix, which it failed to match. - The roll-up's checked total is read only from its header, so the
planned-events line can no longer be taken for it.
v3.4.0
Added
- Three sweep collectors for the weekend report, so its infrastructure,
inbox and release sections arrive as complete records instead of being
read by the gathering model through a judge that refuses them:
nagios_health(current problems, the week's roll-up and what paged, one
record per qualifying check with its status and history links encoded and
times local),ashigaru_issue(an Ashigaru record issue found by label,
every part parsed into items) andcrunchtools_releases(the releases
issue joined with what lotor runs, live/behind/not-deployed decided in
code). A flagged result keeps its structure and withholds plugin output
or contributor-written titles, as the other collectors do. crunchtools_releasesreads a container's version from the first of
org.opencontainers.image.versionandversionthat is a version: images
built from a branch carry "main" in the OCI label, which had made 13
deployed MCP servers read as not deployed.
Changed
- Container base images pinned to
quay.io/hummingbird/python:3.14*instead of
latest, which moved to Python 3.15.0 on 2026-10-20 (crunchtools/constitution#66).
v3.3.0 — pull owners
Reports owned by an agent in METSUKE_PULL_OWNERS are opened and swept on schedule, then left for that owner to collect. No callback is sent.
v3.2.0
Added
- The five tools that only read (
list_reports,get_spec,get_output,
list_outputs,get_sweep) publishreadOnlyHint: true. A gateway uses it
to decide whether an invalid optional argument may be dropped or must refuse
the call (crunchtools/constitution#35). - Tests pin every registered tool into
READ_ONLYorWRITES, and check that
no read-only tool inserts, updates or deletes a row or opens an HTTP client.
Changed
- Inherits constitution v1.22.0; the workflow pins and the pre-commit hook rev
(which sat on v1.6.0) move with it.
v2.2.0 — jira_issues sweep collector
Added
-
jira_issuescollector. Runs up to six named JQL queries per sweep, with
{since}substituted by the sweep window's start as a JQL datetime in the
window's zone, socreated >= "{since}"reads "since the last report". A
query without the placeholder is sent unchanged, which is how a still-open
list reaches past the window.Each issue becomes a fixed-shape record: key, browse link, issue type,
status, components, created,age_days. Where an issue was filed by a web
intake form, the description's flatField: valuepairs are parsed into a
contactblock and one cappeddetailline — first occurrence of a name
wins, so trailing free text cannot overwrite a structured answer. A
hand-filed ticket parses to nothing and still renders from its summary.Queries run in order and share one 100-record budget. A query that fails is
recorded and the rest still run. A flagged result keeps only the fields the
collector generated or that come from a controlled vocabulary, withholding
summary,detailandcontact— an intake form carries a stranger's prose.The sweep profile must grant the Jira backend
jira_search; no write tool is
reachable from a sweep.
Spec: .specify/specs/003-jira-collector/spec.md
v1.1.0
The gather callback carries gather_prompt and source_config with report and run_id (RT #1505). See CHANGELOG.md.