Skip to main content
Glama

Verizon Fios CR1000A MCP Server

PyPI version

An MCP server for the Verizon CR1000A (Fios) router. Ask your AI assistant who is on your network, what your WAN address is, or to add a local DNS record.

Verizon publishes no API for this router. The server talks to the router's undocumented web-UI API (cgi/*.js endpoints behind a sysauth cookie login) through the community verizon-router-client library. Read paths were validated on a real CR1000A running firmware 3.6.0.5_BD; see docs/endpoints.md for every endpoint and verified response shape.

Quick start

You need uv and your router's Network Settings Password (printed on the router's sticker).

# 1. Put your settings in a .env file (or export them). Plain text is the least secure
#    option; on macOS see "Keep the password out of plain-text files" below.
cat > .env <<'EOF'
ROUTER_IP=192.168.1.1
NETWORK_SETTINGS_PASSWORD=the-password-from-the-sticker
EOF
chmod 600 .env

# 2. Check that everything works (read-only; prints response shapes, never values)
uvx cr1000a-mcp check

uvx cr1000a-mcp with no arguments starts the MCP server on stdio.

Related MCP server: sfrbox-mcp

Add it to your AI client

Claude Code

claude mcp add cr1000a \
  --env ROUTER_IP=192.168.1.1 \
  --env NETWORK_SETTINGS_PASSWORD=the-password-from-the-sticker \
  -- uvx cr1000a-mcp

Claude Desktop, one-click (MCPB bundle)

  1. Download cr1000a-mcp-<version>.mcpb from the latest release.

  2. Open the file (or Claude Desktop > Settings > Extensions > Advanced settings > Install Extension) and click Install.

  3. Enter your router IP (the default is usually right) and the Network Settings Password. The password field is marked sensitive, so Claude Desktop masks it and stores it securely (per the MCPB spec) instead of in a plain-text config. "Allow changes" is off by default.

The bundle is tiny: on first start uv downloads the pinned cr1000a-mcp release from PyPI, so it needs network access and uv installed.

Claude Desktop, manual config (claude_desktop_config.json)

{
  "mcpServers": {
    "cr1000a": {
      "command": "uvx",
      "args": ["cr1000a-mcp"],
      "env": {
        "ROUTER_IP": "192.168.1.1",
        "NETWORK_SETTINGS_PASSWORD": "the-password-from-the-sticker"
      }
    }
  }
}

The server is read-only until you also set CR1000A_MCP_ALLOW_WRITE=1 (see below).

Keep the password out of plain-text files (macOS)

The setup above puts the Network Settings Password in plain text in a .env file, in ~/.claude.json (what claude mcp add --env writes) or in claude_desktop_config.json. AI agents read those files routinely, so the password can end up in an agent's context, its transcripts or a pasted bug report. Those options are the simplest but the least secure. On macOS you can keep the password in the Keychain and start the server through a small launcher that reads it at startup. (Suggested in #39.)

1. Save the password. With -w and no value it prompts, so the password never appears on screen or in shell history:

security add-generic-password -s cr1000a-mcp -a admin -w

2. Create a launcher, for example ~/.local/bin/cr1000a-mcp-launch, then run chmod 755 ~/.local/bin/cr1000a-mcp-launch:

#!/bin/zsh
# Claude Desktop starts with a minimal PATH; add the usual uv locations.
export PATH="$HOME/.local/bin:/opt/homebrew/bin:/usr/local/bin:$PATH"
pw=$(/usr/bin/security find-generic-password -s cr1000a-mcp -a admin -w 2>/dev/null)
if [[ -z "$pw" ]]; then
  echo "cr1000a-mcp: no Keychain item 'cr1000a-mcp'. Run: security add-generic-password -s cr1000a-mcp -a admin -w" >&2
  exit 1
fi
export NETWORK_SETTINGS_PASSWORD="$pw"
export ROUTER_IP="${ROUTER_IP:-192.168.1.1}"
exec uvx cr1000a-mcp "$@"

If uvx lives somewhere else (which uvx), add that directory to PATH in the script.

3. Point your client at the launcher. No secret goes into either config:

claude mcp add -s user cr1000a -- ~/.local/bin/cr1000a-mcp-launch
{
  "mcpServers": {
    "cr1000a": { "command": "/Users/<you>/.local/bin/cr1000a-mcp-launch" }
  }
}

4. Check it. The launcher passes arguments through, so this runs the read-only check:

~/.local/bin/cr1000a-mcp-launch check

