Wever World Data
REMOTE · WEVER-WORLD-DATA.QUIET-SALAD-E96E.WORKERS.DEV · SCANNED SEP 29
Discover Wever services, process data, and delegate checked results between agents.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_job). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1099 tokens (~109/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · wever-world-data.quiet-salad-e96e.workers.dev
claude mcp add --transport http com-weverpay-world-data 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp'
{
"mcpServers": {
"com-weverpay-world-data": {
"url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
}
}
} {
"servers": {
"com-weverpay-world-data": {
"type": "http",
"url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
}
}
} [mcp_servers.com-weverpay-world-data] url = "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
{
"$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 mcp add com-weverpay-world-data --url 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp' --transport streamable-http
mcp_servers:
com-weverpay-world-data:
url: "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp" {
"McpServers": {
"com-weverpay-world-data": {
"Transport": "http",
"Url": "https://wever-world-data.quiet-salad-e96e.workers.dev/mcp"
}
}
} assistant mcp add com-weverpay-world-data -t streamable-http -u 'https://wever-world-data.quiet-salad-e96e.workers.dev/mcp'
{
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 19 Sept 26 0
- Server version: 0.9.0 → 0.10.1 functional
- 18 Sept 26 +1
- Server version: 0.8.1 → 0.9.0 functional
- Server version: 0.8.0 → 0.8.1 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 29 Sept 2026 · Probed https://wever-world-data.quiet-salad-e96e.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quiet-salad-e96e.workers.dev | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 690ccc0964e7598b1313bcf7c863ee13 |
| SANs: quiet-salad-e96e.workers.dev, *.quiet-salad-e96e.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wever-world-data.quiet-salad-e96e.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wever-world-data.quiet-salad-e96e.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://wever-world-data.quiet-salad-e96e.workers.dev/mcp | Inconclusive | 405 |
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 →
create_result_reference ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
| recipient_client_id | string | yes | Public client identifier provided by the intended recipient through an authorized connection. Never their token. |
| request_key | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
delete_job ~46
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_catalog ~31
Read public capabilities, free allowances, access bootstrap, privacy, retention and HTTP discovery routes. No access credential required.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_job ~48
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_result_reference ~48
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.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_capability ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | Exact canonical service_id from capability search, at most 96 UTF-8 bytes. Never a URL or credential. |
Structured output declared, but exposes no named fields.
No examples provided.
revoke_result_reference ~42
Owner revokes future retrieval through one shared result reference. Repeating this action is safe; previously downloaded copies cannot be recalled.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_capabilities ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | Nonblank query of at most 160 UTF-8 bytes. Deterministic keyword matching over maintained Wever services only. |
Structured output declared, but exposes no named fields.
No examples provided.
submit_audit ~301
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.
| Name | Type | Req | Description |
|---|---|---|---|
| csv_text | string | yes | 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 | yes | Ordered expected records; field names and values are strings of at most 4096 UTF-8 bytes each. |
| request_key | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
submit_csv ~98
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.
| Name | Type | Req | Description |
|---|---|---|---|
| csv_text | string | yes | At most 16 KiB UTF-8 and 100 data records |
| request_key | string | yes | Stable idempotency key shared across CSV and audit. Reuse only with identical input for the same capability. |
| schema | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.