Hum Internet Availability
REMOTE · MCP.LETSHUM.COM · SCANNED SEP 24
Check internet providers, plans, speeds, and known pricing at a specific U.S. street address.
Available components
Recent critical change
Authorization (21 Sept 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_order). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 612 tokens (~102/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.letshum.com
claude mcp add --transport http com-letshum-internet-availability 'https://mcp.letshum.com/mcp'
{
"mcpServers": {
"com-letshum-internet-availability": {
"url": "https://mcp.letshum.com/mcp"
}
}
} {
"servers": {
"com-letshum-internet-availability": {
"type": "http",
"url": "https://mcp.letshum.com/mcp"
}
}
} [mcp_servers.com-letshum-internet-availability] url = "https://mcp.letshum.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-letshum-internet-availability": {
"type": "remote",
"url": "https://mcp.letshum.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-letshum-internet-availability --url 'https://mcp.letshum.com/mcp' --transport streamable-http
mcp_servers:
com-letshum-internet-availability:
url: "https://mcp.letshum.com/mcp" {
"McpServers": {
"com-letshum-internet-availability": {
"Transport": "http",
"Url": "https://mcp.letshum.com/mcp"
}
}
} assistant mcp add com-letshum-internet-availability -t streamable-http -u 'https://mcp.letshum.com/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +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.
- 22 Sept 26 0
- Tool “validate_order” rewrote its description, which is the text the model reads security
- Schema quality: 87 → 102 ▼ functional
- 21 Sept 26 −9
- Authorization: partial → fail ▼ critical
- 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 security
- Tool coverage: 100% → 0% ▼ functional
- 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” functional
- “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 cosmetic
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.letshum.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.letshum.com | CN=YE2,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6c8e8f2392814fdcef3da96723bdc14d529 |
| SANs: mcp.letshum.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.letshum.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| letshum.com. | present | 2371 | 13 | Verified |
| mcp.letshum.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.letshum.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.letshum.com/mcp | HTTPS enforced | 301 | https://mcp.letshum.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_availability Check broadband availability ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| answers | – | – | – |
| candidate_id | – | – | – |
| lookup_id | – | – | – |
| question_set_id | – | – | – |
| unit | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| sources | – | – | – |
| status | string | yes | – |
| warnings | array | – | – |
No examples provided.
create_order Create internet order ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| confirmation | – | yes | – |
| idempotency_key | string | yes | – |
| validation_token | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| evidence | – | – | – |
| last_checked_at | – | – | – |
| next_action | – | – | – |
| order_id | – | – | – |
| provider_name | – | – | – |
| schema_version | integer | yes | – |
| selected_offer_summary | – | – | – |
| status | string | yes | – |
| submitted_at | – | – | – |
No examples provided.
get_order Get internet order ~45
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| error | – | – | – |
| evidence | – | – | – |
| last_checked_at | – | – | – |
| next_action | – | – | – |
| order_id | – | – | – |
| provider_name | – | – | – |
| schema_version | integer | yes | – |
| selected_offer_summary | – | – | – |
| status | string | yes | – |
| submitted_at | – | – | – |
No examples provided.
validate_order Validate internet order ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | – | – | – |
| details | – | – | – |
| expected_revision | – | – | – |
| lookup_id | – | – | – |
| offer_id | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checkout_id | – | – | – |
| equipment_options | array | – | – |
| error | – | – | – |
| expires_at | – | – | – |
| field_errors | object | – | – |
| next_action | – | – | – |
| required_fields | array | – | – |
| retry_after_seconds | – | – | – |
| review | – | – | – |
| revision | – | – | – |
| schema_version | integer | yes | – |
| status | string | yes | – |
| terms_hash | – | – | – |
| validation_token | – | – | – |
No examples provided.
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.