What this does not protect against. The Keychain keeps the password out of files, client config and chat, but not from an agent with unrestricted shell access as your user:

  • A Keychain item created with the security command trusts security, so security find-generic-password -s cr1000a-mcp -w prints the password with no prompt. In Claude Code, deny that command in ~/.claude/settings.json:

    { "permissions": { "deny": ["Bash(security find-generic-password:*)"] } }

    Other agents have their own ways to restrict shell commands.

  • The password is an environment variable of the running server, so other processes running as your user can read it (for example with ps -E).

Linux (secret-tool) and Windows (Credential Manager) could get the same treatment later. Reading the Keychain inside the server itself, so the password never sits in an environment variable, is a possible future option.

Configuration

Set as environment variables, or in a .env file in the working directory.

Variable

Default

Notes

VZ_ROUTER_IP

(unset)

Router IP or hostname, optionally with :port (192.168.1.1, router.lan, [fe80::1]:8443). HTTPS is added; http:// is rejected. Alias: ROUTER_IP. mynetworksettings.com also works if it resolves on your network

VZ_ROUTER_BASE_URL

https://192.168.1.1

Full URL. If set, it wins over the IP variables

VZ_ROUTER_USERNAME

admin

The router's login page has no username field; leave the default

VZ_ROUTER_PASSWORD

(empty)

Network Settings Password

NETWORK_SETTINGS_PASSWORD

(unset)

Alias for the password, used only when VZ_ROUTER_PASSWORD is empty

CR1000A_MCP_ALLOW_WRITE

off

Set to 1 to register the write tools

The router's TLS certificate is issued by Verizon's own CA for mynetworksettings.com. The client bundles that CA and sets the right server name when you connect by IP, so leave certificate verification on.

Tools

Read-only (always available):

Tool

Returns

router_status

uptime, WAN IPv4/IPv6, WAN DNS servers

list_devices

known devices. Default is 13 fields per device; options name_contains, limit, fields, verbose

get_bandwidth_history

recent WAN throughput series

get_host_traffic

per-device traffic counters by period

list_dns_records / list_dns_records_v6

local DNS records

list_port_forwards

port-forwarding rules (user and UPnP)

list_ipv6_pinholes

IPv6 pinhole rules

get_router_page

one allowlisted page: arp, net_connections, log, upnp, firmware. Secret-named fields (passwords, keys, tokens) are returned as [redacted]

Write tools, registered only when CR1000A_MCP_ALLOW_WRITE=1:

Tool

Effect

add_dns_record, remove_dns_record, remove_dns_record_v6

local DNS records (adding IPv6 records is not supported by the underlying client)

add_port_forward, remove_port_forward

port forwards. A forward opens a port to the internet

add_ipv6_pinhole, remove_ipv6_pinhole

inbound IPv6 firewall holes

Inputs are validated before the router is contacted, and a failed write is never retried.

Verify the write tools on your router

The write tools have not been verified against every firmware. To prove them on your own router, run the self-cleaning write test. It adds a throwaway DNS record, checks it appears, removes it, and checks it is gone:

uvx cr1000a-mcp write-test                  # DNS record only
uvx cr1000a-mcp write-test --port-forward   # also a throwaway port forward

It prints what it will change and asks for confirmation first (--yes skips the prompt). It refuses to start if a leftover cr1000a-mcp-test entry exists, always tries to clean up even when a check fails, and tells you where to delete the entry by hand if removal fails.

Commands

Command

What it does

cr1000a-mcp

start the MCP server (stdio)

cr1000a-mcp check

log in once and run every read-only call; prints response shapes and the firmware version, never values. Safe to paste into an issue

cr1000a-mcp write-test

live test of the write tools (see above)

Log out of the router's web UI before running check or write-test: the router may allow only one admin session.

Caveats

  • Unofficial: a firmware update can change the endpoints. Run check after updating.

  • Logging in may end an active web-UI session on the router.

  • Only firmware 3.6.0.5_BD has been verified: all read tools and the DNS and port-forward write tools (add_dns_record, remove_dns_record, add_port_forward, remove_port_forward). remove_dns_record_v6 and the IPv6 pinhole tools have not been tried on a real router yet.

Changelog and contributing

Bug reports, firmware compatibility reports and pull requests are welcome. See CONTRIBUTING.md for development setup, the issue-first workflow, how to run the live checks, and how releases work. Release notes are in CHANGELOG.md.

License

MIT

