# Hum Internet Availability (remote · mcp.letshum.com)

Check internet providers, plans, speeds, and known pricing at a specific U.S. street address.

- Trust score: 77/100 (medium)
- Change this week: −7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

> **Recent critical change**: Authorization (2026-09-21). See the changelog below before you install this server.

## Components

- remote · `mcp.letshum.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-letshum-internet-availability/mcp.md), [page](https://verifymcp.io/servers/com-letshum-internet-availability/mcp)

## Channel facts

- Endpoint: `https://mcp.letshum.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_order).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 612 tokens (~102/item across 6 items; 4 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hum Internet Availability MCP server?

Hum Internet Availability is a hosted endpoint at https://mcp.letshum.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-letshum-internet-availability 'https://mcp.letshum.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-letshum-internet-availability": {
      "url": "https://mcp.letshum.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-letshum-internet-availability": {
      "type": "http",
      "url": "https://mcp.letshum.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-letshum-internet-availability]
url = "https://mcp.letshum.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-letshum-internet-availability": {
      "type": "remote",
      "url": "https://mcp.letshum.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-letshum-internet-availability --url 'https://mcp.letshum.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-letshum-internet-availability:
    url: "https://mcp.letshum.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-letshum-internet-availability": {
      "Transport": "http",
      "Url": "https://mcp.letshum.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-letshum-internet-availability -t streamable-http -u 'https://mcp.letshum.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-letshum-internet-availability": {
      "type": "http",
      "url": "https://mcp.letshum.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-23 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 76, 0)

- [security] Tool “validate_order” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 87 → 102

### 2026-09-21 (score 76, −9)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] The server changed its declared name: com.letshum/internet-availability → com.letshum/broadband
- [security] New tool “create_order”, which the server declares destructive
- [security] Tool “check_availability” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 100% → 0%
- [functional improvement] Schema quality: 119 → 87
- [functional] New resource “order-internet-service”
- [functional] Server version: 1.3.0 → 2.0.1
- [functional] New tool “get_order”
- [functional] New tool “validate_order”
- [cosmetic] “check_availability” added an optional parameter “answers”
- [cosmetic] “check_availability” added an optional parameter “candidate_id”
- [cosmetic] “check_availability” added an optional parameter “lookup_id”
- [cosmetic] “check_availability” added an optional parameter “question_set_id”
- [cosmetic] “check_availability” reworded the description of “address”
- [cosmetic] “check_availability” reworded the description of “unit”
- [cosmetic] “check_availability” dropped the optional parameter “candidateId”
- [cosmetic] “check_availability” dropped the optional parameter “lookupId”
- [cosmetic] Tool “check_availability” changed its title: Check internet availability → Check broadband availability

### 2026-09-19 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `check_availability` (~90 tokens)

Check broadband availability

Start with {address}; continue only with a returned candidate_id and requested unit, {lookup_id} to poll, or the current question_set_id and answers. FCC findings are area-level evidence. Select only returned executable offer_id values.

Input parameters:

- `address`
- `answers`
- `candidate_id`
- `lookup_id`
- `question_set_id`
- `unit`

Output parameters:

- `candidates`
- `clarification_type`
- `error`
- `expires_at`
- `lookup_id`
- `message`
- `next_action`
- `normalized_address`
- `providers`
- `question_set_id`
- `questions` (array)
- `required_field`
- `retry_after_seconds`
- `revision`
- `schema_version` (integer)
- `sources`
- `status` (string)
- `warnings` (array)

### `validate_order` (~193 tokens)

Validate internet order

Start with {lookup_id, offer_id}; resume with checkout_id, adding the exact expected_revision and requested details when required. Refreshes the offer and returns the exact review without creating an order or contacting fulfillment. When preferred installation dates are required, provide both first and second choices using a time_window value allowed by the input schema. Installation type must be self or professional. Record the customer's explicit true or false choices for auto-pay and paperless billing; never enable them silently. Present equipment_options and submit the complete internet_addons selection using returned option_id values and quantities. Omit internet_addons to keep the selection; send [] to decline optional equipment. A radio group allows one choice; dependent options appear after choosing their parent. Review all equipment charges and bundle discounts before confirmation.

Input parameters:

- `checkout_id`
- `details`
- `expected_revision`
- `lookup_id`
- `offer_id`

Output parameters:

- `checkout_id`
- `equipment_options` (array)
- `error`
- `expires_at`
- `field_errors` (object)
- `next_action`
- `required_fields` (array)
- `retry_after_seconds`
- `review`
- `revision`
- `schema_version` (integer)
- `status` (string)
- `terms_hash`
- `validation_token`

### `create_order` (~84 tokens)

Create internet order

Only after presenting the current review and obtaining authorization for its terms_hash, commit with its validation_token and one stable idempotency_key. After a lost or uncertain response, call get_order first; do not blindly resubmit.

Input parameters:

- `checkout_id` (string, required)
- `confirmation` (required)
- `idempotency_key` (string, required)
- `validation_token` (string, required)

Output parameters:

- `error`
- `evidence`
- `last_checked_at`
- `next_action`
- `order_id`
- `provider_name`
- `schema_version` (integer)
- `selected_offer_summary`
- `status` (string)
- `submitted_at`

### `get_order` (~45 tokens)

Get internet order

Retrieve recorded fulfillment evidence with checkout_id, especially after a lost or uncertain create_order response. Public statuses do not prove ISP acceptance or installation confirmation.

Input parameters:

- `checkout_id` (string, required)

Output parameters:

- `error`
- `evidence`
- `last_checked_at`
- `next_action`
- `order_id`
- `provider_name`
- `schema_version` (integer)
- `selected_offer_summary`
- `status` (string)
- `submitted_at`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-letshum-internet-availability/mcp#diagnostics

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 83
- 2026-09-15: 83
- 2026-09-14: 83
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 76
- 2026-08-29: 74
- 2026-08-28: 73
- 2026-08-27: 73

## Common questions

### What is the Hum Internet Availability MCP server?

Hum Internet Availability is an MCP server listed in the public MCP registry as com.letshum/internet-availability. Check internet providers, plans, speeds, and known pricing at a specific U.S. street address. This page covers its hosted endpoint (https://mcp.letshum.com/mcp).

### Is the Hum Internet Availability MCP server safe to use?

Hum Internet Availability scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Hum Internet Availability MCP server expose?

Hum Internet Availability exposes 4 tools: check_availability, validate_order, create_order, get_order. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

### Does the Hum Internet Availability MCP server require authentication?

No. We connected to Hum Internet Availability without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Hum Internet Availability MCP server still maintained?

Hum Internet Availability is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.letshum.com/mcp
- Website: https://letshum.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-letshum-internet-availability/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-letshum-internet-availability/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-letshum-internet-availability/mcp