cr1000a-mcp
An MCP server for the Verizon CR1000A (Fios) router.
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.
Tools
Read-only (always available):
| Tool | Returns |
|---|---|
router_status |
uptime, WAN IPv4/IPv6, WAN DNS servers |
list_devices |
known devices (13-field default; fields, name_contains, limit, verbose) |
get_bandwidth_history |
recent WAN throughput series |
get_host_traffic |
per-device traffic counters by period |
list_dns_records |
local IPv4 DNS records |
list_port_forwards |
port-forwarding rules |
list_dns_records_v6 |
local IPv6 DNS records |
list_ipv6_pinholes |
IPv6 pinhole rules |
get_router_page |
one allowlisted data page: arp, net_connections, log, upnp, firmware; secret-named fields are redacted |
Write tools, registered only when CR1000A_MCP_ALLOW_WRITE=1:
add_dns_record, remove_dns_record, remove_dns_record_v6, add_port_forward,
remove_port_forward, add_ipv6_pinhole, remove_ipv6_pinhole. (Adding IPv6 DNS records is not
supported by the underlying client.)
Inputs are validated before the router is contacted, and failed writes are never retried.
Configuration
Set via environment variables (or a .env file in the working directory):
| Variable | Default | Notes |
|---|---|---|
VZ_ROUTER_BASE_URL |
https://192.168.1.1 |
full URL; wins over the IP variables below |
VZ_ROUTER_IP |
(unset) | router IP or hostname, optionally :port (for example 192.168.1.1); HTTPS is added. Alias: ROUTER_IP. http:// is rejected |
VZ_ROUTER_USERNAME |
admin |
|
VZ_ROUTER_PASSWORD |
(empty) | router admin password ("Network Settings Password" on the router's sticker) |
NETWORK_SETTINGS_PASSWORD |
(unset) | alias, used only when VZ_ROUTER_PASSWORD is empty; read from the environment or .env |
CR1000A_MCP_ALLOW_WRITE |
off | set to 1 to enable write tools |
The router's certificate is bound to mynetworksettings.com; the client sets SNI/Host
automatically when you connect by IP and bundles the Verizon root CA.
Install
Once published to PyPI (see Releasing), run it without cloning:
uvx cr1000a-mcp # start the MCP server
uvx cr1000a-mcp check # live read-only validation
Until then, use uv run --directory /path/to/cr1000a-mcp cr1000a-mcp as shown below.
Use with Claude Code
claude mcp add cr1000a \
--env VZ_ROUTER_PASSWORD=your-admin-password \
-- uv run --directory /path/to/cr1000a-mcp cr1000a-mcp
Use with Claude Desktop
{
"mcpServers": {
"cr1000a": {
"command": "uv",
"args": ["run", "--directory", "/path/to/cr1000a-mcp", "cr1000a-mcp"],
"env": { "VZ_ROUTER_PASSWORD": "your-admin-password" }
}
}
}
Live check
cr1000a-mcp check logs in once, runs every read-only call against your router and prints a
JSON report of response shapes (types, counts, key names; never values), so it is safe to
paste into an issue. It never calls a write endpoint.
uv run cr1000a-mcp check
Exit code is 0 when every check passes. Log out of the router's web UI first, since the router may allow only one session.
Caveats
- Unofficial: firmware updates can change the endpoints.
- Logging in may end an active web-UI session on the router.
- All read paths were validated against a real CR1000A on firmware 3.6.0.5_BD (see
docs/endpoints.md); write tools are tested with fakes only. Runcr1000a-mcp checkto validate your own firmware.
Releasing
Publishing uses PyPI trusted publishing (no API token). One-time setup, by the repo owner:
- On PyPI, add a pending publisher for project
cr1000a-mcp: ownersohampatwardhan, repositorycr1000a-mcp, workflowrelease.yml, environmentpypi. - In GitHub, create an environment named
pypi(optionally require a reviewer).
To release: bump version in pyproject.toml, merge, then tag and push:
git tag v0.1.0 && git push origin v0.1.0
The workflow checks the tag matches the package version, runs lint and tests, builds, and publishes.
Development
uv sync
uv run ruff check . && uv run ruff format --check .
uv run pytest
Metadata
Release files for cr1000a-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cr1000a_mcp-0.1.0.tar.gz | 12.7 kB | With provenance | Details for cr1000a_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cr1000a_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cr1000a_mcp-0.1.0-py3-none-any.whl |
Total release size: 27.6 kB
Release files / cr1000a_mcp-0.1.0.tar.gz
| Download URL | cr1000a_mcp-0.1.0.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4506a250d51ac690376d33c9f2b743ea1f0cdceeaf7a0423014d2d8fbd9ba65e
|
|
BLAKE2b-256 checksum How to use checksums |
42dec56552c03f30e2403e5a02bce25914b11a5005e46716d0d6868f29c82625
|
| 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 logRelease files / cr1000a_mcp-0.1.0-py3-none-any.whl
| Download URL | cr1000a_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 14.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e4262ccff20c720f6fc71002b8d70ed1f25a86d1210c16a88ecc032856971290
|
|
BLAKE2b-256 checksum How to use checksums |
441f7c9ebae89998f654ff75eefa411a499eaf07db75b4968f62b6368ee64ed7
|
| 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 logSecurity for cr1000a-mcp 0.1.0
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.
Attestation for cr1000a_mcp-0.1.0.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 logA 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.