zte-f6600p
Related Servers
Alternatives to zte-f6600p
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables remote agents to securely read firewall and NAT rules, inspect routing tables and logs, and execute safety-gated mutation plans through a bearer-authenticated MCP endpoint.49 npmMIT
- AlicenseBqualityBmaintenanceEnables MCP clients to read FRITZ!Box data over TR-064, including mesh, Wi-Fi, devices, logs, DSL, call lists, and voicemail, with optional guarded write actions for configuration changes.10MIT

Yeelight IoT MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables MCP clients to discover homes, areas, rooms, devices, groups, and scenes, query live state, and safely preview and execute device controls or scenes with dry-run confirmation.10Apache 2.0- AlicenseBqualityCmaintenanceEnables MCP clients to inspect an ISOTEL IDM smart gateway's devices, parameters, records, protocol stacks, streams, and connections, with read-only tools by default and opt-in allow-listed validated writes.14LGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and MCP clients to inspect accessible accounts, read provider data, and make explicitly approved entity-tag changes through a hosted gateway with discovery, schemas, policy enforcement, and execution controls.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to connect through a single Streamable HTTP endpoint, discover allowed backend servers and tools, inspect schemas, and invoke allowlisted catalog operations with authentication and scope checks.621 npmMIT
TDQS
Scored across 9 tools
Most tools target clearly different resources or actions, but router_read, router_get_dhcp, router_get_wifi, and router_soap_read form a cluster of read operations that could be confused. Similarly, router_execute_action and router_soap_action are both generic write paths, though the descriptions mostly disambiguate by protocol and safety level.
All tools consistently use the router_ prefix and snake_case, with mostly verb-led names such as router_list_endpoints and router_set_dhcp_range. Minor deviations include router_read as a bare verb and router_soap_read/router_soap_action placing the protocol qualifier before the action.
Nine tools is well within the appropriate range for a router-control server. The set includes specific safe helpers plus generic read/action and SOAP paths without feeling bloated.
The set covers endpoint discovery, DHCP and Wi-Fi reads, targeted DHCP/radio writes, and generic/SOAP read-action paths, which is solid for this router wrapper. Some common operations such as broader Wi-Fi/SSID writes or 5 GHz changes are left to generic actions rather than dedicated tools.