Skip to main content

cr1000a-mcp

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

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 (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).

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

Metadata

Release files for cr1000a-mcp 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cr1000a-mcp 0.2.1
File Size Uploaded Provenance Actions
cr1000a_mcp-0.2.1.tar.gz 15.0 kB With provenance Details for cr1000a_mcp-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cr1000a-mcp 0.2.1
File Interpreter ABI Platform Actions
cr1000a_mcp-0.2.1-py3-none-any.whl Python 3 none any Details for cr1000a_mcp-0.2.1-py3-none-any.whl

Total release size: 32.6 kB

Release files / cr1000a_mcp-0.2.1.tar.gz

Download URL cr1000a_mcp-0.2.1.tar.gz
Size 15.0 kB
Tags Source
SHA-256 checksum
How to use checksums
af9e67305a4859cc908a32a88573960220250a10e92f383034529429950a568b
BLAKE2b-256 checksum
How to use checksums
67945aa2633be366797287af9aca5dec672a7e7cb464658b528d4b08f289f4da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

Release files / cr1000a_mcp-0.2.1-py3-none-any.whl

Download URL cr1000a_mcp-0.2.1-py3-none-any.whl
Size 17.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b1cfcd276273578613150a0471b1e6c1901c703882a2b4d8ddb1eafd04268c9c
BLAKE2b-256 checksum
How to use checksums
e3ef0e5aaa74cb9d0079b2dc4b4063778f3dbbbd80da90571add25f5537cf232
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

Security for cr1000a-mcp 0.2.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for cr1000a_mcp-0.2.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page