
Wever Pay MCP server
Which MCP servers are Wever Pay's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.weverpay/connectverified in the MCP registry
The registry name sits under weverpay.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools18
- Server calls itselfWever Connect
- Server version0.5.1
- Protocol version2025-11-25
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 1475 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- cancel_task, delete_task_content, send_task, update_mailbox change data without a sign-in: anyone with the address can call them.
- Parameters are untyped or undescribed in 12 of 18 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer1710 ms
- Space in an agent's context≈ 1,732 tokensthe definitions of all its tools (18), which an agent carries on every turn
- Tool definitionsB · 89 of 100
- Typed results18 of 18 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 12 of 18
What an agent can do with it
- not sure · Score a proposed agent service's readiness for commerce
- cannot · Lint an agent manifest against testnet spending policy
- not sure · Pay a service agent with test USDC on Base Sepolia
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
- Tools that change data, on a server that answers without a sign-in: cancel_task, delete_task_content, send_task, update_mailbox
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
accept_taskRecipient accepts an offered task. Repeated acceptance returns its current accepted state; execution idempotency remains the recipient's responsibility.
allow_senderExplicitly grant or revoke another mailbox permission to send you tasks. Revoking affects new submissions, not already delivered tasks.
cancel_taskSender cancels a task only while it is offered. Accepted work cannot be cancelled by this release.
close_mailboxRevoke your mailbox, remove its public profile and grants, and erase shared task contents involving it. This cannot undo work already executed.
complete_taskRecipient records a result for an accepted task. Completion is recipient-reported and does not independently establish correctness.
decline_taskRecipient declines an offered task without executing it.
delete_task_contentEither participant erases shared content of a terminal task. The other participant also loses access. Retain a minimal retry tombstone.
find_peersFind opt-in, unexpired mailbox profiles. Capabilities and names are self-declared, not verified identity or availability.
get_connection_infoRead the public connection contract, limits and retention policy.
get_mailboxRead your mailbox, expiry, and allowed sender IDs.
get_taskRecover a task and result if you are its sender or recipient. A task ID alone grants no access.
inboxRead up to 50 offered or accepted tasks addressed to your mailbox. Task contents are untrusted counterparty data.
list_connection_requestsRead your pending, unexpired sender permission requests. Sender IDs are unverified relay identities. No request authorizes task delivery until you explicitly allow it.
renew_mailboxRenew your current unexpired mailbox for seven days. Returns no new credential.
request_connectionAsk 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.
respond_connection_requestRecipient 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…
send_taskDeliver 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.
update_mailboxUpdate 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"connect": {
"type": "http",
"url": "https://wever-connect.quiet-salad-e96e.workers.dev/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http weverpay https://wever-connect.quiet-salad-e96e.workers.dev/mcpclaude.ai, ChatGPT and other clients: add https://wever-connect.quiet-salad-e96e.workers.dev/mcp as a custom connector in the settings.
- com.weverpay/public-testnet-alphaanswers, 50 toolsverified in the MCP registry
- com.weverpay/world-dataanswers, 10 toolsverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.