Skip to main content

​
Releases and migration

Hum Broadband MCP 2.0.1 adds live qualification, order validation, authorized submission, and retrieval at Hum’s stable MCP endpoint. This release replaces the earlier availability-only schema at that endpoint.

​
Version 2.0.1

The public contract and examples are frozen to letshum/hum-mcp commit 96eaeeaa6714010338822bf06b1d0f35b8a332f8 on September 20, 2026. Harmony-backed example fixtures are verified against letshum/harmony commit 440becb1df0c64afa2c908ba674b0ff00fe695d3. Version 2.0.1 makes the mailing-address choice explicit and aligns the server-owned fulfillment payload with the selected offer. The public payload schema remains version 4. The server version identifies the connector release. schema_version identifies the payload contract. They use separate version numbers and should not be compared as if they were the same sequence.

​
Availability-only clients

There is one public endpoint. It reports com.letshum/broadband, exposes all four tools, and uses schema version 4 with snake_case fields. /mcp/v2 is not a released endpoint. The shorter availability skill remains available for clients that only use check_availability: Version 2.0.0 of that skill describes the availability portion of schema version 4. It does not preserve the earlier schema-version 3 payload or camelCase field names. Load the ordering skill before calling validate_order, create_order, or get_order.

​
Released lifetimes

Availability and validation work can run for up to 90 seconds per attempt. Poll after the delay in the current response. These values are freshness and access limits; they do not reserve provider inventory or guarantee a price.

​
Schema 3 to schema 4

The stable URL does not imply payload compatibility. Update schema-3 clients before reconnecting them to /mcp, including field names, status handling, continuation shapes, and order safety rules.

​
Migration steps

  1. Test the schema-version 4 server at the stable endpoint before replacing a production client connection.
  2. Confirm discovery returns the four tools and schema version 4.
  3. Load skill://order-internet-service/SKILL.md, or verify that the client can follow the tool descriptions without it.
  4. Update field access from camelCase to snake_case.
  5. Preserve separate FCC and live-source states and support typed question continuations.
  6. Treat catalog plans as informational and select only exact returned executable offer IDs.
  7. Add non-committing validation and exact-review authorization before submission.
  8. Persist the checkout ID and stable idempotency identity so a lost create response can be recovered through get_order.
  9. Present the six fulfillment states as Hum submission evidence, not ISP acceptance or installation status.
  10. Complete the testing checklist before enabling the updated connection for users.

​
Skill migration

Both skills use the same canonical Markdown, digest, MCP resource, and fixed HTTP delivery mechanism. Use order-internet-service for the complete schema-version 4 workflow. Keep check-internet-availability when a client only needs discovery. Both skills use snake_case fields at /mcp; the shorter skill directs transactional clients to the broader manual. This release does not change Hum’s partner REST API or widget contract. The partner API still does not expose order placement, and its analytics states do not map directly to MCP fulfillment states.