# Wever World Data (remote · wever-world-data.quiet-salad-e96e.workers.dev)

Discover Wever services, process data, and delegate checked results between agents.

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `wever-world-data.quiet-salad-e96e.workers.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data.md), [page](https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data)

## Channel facts

- Endpoint: `https://wever-world-data.quiet-salad-e96e.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.10.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_job).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1099 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Wever World Data MCP server?

Wever World Data is a hosted endpoint at https://wever-world-data.quiet-salad-e96e.workers.dev/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 com-weverpay-world-data 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-weverpay-world-data": {
      "url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-weverpay-world-data": {
      "type": "http",
      "url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-weverpay-world-data]
url = "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-weverpay-world-data": {
      "type": "remote",
      "url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-weverpay-world-data --url 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-weverpay-world-data:
    url: "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-weverpay-world-data": {
      "Transport": "http",
      "Url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-weverpay-world-data -t streamable-http -u 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-weverpay-world-data": {
      "type": "http",
      "url": "https://wever-world-data.quiet-salad-e96e.workers.dev/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-09-28 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 63, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 60, 0)

- [functional] Server version: 0.9.0 → 0.10.1

### 2026-09-18 (score 60, +1)

- [functional] Server version: 0.8.1 → 0.9.0
- [functional] Server version: 0.8.0 → 0.8.1

## MCP tools (10)

### `create_result_reference` (~142 tokens)

Authorize one recipient client_id to read one owned result with its own credential. Returns a credential-free, expiring reference for agent handoff. Owner access stays in the configured header. Requires explicit intended recipient; no permission to other jobs, deletion or resharing.

Input parameters:

- `job_id` (string, required)
- `recipient_client_id` (string, required): Public client identifier provided by the intended recipient through an authorized connection. Never their token.
- `request_key` (string, required): Stable reference idempotency key. Reuse with identical job, recipient and requested lifetime.
- `ttl_seconds` (integer): Reference lifetime, also bounded by the job and both access credentials' expiry.

### `delete_job` (~46 tokens)

Delete the owner's stored result content. Retains an idempotency tombstone until expiry and does not reset quotas. Configure the owner's bearer access header.

Input parameters:

- `job_id` (string, required)

### `get_catalog` (~31 tokens)

Read public capabilities, free allowances, access bootstrap, privacy, retention and HTTP discovery routes. No access credential required.

### `get_job` (~48 tokens)

Recover the original complete private CSV or audit result using its job_id and the owner's bearer access header. Results expire within 24 hours and cannot outlive access.

Input parameters:

- `job_id` (string, required)

### `get_result_reference` (~48 tokens)

Retrieve the full shared result using the nominated recipient's configured bearer header. The reference alone grants no access. Expired, revoked or deleted results are unavailable.

Input parameters:

- `reference_id` (string, required)

### `resolve_capability` (~83 tokens)

Resolve an exact canonical Wever service_id to its maintained connection metadata, contract, limits and access steps. Unknown identities are rejected; no caller-supplied URL is fetched. Does not verify live availability or authorize execution.

Input parameters:

- `service_id` (string, required): Exact canonical service_id from capability search, at most 96 UTF-8 bytes. Never a URL or credential.

### `revoke_result_reference` (~42 tokens)

Owner revokes future retrieval through one shared result reference. Repeating this action is safe; previously downloaded copies cannot be recalled.

Input parameters:

- `reference_id` (string, required)

### `search_capabilities` (~93 tokens)

Find maintained Wever capabilities by a short task description or keyword. Returns fixed known services with connection details, contracts, limits and access steps. Does not execute work, grant permissions, search the whole web, or verify live availability.

Input parameters:

- `limit` (integer)
- `query` (string, required): Nonblank query of at most 160 UTF-8 bytes. Deterministic keyword matching over maintained Wever services only.

### `submit_audit` (~301 tokens)

Audit bounded CSV against caller-supplied expected records with explicit grouping, exact source references, lineage and integrity checks. A completed audit can report mismatches or blocked parsing. Inspect result.status, comparison, ambiguities and unsupported rules. No factual verification or inferred transformations.

Input parameters:

- `csv_text` (string, required): At most 8192 UTF-8 bytes, 20 data records, 30 columns and 4096 UTF-8 bytes per cell. Exact strings are preserved.
- `expected_records` (array, required): Ordered expected records; field names and values are strings of at most 4096 UTF-8 bytes each.
- `request_key` (string, required): Stable idempotency key shared across CSV and audit. Reuse only with identical input for the same capability.
- `requested_rules` (array): Descriptive requests, each at most 200 UTF-8 bytes. Every entry is reported unsupported; these do not authorize extra transformations.
- `rule` (object): Supports {kind: preserve_rows} or {kind: explicit_groups, groups: [{source_records: [1,2], concatenate: {column: separator}}]}. Source indexes are one-based and exclude the header. Invalid or unsuppo…
- `source_metadata` (object): Descriptive metadata only, each value at most 200 UTF-8 bytes. No URL fetching or encoding conversion.

### `submit_csv` (~98 tokens)

Normalize bounded CSV using explicit column rules. Returns a complete private job and checked CSV. Configure bearer access in the client header. Reuse request_key on retries.

Input parameters:

- `csv_text` (string, required): At most 16 KiB UTF-8 and 100 data records
- `request_key` (string, required): Stable idempotency key shared across CSV and audit. Reuse only with identical input for the same capability.
- `schema` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data#diagnostics

## Score history

- 2026-09-29: 65
- 2026-09-28: 65
- 2026-09-27: 64
- 2026-09-26: 64
- 2026-09-25: 63
- 2026-09-24: 63
- 2026-09-23: 62
- 2026-09-22: 62
- 2026-09-21: 61
- 2026-09-20: 61
- 2026-09-19: 60
- 2026-09-18: 60
- 2026-09-17: 59
- 2026-09-16: 59

## Common questions

### What is the Wever World Data MCP server?

Wever World Data is an MCP server listed in the public MCP registry as com.weverpay/world-data. Discover Wever services, process data, and delegate checked results between agents. This page covers its hosted endpoint (https://wever-world-data.quiet-salad-e96e.workers.dev/mcp).

### Is the Wever World Data MCP server safe to use?

Wever World Data scores 65 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 Wever World Data MCP server expose?

Wever World Data exposes 10 tools: create_result_reference, delete_job, get_catalog, get_job, get_result_reference, and 5 more. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.

### Does the Wever World Data MCP server require authentication?

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

### Is the Wever World Data MCP server still maintained?

Wever World Data is still listed as active in the MCP registry. We last reached this channel on 29 September 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://wever-world-data.quiet-salad-e96e.workers.dev/mcp
- Authorisation metadata: https://wever-world-data.quiet-salad-e96e.workers.dev/.well-known/oauth-protected-resource/mcp
- Website: https://wever-world-data.quiet-salad-e96e.workers.dev/.well-known/wever-agent-services.json
- Changelog RSS feed: https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data.json
- HTML version of this page: https://verifymcp.io/servers/com-weverpay-world-data/wever-world-data