Available Tools

9 tools
get_bandwidth_historyGet Bandwidth HistoryB
Read-onlyIdempotent

Recent WAN throughput samples as a list of integer series.

Inputs: no named parameters. Returns: result

get_host_trafficGet Host TrafficA
Read-onlyIdempotent

Per-device traffic counters, keyed by period in seconds then MAC.

Inputs: no named parameters. Returns: object

get_router_pageGet Router PageA
Read-onlyIdempotent

Read one allowlisted router data page: arp (ARP table), net_connections, log, upnp or firmware (version info). Long lists are truncated to limit. Fields that look like secrets (passwords, keys, tokens) are returned as "[redacted]". Response shapes are firmware-specific; see docs/endpoints.md.

Inputs: page (required), limit. Returns: object

list_devicesList DevicesA
Read-onlyIdempotent

Devices the router knows about (connected and previously seen).

name_contains filters case-insensitively on any field (hostname, IP, MAC). Results are capped at limit. By default each device keeps a short field set (name, hostname, ip, ipv6, mac, mac_vendor, ui_type, ui_manufacturer, ui_model, activity, port, is_dhcp, time_last_active); pass fields to choose others (the router returns 41, for example user_agent, os, time_first_seen) or verbose for everything.

Inputs: limit, fields, verbose, name_contains. Returns: object

list_dns_recordsList Dns RecordsB
Read-onlyIdempotent

Local IPv4 DNS records as {idx, name, ip} rows.

Inputs: no named parameters. Returns: result

list_dns_records_v6List Dns Records V6A
Read-onlyIdempotent

Local IPv6 DNS records as {idx, name, ip} rows.

Inputs: no named parameters. Returns: result

list_ipv6_pinholesList Ipv6 PinholesB
Read-onlyIdempotent

Configured IPv6 pinhole (inbound firewall) rules.

Inputs: no named parameters. Returns: object

list_port_forwardsList Port ForwardsB
Read-onlyIdempotent

Configured port-forwarding rules (user rules and UPnP rules).

Firmware-reserved read-only rules are only counted unless include_readonly is true.

Inputs: include_readonly. Returns: object

router_statusRouter StatusC
Read-onlyIdempotent

Uptime (seconds), WAN IPv4/IPv6 addresses and WAN DNS servers.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct data domain: router status, device list, WAN throughput, per-device traffic, IPv4/IPv6 DNS records, port forwards, and IPv6 pinholes. The generic get_router_page partially overlaps specialized tools (arp vs list_devices, upnp vs list_port_forwards), which could cause occasional misselection.

    Naming Consistency4/5

    Seven of nine tools follow a predictable list_/get_ + noun pattern, and the IPv4/IPv6 DNS pair is clearly differentiated by suffix. router_status is the only noun-first outlier, and get_bandwidth_history/get_host_traffic return collections despite the get_ prefix, but overall the convention is readable and consistent.

    Tool Count5/5

    Nine tools sit comfortably in the ideal 3-15 range for a router-monitoring server. Each tool covers a distinct concern with no filler or redundant entries.

    Completeness4/5

    The read-only surface is broad: status, clients, bandwidth, per-host traffic, DNS records for both IP versions, forwarding/pinhole rules, and generic access to ARP, logs, UPnP, and firmware pages. Write/configuration operations (e.g., adding port forwards or DNS entries, rebooting) are absent, but this appears intentional for a diagnostics-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact with Xiaomi/Redmi routers, providing read-only queries and management capabilities such as device listing, port forwarding, DHCP reservations, and reboot control.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Exposes 21 tools that let an AI agent read and write the configuration of an SFR NB6VAC fibre box over its reverse-engineered web interface, covering WAN status, connected devices, Wi-Fi SSIDs and WPA keys, DHCP, NAT port forwarding, DMZ, UPnP, firewall, DDNS, Wake-on-LAN and reboots.
      21
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM clients to inspect and manage a TP-Link Deco mesh Wi-Fi network, covering mesh nodes, connected devices, SSIDs and radio settings, internet status, blocked clients, and DHCP address reservations. Runs entirely against the router on the local network without any cloud account.
      15
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables an AI assistant to manage a Verizon Fios CR1000A router through its local web interface, covering port forwarding, DHCP reservations, static routes, DNS, firewall/DMZ, UPnP, Wi-Fi, device blocking, and configuration migration. Changes use preview/confirm and read-back verification, with policy controls and secret redaction.
      41
      MIT