# WeaveFox (remote · www.weavefox.cn)

Manage WeaveFox apps and deploy web apps to WeaveFox Pages from any MCP client via API key.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `www.weavefox.cn`: 78/100 (this document), [markdown](https://verifymcp.io/servers/weavefox-weavefox/www.md), [page](https://verifymcp.io/servers/weavefox-weavefox/www)

## Channel facts

- Endpoint: `https://www.weavefox.cn/mcp`
- Transports: `streamable-http, sse`
- Auth: `required (not validated)`
- Version: `0.0.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1129 tokens (~80/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http weavefox-weavefox 'https://www.weavefox.cn/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "weavefox-weavefox": {
      "url": "https://www.weavefox.cn/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "weavefox-weavefox": {
      "type": "http",
      "url": "https://www.weavefox.cn/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.weavefox-weavefox]
url = "https://www.weavefox.cn/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "weavefox-weavefox": {
      "type": "remote",
      "url": "https://www.weavefox.cn/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add weavefox-weavefox --url 'https://www.weavefox.cn/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  weavefox-weavefox:
    url: "https://www.weavefox.cn/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "weavefox-weavefox": {
      "Transport": "http",
      "Url": "https://www.weavefox.cn/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add weavefox-weavefox -t streamable-http -u 'https://www.weavefox.cn/mcp'
```

### Other

```json
{
  "mcpServers": {
    "weavefox-weavefox": {
      "type": "http",
      "url": "https://www.weavefox.cn/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-19 (score 78, +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.

### 2026-11-18 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-11-15 (score 36)

First indexed and scored.

## MCP tools (14)

### `wf_readme` (~35 tokens)

Read WeaveFox guide

Read this first before using any other WeaveFox MCP tools. Provides a guide on how to use WeaveFox open capabilities.

### `wf_get_me` (~16 tokens)

Get authenticated user profile

Get the current authenticated user profile

### `wf_create_app` (~76 tokens)

Create WeaveFox app

Create a new app. Currently only supports external (WeaveFox Pages) app type that hosts web app artifacts.

Input parameters:

- `agentType` (string, required): App agent type. Currently only "external" (WeaveFox Pages hosting) is supported.
- `description` (string): App description
- `name` (string, required): App name

### `wf_list_apps` (~108 tokens)

List WeaveFox apps

List apps of the current authenticated user with pagination

Input parameters:

- `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

### `wf_update_app` (~307 tokens)

Update WeaveFox app

Update an app name, description, tags, cover image, visibility status, custom domain URL, etc.

Input parameters:

- `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, required): 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…

### `wf_send_message` (~67 tokens)

Send message to app agent

Send a message to the app agent to iterate on app features. The agent runs asynchronously; use get_message to poll status.

Input parameters:

- `message` (string, required): The text message to send to the app
- `publicId` (string, required): The public ID of the app to send message to

### `wf_get_message` (~39 tokens)

Get app agent message status

Get the status and content of the app agent message

Input parameters:

- `publicId` (string, required): The public ID of the app to query message status for

### `wf_list_messages` (~75 tokens)

List app agent messages

List messages of an app with pagination, sorted by creation time in descending order.

Input parameters:

- `page`: Page number, starts from 1, default 1
- `pageSize`: Page size, max 20, default 20
- `publicId` (string, required): The public ID of the app to list messages for

### `wf_stop_message` (~38 tokens)

Stop app agent stream

Stop the running agent stream of an app.

Input parameters:

- `publicId` (string, required): The public ID of the app to stop the running agent stream

### `wf_get_upload_token` (~55 tokens)

Get Pages upload token

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.

Input parameters:

- `publicId` (string, required): The public ID of the app

### `wf_pages_create_version` (~113 tokens)

Create Pages version from artifact

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.

Input parameters:

- `artifactZipUrl` (string, required): URL of the artifact zip file, must be the artifactZipUrl returned by upload_artifact_zip
- `changelog` (string, required): Changelog for this version
- `previewImg` (string): Preview screenshot URL for this version
- `publicId` (string, required): The public ID of the app

### `wf_list_versions` (~69 tokens)

List app versions

List versions of an app with pagination, sorted by creation time descending.

Input parameters:

- `page`: Page number, starts from 1, default 1
- `pageSize`: Page size, max 100, default 20
- `publicId` (string, required): The public ID of the app

### `wf_deploy_version` (~100 tokens)

Deploy Pages version

Deploy a specific version of a WeaveFox Pages app to make it live.

Input parameters:

- `publicId` (string, required): 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, required): Version number to deploy, e.g. "v1" (obtained from list_versions response)

### `wf_get_docs` (~31 tokens)

Get WeaveFox documentation

Get WeaveFox documentation links for LLM-friendly reading, including a concise summary and a full-text version.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/weavefox-weavefox/www#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 36
- 2026-11-15: 36

## Common questions

### 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.

## Links

- Remote endpoint: https://www.weavefox.cn/mcp
- Repository: https://github.com/weavefox/weavefox-cli
- Website: https://www.weavefox.cn/open
- Changelog RSS feed: https://verifymcp.io/servers/weavefox-weavefox/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/weavefox-weavefox/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/weavefox-weavefox/www.json
- HTML version of this page: https://verifymcp.io/servers/weavefox-weavefox/www
