WideWired / 网连网络
REMOTE · WWW-API.WIDEWIRED.COM · 2 COMPONENTS
Manage WideWired private networks with an account API key. Choose China or global data storage.
Available components
Last scanned (19 hours ago)
Scores higher than 16% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: 0.50 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www-api.widewired.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www-api.widewired.com | CN=Cloudflare TLS Issuing ECC CA 4,O=SSL Corporation,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 492d52c1acfc795a7e6d90d69cae60f6 |
| SANs: www-api.widewired.com | ||||||
| CN=Cloudflare TLS Issuing ECC CA 4,O=SSL Corporation,C=US (CA) | CN=SSL.com TLS Transit ECC CA R2,O=SSL Corporation,C=US | 29 May 2025 | 27 May 2035 | ECDSA 256 | ECDSA-SHA384 | 604d12ecb70834c3a2c712bf9a8c7a89 |
| CN=SSL.com TLS Transit ECC CA R2,O=SSL Corporation,C=US (CA) | CN=SSL.com TLS ECC Root CA 2022,O=SSL Corporation,C=US | 21 Oct 2022 | 17 Oct 2037 | ECDSA 384 | ECDSA-SHA384 | 604d8af8d00ba8748b955853172c5f2e |
| CN=SSL.com TLS ECC Root CA 2022,O=SSL Corporation,C=US (CA) | CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB | 1 Aug 2025 | 31 Dec 2028 | ECDSA 384 | SHA256-RSA | 173dca60ea9f8e1026dafcd72810e48e |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www-api.widewired.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| widewired.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="WideWired MCP"
Bearer realm="WideWired MCP"| Header | Value |
|---|---|
| www-authenticate | Bearer realm="WideWired MCP" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www-api.widewired.com/mcp | Auth required | 401 | |
| http (plaintext) | http://www-api.widewired.com/mcp | HTTPS enforced | 301 | https://www-api.widewired.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
call_operation ~139
Invoke one discovered ordinary-user operation. Can modify/delete resources: obtain the human's decision and honor the existing service's validation and reauthentication. Purchases and checkout are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | Existing ordinary Account access token. Prefer host Authorization header or stdio credential storage; never repeat credentials in chat. |
| body | object | – | – |
| file | null|object | – | – |
| idempotency_key | string | – | – |
| last_event_id | string | – | – |
| operation_id | string | yes | The operation ID returned by search_operations or describe_operation |
| path | object | – | – |
| query | object | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
describe_operation ~34
Read an existing API's method, exact path parameters, request fields and service response contract.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
recharge ~27
Return the human-only browser recharge page. Does not create a purchase, initiate checkout or move money.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_operations ~90
Discover the existing user API operations for this Target. Paginate and describe an operation before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | Search API path, summary or request description, for example networks, devices, forward, alerts, password, rewards, messages |
| service | string | – | Optional account, controller, billing or livechat filter |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the WideWired / 网连网络 MCP server?
WideWired / 网连网络 is a hosted endpoint at https://www-api.widewired.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www-api.widewired.com
claude mcp add --transport http com-widewired-wwnet 'https://www-api.widewired.com/mcp'
What is the WideWired / 网连网络 MCP server?
WideWired / 网连网络 is an MCP server listed in the public MCP registry as com.widewired/wwnet. Manage WideWired private networks with an account API key. Choose China or global data storage. This page covers its hosted endpoint (https://www-api.widewired.com/mcp).
Is the WideWired / 网连网络 MCP server safe to use?
WideWired / 网连网络 scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the WideWired / 网连网络 MCP server expose?
WideWired / 网连网络 exposes 4 tools: call_operation, describe_operation, recharge, search_operations. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.
Does the WideWired / 网连网络 MCP server require authentication?
Yes. WideWired / 网连网络 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the WideWired / 网连网络 MCP server still maintained?
WideWired / 网连网络 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the WideWired / 网连网络 MCP server?
VerifyMCP ran 5 checks on WideWired / 网连网络, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about WideWired / 网连网络: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.