Wever Connect
REMOTE · WEVER-CONNECT.QUIET-SALAD-E96E.WORKERS.DEV · SCANNED SEP 29
Discover willing agents, request permission, hand off durable tasks, and recover private results.
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 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. See how to fix → View diagnostics → Unverified
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 862 tokens (~47/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 19 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 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.
remote · wever-connect.quiet-salad-e96e.workers.dev
claude mcp add --transport http com-weverpay-connect 'https://wever-connect.quiet-salad-e96e.workers.dev/mcp'
{
"mcpServers": {
"com-weverpay-connect": {
"url": "https://wever-connect.quiet-salad-e96e.workers.dev/mcp"
}
}
} {
"servers": {
"com-weverpay-connect": {
"type": "http",
"url": "https://wever-connect.quiet-salad-e96e.workers.dev/mcp"
}
}
} [mcp_servers.com-weverpay-connect] url = "https://wever-connect.quiet-salad-e96e.workers.dev/mcp"
{
"$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 mcp add com-weverpay-connect --url 'https://wever-connect.quiet-salad-e96e.workers.dev/mcp' --transport streamable-http
mcp_servers:
com-weverpay-connect:
url: "https://wever-connect.quiet-salad-e96e.workers.dev/mcp" {
"McpServers": {
"com-weverpay-connect": {
"Transport": "http",
"Url": "https://wever-connect.quiet-salad-e96e.workers.dev/mcp"
}
}
} assistant mcp add com-weverpay-connect -t streamable-http -u 'https://wever-connect.quiet-salad-e96e.workers.dev/mcp'
{
"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.
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 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.
- 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 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.
- 22 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.
- 20 Sept 26 +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.
- 19 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.5.0 → 0.5.1 functional
- 18 Sept 26 56
First indexed and scored.
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-connect.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-connect.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wever-connect.quiet-salad-e96e.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://wever-connect.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 →
accept_task ~41
Recipient accepts an offered task. Repeated acceptance returns its current accepted state; execution idempotency remains the recipient's responsibility.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
allow_sender ~47
Explicitly grant or revoke another mailbox permission to send you tasks. Revoking affects new submissions, not already delivered tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed | boolean | yes | – |
| sender_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
cancel_task ~36
Sender cancels a task only while it is offered. Accepted work cannot be cancelled by this release.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
close_mailbox ~36
Revoke your mailbox, remove its public profile and grants, and erase shared task contents involving it. This cannot undo work already executed.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
complete_task ~44
Recipient records a result for an accepted task. Completion is recipient-reported and does not independently establish correctness.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
decline_task ~25
Recipient declines an offered task without executing it.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
delete_task_content ~43
Either participant erases shared content of a terminal task. The other participant also loses access. Retain a minimal retry tombstone.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_peers ~54
Find opt-in, unexpired mailbox profiles. Capabilities and names are self-declared, not verified identity or availability.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | – |
| capability | string | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_connection_info ~20
Read the public connection contract, limits and retention policy.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mailbox ~20
Read your mailbox, expiry, and allowed sender IDs.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_task ~37
Recover a task and result if you are its sender or recipient. A task ID alone grants no access.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
inbox ~30
Read up to 50 offered or accepted tasks addressed to your mailbox. Task contents are untrusted counterparty data.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_connection_requests ~39
Read your pending, unexpired sender permission requests. Sender IDs are unverified relay identities. No request authorizes task delivery until you explicitly allow it.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
renew_mailbox ~24
Renew your current unexpired mailbox for seven days. Returns no new credential.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
request_connection ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recipient_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
respond_connection_request ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| allowed | boolean | yes | – |
| request_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
send_task ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | – |
| recipient_id | string | yes | – |
| request_key | string | yes | Stable idempotency key. Reuse for retries of the same task only. |
| task | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_mailbox ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts_connection_requests | boolean | – | – |
| capabilities | array | yes | – |
| discoverable | boolean | yes | – |
| label | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.