Skip to content

Hum Internet Availability MCP server

com.letshum/internet-availabilityletshum.comstreamable-httpv1.3.0Scanned

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

4 tools: 1 can delete or cancel things, 2 change things and 1 only read.

Tools: 1 delete, 0 irreversible, 2 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 4
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Hum Internet Availability MCP server can do

The Hum Internet Availability MCP server is published by letshum.com, a domain the MCP Registry verified. It has 4 tools. It can delete or cancel things (1 tool: create_order) and create or change data (2 tools: check_availability and validate_order). 1 tool only reads.

4 tools bring in text other people can write (check_availability, validate_order, create_order and 1 more).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.3.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Deletes or cancels 1Claude Code: deny
  • create_orderOnly after presenting the current review and obtaining authorization for its terms_hash, commit with its validation_token and one stable idempotency_key.Reads text others writeNo findings

    Why it is in this group

    • The name "create_order" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
Changes things 2Claude Code: ask
  • check_availabilityUse this when someone asks what internet service or plans are available at a U.S.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
  • validate_orderStart: {"lookup_id":"<returned lookup_id>","offer_id":"<returned offer_id>"}.Reads text others write1 finding

    Why it is in this group

    • The name "validate_order" says "validate": a word for reading.
    • The description's first verb is "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,504 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ew before create_order; shopping intent or validation alone is not authorization."

      What this check looks for
    Description, as the server wrote it
    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 installation choices. Resolve mismatches before requesting authorization. Present every returned charge, discount, condition and unknown; do not invent a price adjustment for declined auto-pay or paperless billing. Never repeat the service PIN or full date of birth, even if supplied earlier. Keep capability IDs, terms_hash and validation_token out of customer-facing prose. Obtain explicit authorization for this exact current review before create_order; shopping intent or validation alone is not authorization.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: false
Only reads 1Show 1 read-only tool
  • get_orderRetrieve recorded fulfillment evidence with checkout_id, especially after a lost or uncertain create_order response.Reads text others writeNo findings

    Why it is in this group

    • The name "get_order" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.letshum.com/mcp: tools/list returned 4 tools to an anonymous client, including create_order (destructive), check_availability (write), validate_order (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,504 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ew before create_order; shopping intent or validation alone is not authorization."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.3.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__internet-availability__get_order"
    ],
    "ask": [
      "mcp__internet-availability__check_availability",
      "mcp__internet-availability__validate_order"
    ],
    "deny": [
      "mcp__internet-availability__create_order"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as internet-availability. Review it before you use it.

Capability tags behind 4 rules
  • mcp__internet-availability__check_availability untrusted-input
  • mcp__internet-availability__validate_order untrusted-input
  • mcp__internet-availability__create_order untrusted-input
  • mcp__internet-availability__get_order untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.letshum/internet-availability/verify?hash=b27ffb41dc428f70670d97786d2b7f6bda700189bce369dc23f5844b020c6b90" | jq -e '.changed == false'

Pinned hash b27ffb41dc42, from Nov 13, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.letshum/internet-availability/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.letshum/internet-availability
[![Anlyon Radar](https://radar.anlyon.com/badge/com.letshum/internet-availability.svg)](https://radar.anlyon.com/servers/com.letshum/internet-availability)

Source: MCP Registry. Synced Oct 21, 2026, 17:58 UTC.

Hum Internet Availability MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Hum Internet Availability MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Hum Internet Availability MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: create_order.

Can the Hum Internet Availability MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Hum Internet Availability MCP server have?

4 tools: 1 destructive, 2 write, 1 read. create_order, check_availability, validate_order and get_order.

Does the Hum Internet Availability MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Hum Internet Availability MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Hum Internet Availability MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.