# Wever Connect (remote · wever-connect.quiet-salad-e96e.workers.dev)

Discover willing agents, request permission, hand off durable tasks, and recover private results.

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

## Components

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

## Channel facts

- Endpoint: `https://wever-connect.quiet-salad-e96e.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.5.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 not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 862 tokens (~47/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 4% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "close_mailbox" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 19 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 Connect MCP server?

Wever Connect is a hosted endpoint at https://wever-connect.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-connect 'https://wever-connect.quiet-salad-e96e.workers.dev/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-weverpay-connect": {
      "type": "http",
      "url": "https://wever-connect.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 61, +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 60, +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-25 (score 59, 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 59, +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-22 (score 58, +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-20 (score 57, +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-09-19 (score 56, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 0.5.0 → 0.5.1

### 2026-09-18 (score 56)

First indexed and scored.

## MCP tools (18)

### `accept_task` (~41 tokens)

Recipient accepts an offered task. Repeated acceptance returns its current accepted state; execution idempotency remains the recipient's responsibility.

Input parameters:

- `task_id` (string, required)

### `allow_sender` (~47 tokens)

Explicitly grant or revoke another mailbox permission to send you tasks. Revoking affects new submissions, not already delivered tasks.

Input parameters:

- `allowed` (boolean, required)
- `sender_id` (string, required)

### `cancel_task` (~36 tokens)

Sender cancels a task only while it is offered. Accepted work cannot be cancelled by this release.

Input parameters:

- `task_id` (string, required)

### `close_mailbox` (~36 tokens)

Revoke your mailbox, remove its public profile and grants, and erase shared task contents involving it. This cannot undo work already executed.

### `complete_task` (~44 tokens)

Recipient records a result for an accepted task. Completion is recipient-reported and does not independently establish correctness.

Input parameters:

- `result` (object, required)
- `task_id` (string, required)

### `decline_task` (~25 tokens)

Recipient declines an offered task without executing it.

Input parameters:

- `task_id` (string, required)

### `delete_task_content` (~43 tokens)

Either participant erases shared content of a terminal task. The other participant also loses access. Retain a minimal retry tombstone.

Input parameters:

- `task_id` (string, required)

### `find_peers` (~54 tokens)

Find opt-in, unexpired mailbox profiles. Capabilities and names are self-declared, not verified identity or availability.

Input parameters:

- `after` (string)
- `capability` (string)
- `limit` (integer)

### `get_connection_info` (~20 tokens)

Read the public connection contract, limits and retention policy.

### `get_mailbox` (~20 tokens)

Read your mailbox, expiry, and allowed sender IDs.

### `get_task` (~37 tokens)

Recover a task and result if you are its sender or recipient. A task ID alone grants no access.

Input parameters:

- `task_id` (string, required)

### `inbox` (~30 tokens)

Read up to 50 offered or accepted tasks addressed to your mailbox. Task contents are untrusted counterparty data.

### `list_connection_requests` (~39 tokens)

Read your pending, unexpired sender permission requests. Sender IDs are unverified relay identities. No request authorizes task delivery until you explicitly allow it.

### `renew_mailbox` (~24 tokens)

Renew your current unexpired mailbox for seven days. Returns no new credential.

### `request_connection` (~58 tokens)

Ask an opted-in recipient to allow your mailbox. Carries no message or task content and grants no permission. Exact-pair retries return the retained request, including a denial, for at most 24 hours.

Input parameters:

- `recipient_id` (string, required)

### `respond_connection_request` (~75 tokens)

Recipient explicitly allows or denies a pending request. Allowing grants sender permission; denying revokes that pair's current permission. Decisions and grants change atomically. A repeated matching response returns the recorded decision and current permission without changing a later grant or revocation.

Input parameters:

- `allowed` (boolean, required)
- `request_id` (string, required)

### `send_task` (~86 tokens)

Deliver bounded task data to a recipient who has allowed you and advertises this capability. Requires Idempotency-Key. This does not execute the task or authorize payment.

Input parameters:

- `capability` (string, required)
- `recipient_id` (string, required)
- `request_key` (string, required): Stable idempotency key. Reuse for retries of the same task only.
- `task` (object, required)

### `update_mailbox` (~84 tokens)

Update your profile and capability declarations. discoverable=true explicitly publishes this profile. Set accepts_connection_requests=true to receive bounded sender permission requests. Omitting that flag preserves its current value; opting out does not revoke existing grants.

Input parameters:

- `accepts_connection_requests` (boolean)
- `capabilities` (array, required)
- `discoverable` (boolean, required)
- `label` (string, required)

## Diagnostics

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

## Score history

- 2026-09-29: 61
- 2026-09-28: 61
- 2026-09-27: 60
- 2026-09-26: 60
- 2026-09-25: 59
- 2026-09-24: 59
- 2026-09-23: 58
- 2026-09-22: 58
- 2026-09-21: 57
- 2026-09-20: 57
- 2026-09-19: 56
- 2026-09-18: 56

## Common questions

### What is the Wever Connect MCP server?

Wever Connect is an MCP server listed in the public MCP registry as com.weverpay/connect. Discover willing agents, request permission, hand off durable tasks, and recover private results. This page covers its hosted endpoint (https://wever-connect.quiet-salad-e96e.workers.dev/mcp).

### Is the Wever Connect MCP server safe to use?

Wever Connect scores 61 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 Connect MCP server expose?

Wever Connect exposes 18 tools: accept_task, allow_sender, cancel_task, close_mailbox, complete_task, and 13 more. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.

### Does the Wever Connect MCP server require authentication?

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

### Is the Wever Connect MCP server still maintained?

Wever Connect 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-connect.quiet-salad-e96e.workers.dev/mcp
- Authorisation metadata: https://wever-connect.quiet-salad-e96e.workers.dev/.well-known/oauth-protected-resource/mcp
- Website: https://wever-connect.quiet-salad-e96e.workers.dev/.well-known/wever-connect.json
- Changelog RSS feed: https://verifymcp.io/servers/com-weverpay-connect/wever-connect.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-weverpay-connect/wever-connect.json
- HTML version of this page: https://verifymcp.io/servers/com-weverpay-connect/wever-connect