cr1000a-mcp
Provides tools for interacting with a Verizon CR1000A Fios router via its undocumented web-UI API. It can query router status, connected devices, bandwidth and traffic history, DNS records, port forwards, IPv6 pinholes, and allowlisted router pages, with optional write tools for managing local DNS records, port forwards, and IPv6 pinholes when explicitly enabled.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cr1000a-mcp Who is connected to my network right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Verizon Fios CR1000A MCP Server
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 checkuvx 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-mcpClaude Desktop, one-click (MCPB bundle)
Download
cr1000a-mcp-<version>.mcpbfrom the latest release.Open the file (or Claude Desktop > Settings > Extensions > Advanced settings > Install Extension) and click Install.
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 -w2. 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 checkWhat 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
securitycommand trustssecurity, sosecurity find-generic-password -s cr1000a-mcp -wprints 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 |
| (unset) | Router IP or hostname, optionally with |
|
| Full URL. If set, it wins over the IP variables |
|
| The router's login page has no username field; leave the default |
| (empty) | Network Settings Password |
| (unset) | Alias for the password, used only when |
| off | Set to |
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 |
| uptime, WAN IPv4/IPv6, WAN DNS servers |
| known devices. Default is 13 fields per device; options |
| recent WAN throughput series |
| per-device traffic counters by period |
| local DNS records |
| port-forwarding rules (user and UPnP) |
| IPv6 pinhole rules |
| one allowlisted page: |
Write tools, registered only when CR1000A_MCP_ALLOW_WRITE=1:
Tool | Effect |
| local DNS records (adding IPv6 records is not supported by the underlying client) |
| port forwards. A forward opens a port to the internet |
| 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 forwardIt 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 |
| start the MCP server (stdio) |
| log in once and run every read-only call; prints response shapes and the firmware version, never values. Safe to paste into an issue |
| 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
checkafter 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_v6and 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 toolsget_bandwidth_historyGet Bandwidth HistoryBRead-onlyIdempotent
Recent WAN throughput samples as a list of integer series.
Inputs: no named parameters. Returns: result
get_host_trafficGet Host TrafficARead-onlyIdempotent
Per-device traffic counters, keyed by period in seconds then MAC.
Inputs: no named parameters. Returns: object
get_router_pageGet Router PageARead-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 DevicesARead-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 RecordsBRead-onlyIdempotent
Local IPv4 DNS records as {idx, name, ip} rows.
Inputs: no named parameters. Returns: result
list_dns_records_v6List Dns Records V6ARead-onlyIdempotent
Local IPv6 DNS records as {idx, name, ip} rows.
Inputs: no named parameters. Returns: result
list_ipv6_pinholesList Ipv6 PinholesBRead-onlyIdempotent
Configured IPv6 pinhole (inbound firewall) rules.
Inputs: no named parameters. Returns: object
list_port_forwardsList Port ForwardsBRead-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 StatusCRead-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
Scored across 9 tools
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.
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.
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.
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
Related MCP Connectors
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Manage VeriTeknik servers, DNS, backups and support tickets from your AI assistant.
37 WHOIS, DNS, IP, threat intelligence, email, and bulk tools for AI agents via WhoisXML API.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseBqualityCmaintenanceExposes 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.21MIT
- AlicenseAqualityBmaintenanceEnables 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.15MIT
- AlicenseBqualityCmaintenanceEnables 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.41MIT