Repository navigation
Input caps, Azure DevOps, wire-format DNS, plain vendor text
- Breaking:
devops_watch_stacksaves no stacks over HTTP withMCP_AUTH_MODE=none(vendors_required), rejects over 20 saved vendors (stack_too_large);DEVOPS_STATUS_CERT_TIMEOUT_MS(1000–15000) andDEVOPS_STATUS_DNS_TIMEOUT_MS(1000–10000) are validated at startup;invalid_domainis removed from the probe tools (#60, #66, #68, #69) azure-devopsvendor, andsendgridscoped to its own components on Twilio's status page, viacomponent_scope_prefix(#54, #56)- Vendor update bodies converted to plain text on every backend; vendor text in
content[]escaped (#63) groupon status components, matched bycomponent_filterand shown asGroup / Leaf(#62)devops_check_dnsqueries resolvers over the DNS wire protocol and readsCAAandSOA; record values escaped (#64, #70, #75)devops_check_certsanddevops_check_dnsaccept URLs,host:port, and Unicode names; certs send SNI, retry legacy TLS, and inspect non-HTTP TLS ports (#65, #68)devops_get_incidentsgainsuntil,match,full_updates, and a 64,000-byte response budget (#58, #71)- Batches and output bounds served at the cap with
deferred_*fields and anotice(#69) - Status-fetch cache and upstream response bodies size-bounded (#67)
- Follow-ups:
devops_list_vendorsempty-resultnotice,devops_suggest_actionroutes unregistered vendors todevops_list_vendors(#72, #73) - deps:
@cyanheads/mcp-ts-core^0.13.14 → ^0.13.15 (+ zod, @types/node, Bun 1.4.3)
CHANGELOG v0.10.0 · release PR #76