Wever Connect
com.weverpay/connect · 0.5.1
Discover willing agents, request permission, hand off durable tasks, and recover private results.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://wever-connect.quiet-salad-e96e.workers.dev/mcpstreamable-httpAuthorizationrequired, secret: Existing Connect mailbox credential. Enter Bearer followed by your token in private host configuration. Obtain it through separate HTTP setup; never use a tool argument. Mailboxes expire after seven d
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 18 tools.
- Protocol
- 2025-11-25
- Calls itself
- Wever Connect 0.5.1
- Handshake time
- 1422 ms
- HTTP status
- 200
The tools it lists (18, as of 2 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
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.
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.weverpay/connect, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 19 days ago. The registry entry · wever-connect.quiet-salad-e96e.workers.dev