# Vaneform (remote · vaneform.com)

Free website traffic checker: monthly visits, traffic sources, top countries and domain compares.

- Trust score: 33/100 (low)
- Change this week: −27
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `vaneform.com`: 33/100 (this document), [markdown](https://verifymcp.io/servers/jiangqizheng-vaneform-mcp/vaneform.md), [page](https://verifymcp.io/servers/jiangqizheng-vaneform-mcp/vaneform)

## Channel facts

- Endpoint: `https://vaneform.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.3`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 5 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.

## Install

### How do I install the Vaneform MCP server?

Vaneform is a hosted endpoint at https://vaneform.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.

### Claude

```bash
claude mcp add --transport http jiangqizheng-vaneform-mcp 'https://vaneform.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jiangqizheng-vaneform-mcp": {
      "url": "https://vaneform.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jiangqizheng-vaneform-mcp": {
      "type": "http",
      "url": "https://vaneform.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jiangqizheng-vaneform-mcp]
url = "https://vaneform.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jiangqizheng-vaneform-mcp": {
      "type": "remote",
      "url": "https://vaneform.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jiangqizheng-vaneform-mcp --url 'https://vaneform.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jiangqizheng-vaneform-mcp:
    url: "https://vaneform.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jiangqizheng-vaneform-mcp": {
      "Transport": "http",
      "Url": "https://vaneform.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jiangqizheng-vaneform-mcp -t streamable-http -u 'https://vaneform.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jiangqizheng-vaneform-mcp": {
      "type": "http",
      "url": "https://vaneform.com/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-10-23 (score 33, −30)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-22 (score 63, +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.

### 2026-10-20 (score 62, +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.

### 2026-10-18 (score 61, +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.

### 2026-10-16 (score 60, +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.

### 2026-10-15 (score 59, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_account” rewrote its description, which is the text the model reads
- [security] Tool “get_research_workspace” rewrote its description, which is the text the model reads
- [security] Tool “lookup_domain” rewrote its description, which is the text the model reads
- [security] Tool “manage_research” rewrote its description, which is the text the model reads
- [security] Tool “monitor_research” rewrote its description, which is the text the model reads
- [security] Tool “research_site” rewrote its description, which is the text the model reads
- [security] Tool “save_research” rewrote its description, which is the text the model reads
- [security] Tool “compare_bulk” rewrote its description, which is the text the model reads
- [security] Tool “compare_tld” rewrote its description, which is the text the model reads
- [security] Tool “lookup_keyword” rewrote its description, which is the text the model reads

### 2026-10-13 (score 59, +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-10-12 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (10)

### `research_site` (~172 tokens)

Free early-access standalone site research. Query Google ads by domain or advertiser, public Meta ads by keyword, AdSense accounts/related sites, outbound page links, collected ad text, recorded website opportunities or DR changes. Source acquisition is explicit and bounded; all these tools spend 0 credits. Ad text and Publisher ID reverse lookups cover the recorded collection. Estimates and observations retain dates, scope and confidence.

Input parameters:

- `cursor` (string)
- `limit` (integer)
- `maxAgeMonths` (integer)
- `maxDr` (number)
- `maxVisits` (number)
- `minDr` (number)
- `minVisits` (number)
- `mode` (string)
- `q` (string, required)
- `region` (string)
- `tool` (string, required)

### `get_research_workspace` (~47 tokens)

Read the caller saved research, folders, private notes, tool history, publisher/ad monitors and in-app change notifications. Free; 0 credits. Account ownership comes from the authenticated key.

### `save_research` (~61 tokens)

Save a standalone site-tool query in the caller workspace, with a folder and private notes. Free; 0 credits.

Input parameters:

- `folder` (string, required)
- `label` (string, required)
- `notes` (string, required)
- `query` (object, required)

### `monitor_research` (~71 tokens)

Monitor a Google Ads or AdSense query daily or weekly. Record newly observed public ads and connected sites as private in-app notifications. The first successful observation establishes a baseline. Free; 0 credits.

Input parameters:

- `interval_days` (integer, required)
- `label` (string, required)
- `query` (object, required)

### `manage_research` (~89 tokens)

Manage the caller private research: remove a saved target, pause/resume or change daily/weekly monitoring, remove a monitor, check current public data, or mark a change notification read. Use IDs from get_research_workspace. Free; 0 credits.

Input parameters:

- `action` (string, required)
- `active` (boolean)
- `id` (string, required)
- `interval_days` (integer)

### `lookup_domain` (~238 tokens)

Read a cached Vaneform domain snapshot: scale (full-site or search visits), registry, site profile, and link-rank popularity. Optional include=baidu is cached Baidu rank. Optional include=search is Pro-only keyword rankings (ranked keywords, landing pages, search competitors) from this month's cache. Cache-only: status=missing means not cached, not zero traffic. Use for 查网站, 访问量, how big a site is, domain visits, registry age, backlink rank, 百度权重, or 关键词排名. A new ready or partial domain spends 1 credit, or 10 when include=search finds no saved ranking or a saved ranking whose status is ready. include=search spends 0 when that saved status is missing, error, or partial.

Input parameters:

- `domain` (string, required): Host such as google.com. A leading www. is removed and the host is lowercased.
- `include` (string): Comma-separated families: scale,registry,profile,popularity,baidu,search. Default is the first four. baidu is cached Baidu rank. search is Pro-only.

### `get_account` (~32 tokens)

Read the caller plan, website lookup allowance, and credit balance. This call spends 0. Use before a batch.

### `lookup_keyword` (~124 tokens)

Read a US/EN keyword brief: monthly searches, difficulty, CPC, and Google occupancy. Pro-only. At most 30 Google results. A cache hit is free; a successful miss spends 60 credits. After trimming, longer than 200 characters is invalid. Matching uses the lowercased, space-collapsed first 80 characters. Use for 关键词查询.

Input parameters:

- `q` (string, required): Keyword such as google or apple. After trimming, longer than 200 characters is invalid. Matching keeps the lowercased, space-collapsed first 80 characters.

### `compare_bulk` (~88 tokens)

Compare domains side by side. Returns scale and registry. Fetches traffic when monthly visits are missing. Spends 1 credit per compared domain with data. Up to 3 domains on Free, 30 on Pro. Use for 批量对比.

Input parameters:

- `q` (string, required): Domains separated by commas or newlines, such as google.com,apple.com. Duplicate domains are kept once.

### `compare_tld` (~138 tokens)

Compare the same registrable name across suffixes. Default suffixes are com,ai,io. example.com is read as example. Response suffixes and items follow a fixed suffix order; match the returned suffixes. Fetches traffic when monthly visits are missing. Spends 1 credit per compared domain with data. Use for 后缀对比.

Input parameters:

- `q` (string, required): Base name such as google. google.com is read as google.
- `s` (string): Comma- or whitespace-separated suffixes. Default is com,ai,io. Duplicates are kept once. Response order follows the site suffix list.

## Diagnostics

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

## Score history

- 2026-10-23: 33
- 2026-10-22: 63
- 2026-10-21: 62
- 2026-10-20: 62
- 2026-10-19: 61
- 2026-10-18: 61
- 2026-10-17: 60
- 2026-10-16: 60
- 2026-10-15: 59
- 2026-10-14: 59
- 2026-10-13: 59
- 2026-10-12: 58
- 2026-10-11: 58

## Common questions

### What is the Vaneform MCP server?

Vaneform is an MCP server listed in the public MCP registry as io.github.jiangqizheng/vaneform-mcp. Free website traffic checker: monthly visits, traffic sources, top countries and domain compares. This page covers its hosted endpoint (https://vaneform.com/mcp).

### Is the Vaneform MCP server safe to use?

Vaneform 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 Vaneform MCP server expose?

Vaneform exposes 10 tools: research_site, get_research_workspace, save_research, monitor_research, manage_research, and 5 more. Their descriptions and schemas cost roughly 1,060 tokens of context every time the server is loaded.

### Does the Vaneform MCP server require authentication?

No. We connected to Vaneform without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vaneform MCP server still maintained?

Vaneform is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vaneform.com/mcp
- Authorisation metadata: https://vaneform.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/vaneform/vaneform-mcp
- Website: https://vaneform.com/docs/api
- Changelog RSS feed: https://verifymcp.io/servers/jiangqizheng-vaneform-mcp/vaneform.xml
- Changelog JSON feed: https://verifymcp.io/servers/jiangqizheng-vaneform-mcp/vaneform.json
- HTML version of this page: https://verifymcp.io/servers/jiangqizheng-vaneform-mcp/vaneform