WeaveFox
REMOTE · WWW.WEAVEFOX.CN
Manage WeaveFox apps and deploy web apps to WeaveFox Pages from any MCP client via API key.
Available components
Last scanned (13 hours ago)
Scores higher than 71% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CI/CD and DevOps
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1129 tokens (~80/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 +41
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 15 Nov 26 36
First indexed and scored.
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 21 Nov 2026 · Probed https://www.weavefox.cn/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=weavefox.cn,O=Alipay Payment Technology Co.\, Ltd,ST=Shanghai,C=CN | CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US | 14 Jul 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | b21de3cd1a3b844d6663f058ca19ad9 |
| SANs: weavefox.cn, www.weavefox.cn, prepub.weavefox.cn, bass.weavefox.cn, baas.weavefox.cn, lab.weavefox.cn, app.weavefox.cn, *.weavefox.cn, *.app.weavefox.cn, *.app-pre.weavefox.cn, *.preview.weavefox.cn, *.preview-pre.weavefox.cn | ||||||
| CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 15 Dec 2022 | 14 Dec 2032 | RSA 4096 | SHA256-RSA | 4c1b960191fcabedcda9301a6cd78c3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.weavefox.cn. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| cn. | DS published | 33094 | 8 | Verified |
| weavefox.cn. | 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 tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 3 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.weavefox.cn/mcp | Verified | 200 | |
| sse | https://www.weavefox.cn/mcp | Unreachable | ||
| http (plaintext) | http://www.weavefox.cn/mcp | HTTPS enforced | 301 | https://www.weavefox.cn/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 →
wf_create_app Create WeaveFox app ~76
Create a new app. Currently only supports external (WeaveFox Pages) app type that hosts web app artifacts.
| Name | Type | Req | Description |
|---|---|---|---|
| agentType | string | yes | App agent type. Currently only "external" (WeaveFox Pages hosting) is supported. |
| description | string | – | App description |
| name | string | yes | App name |
No output schema declared.
No examples provided.
wf_deploy_version Deploy Pages version ~100
Deploy a specific version of a WeaveFox Pages app to make it live.
| Name | Type | Req | Description |
|---|---|---|---|
| publicId | string | yes | The public ID of the app |
| securityCheckId | string | – | Security check ID. Required only when re-deploying after confirming security risks; omit on first deploy to auto-trigger security check |
| version | string | yes | Version number to deploy, e.g. "v1" (obtained from list_versions response) |
No output schema declared.
No examples provided.
wf_get_docs Get WeaveFox documentation ~31
Get WeaveFox documentation links for LLM-friendly reading, including a concise summary and a full-text version.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wf_get_me Get authenticated user profile ~16
Get the current authenticated user profile
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wf_get_message Get app agent message status ~39
Get the status and content of the app agent message
| Name | Type | Req | Description |
|---|---|---|---|
| publicId | string | yes | The public ID of the app to query message status for |
No output schema declared.
No examples provided.
wf_get_upload_token Get Pages upload token ~55
Get a short-lived upload token for uploading an artifact zip file. Use the returned token as Bearer token in the Authorization header when calling the upload URL.
| Name | Type | Req | Description |
|---|---|---|---|
| publicId | string | yes | The public ID of the app |
No output schema declared.
No examples provided.
wf_list_apps List WeaveFox apps ~108
List apps of the current authenticated user with pagination
| Name | Type | Req | Description |
|---|---|---|---|
| agentType | string | – | Filter by agent type: general_code_expert, lingguang, alipay_h5, external |
| keyword | string | – | Fuzzy search keyword for app name or description |
| page | – | – | Page number, starts from 1, default 1 |
| pageSize | – | – | Page size, max 100, default 10 |
| publicId | string | – | Filter by exact public ID |
No output schema declared.
No examples provided.
wf_list_messages List app agent messages ~75
List messages of an app with pagination, sorted by creation time in descending order.
| Name | Type | Req | Description |
|---|---|---|---|
| page | – | – | Page number, starts from 1, default 1 |
| pageSize | – | – | Page size, max 20, default 20 |
| publicId | string | yes | The public ID of the app to list messages for |
No output schema declared.
No examples provided.
wf_list_versions List app versions ~69
List versions of an app with pagination, sorted by creation time descending.
| Name | Type | Req | Description |
|---|---|---|---|
| page | – | – | Page number, starts from 1, default 1 |
| pageSize | – | – | Page size, max 100, default 20 |
| publicId | string | yes | The public ID of the app |
No output schema declared.
No examples provided.
wf_pages_create_version Create Pages version from artifact ~113
Create a new version of a WeaveFox Pages app from a local prebuilt artifact (zip). artifactZipUrl must be the URL returned by the artifact upload API.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactZipUrl | string | yes | URL of the artifact zip file, must be the artifactZipUrl returned by upload_artifact_zip |
| changelog | string | yes | Changelog for this version |
| previewImg | string | – | Preview screenshot URL for this version |
| publicId | string | yes | The public ID of the app |
No output schema declared.
No examples provided.
wf_readme Read WeaveFox guide ~35
Read this first before using any other WeaveFox MCP tools. Provides a guide on how to use WeaveFox open capabilities.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wf_send_message Send message to app agent ~67
Send a message to the app agent to iterate on app features. The agent runs asynchronously; use get_message to poll status.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The text message to send to the app |
| publicId | string | yes | The public ID of the app to send message to |
No output schema declared.
No examples provided.
wf_stop_message Stop app agent stream ~38
Stop the running agent stream of an app.
| Name | Type | Req | Description |
|---|---|---|---|
| publicId | string | yes | The public ID of the app to stop the running agent stream |
No output schema declared.
No examples provided.
wf_update_app Update WeaveFox app ~307
Update an app name, description, tags, cover image, visibility status, custom domain URL, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| customThumbnailUrl | string|null | – | Custom cover image URL, pass null to reset to default |
| description | string | – | App description |
| faviconUrl | string|null | – | Site favicon URL, only in-site upload URLs are accepted, pass null to clear |
| isPublic | integer | – | App visibility: 0 = private, 1 = public |
| isVisible | integer | – | Whether to show in public app list: 0 = hidden, 1 = visible |
| name | string | – | App name |
| newPublicId | string | – | New custom publicId (6-36 chars, letters/numbers/hyphens only). Will be lowercased automatically. |
| publicId | string | yes | The public ID of the app to update |
| tag | integer | – | App tag: 0=other, 1=support, 2=tool, 3=art, 4=translate, 5=data, 6=schedule, 7=video, 8=finance, 9=food, 10=education, 11=writing, 12=home, 13=health, 14=reading, 15=life, 16=audio, 17=office, 18=gar… |
No output schema declared.
No examples provided.
How do I install the WeaveFox MCP server?
WeaveFox is a hosted endpoint at https://www.weavefox.cn/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.weavefox.cn
claude mcp add --transport http weavefox-weavefox 'https://www.weavefox.cn/mcp'
What is the WeaveFox MCP server?
WeaveFox is an MCP server listed in the public MCP registry as io.github.WeaveFox/weavefox. Manage WeaveFox apps and deploy web apps to WeaveFox Pages from any MCP client via API key. This page covers its hosted endpoint (https://www.weavefox.cn/mcp).
Is the WeaveFox MCP server safe to use?
WeaveFox scores 78 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 WeaveFox MCP server expose?
WeaveFox exposes 14 tools: wf_readme, wf_get_me, wf_create_app, wf_list_apps, wf_update_app, and 9 more. Their descriptions and schemas cost roughly 1,129 tokens of context every time the server is loaded.
Does the WeaveFox MCP server require authentication?
Yes. WeaveFox 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 WeaveFox MCP server still maintained?
WeaveFox is still listed as active in the MCP registry. We last reached this channel on 21 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 WeaveFox MCP server?
VerifyMCP ran 13 checks on WeaveFox, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.