Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hum Internet Availability

REMOTE · MCP.LETSHUM.COM

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

Available components

0 this week 77 Trust /100

Last scanned (14 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Recent critical change

Authorization (21 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability75
  • 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
  • Context-footprint check failed: tool/resource definitions use about 1110 tokens (~185/item across 6 items; 4 tools + 2 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Endpoint reachability: unreachable → reachable ▲ functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Authorization: fail → unverified ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 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=YE1,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 ECDSA 256 ECDSA-SHA384 64a79c5453e5a0ce2ec10937c95b2a2c5c4
SANs: mcp.letshum.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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. DS published 19718 13 Verified
letshum.com. DS published 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
MCP tools · 4 exposed · ~805 tokens

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 →

Tool Tokens
check_availability ~184

Use this when someone asks what internet service or plans are available at a U.S. street address: providers, speeds and prices. U.S. addresses only; not for outages, speed tests or router troubleshooting. Start with {address}: the full street address, and include the apartment or unit in the address. Continue only with returned IDs: {candidate_id} (plus unit if asked) to pick an address, {lookup_id} to keep checking, or {lookup_id, question_set_id, answers}. Each call waits for live results; while status is checking, call again with lookup_id. Providers reported only in FCC area data were not checked at the address. Select only returned offer_id values.

NameTypeReqDescription
address–––
answers–––
candidate_id–––
lookup_id–––
question_set_id–––
unit–––
NameTypeReqDescription
candidates–––
clarification_type–––
error–––
expires_at–––
lookup_id–––
message–––
next_action–––
normalized_address–––
providers–––
question_set_id–––
questionsarray––
required_field–––
retry_after_seconds–––
revision–––
schema_versionintegeryes–
sources–––
statusstringyes–
warningsarray––

No examples provided.

create_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.

NameTypeReqDescription
checkout_idstringyes–
confirmation–yes–
idempotency_keystringyes–
validation_tokenstringyes–
NameTypeReqDescription
error–––
evidence–––
last_checked_at–––
next_action–––
order_id–––
provider_name–––
schema_versionintegeryes–
selected_offer_summary–––
statusstringyes–
submitted_at–––

No examples provided.

get_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.

NameTypeReqDescription
checkout_idstringyes–
NameTypeReqDescription
error–––
evidence–––
last_checked_at–––
next_action–––
order_id–––
provider_name–––
schema_versionintegeryes–
selected_offer_summary–––
statusstringyes–
submitted_at–––

No examples provided.

validate_order ~492

Start: {"lookup_id":"<returned lookup_id>","offer_id":"<returned offer_id>"}. Poll: {"checkout_id":"<returned checkout_id>"}. Edit: {"checkout_id":"<returned checkout_id>","expected_revision":<current revision>,"details":{<changed fields>}}. Use exactly one shape. Customer, installation, consents and internet_addons belong inside details, never at the root. Start a checkout only when the customer asks to order. Each call waits for progress; while checking, poll with checkout_id only. Edits restart validation. On stale expected_revision, retrieve with checkout_id only before editing at the current revision. required_fields defines the contract; field_errors identifies actual missing/invalid fields relative to details. Refreshes the offer and returns an exact review without submitting an order. 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. Match the customer's equipment preference using returned equipment_options and catalog facts. Customer-owned equipment, included provider equipment and optional paid equipment are different choices. A free provider gateway does not satisfy an own-equipment request. Price or included status alone does not establish ownership. If an offer lacks the requested option, inspect another qualified offer or explain the limitation and ask the customer to choose; never fabricate an option. Send the complete selection in details.internet_addons using returned option_id and quantity values. Omit it to preserve current/default selections; [] declines optional items. Select at most one radio option and retain dependent parents. Ready means technically valid, not necessarily correct for the customer. Compare the entire review with the customer's budget, speed, equipment, billing and installat…

NameTypeReqDescription
checkout_id–––
details–––
expected_revision–––
lookup_id–––
offer_id–––
NameTypeReqDescription
checkout_id–––
equipment_optionsarray––
error–––
expires_at–––
field_errorsobject––
next_action–––
required_fieldsarray––
retry_after_seconds–––
review–––
revision–––
schema_versionintegeryes–
statusstringyes–
terms_hash–––
validation_token–––

No examples provided.

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.

remote · mcp.letshum.com

# add to Claude Code
claude mcp add --transport http com-letshum-internet-availability 'https://mcp.letshum.com/mcp'
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 805 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Hum Internet Availability MCP server?

VerifyMCP ran 13 checks on Hum Internet Availability, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.