Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Quietwork Swap

MCP server · qw-swap.quietworklabs.workers.dev · found in a public registry · checked since 2026-10-19

Live, handshake completed · latest check

As JSON

GET https://qw-swap.quietworklabs.workers.dev/mcp

The name is the registry's label, not ours. Not reviewed by a person. See 9 endpoints from quietworklabs.workers.dev.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest32 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-10-19under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Details

Tools listed by the server

crosschain_create_shiftcrosschain_rateshift_statusswap_build_txswap_quote

Tools
5
This list since
2026-10-19
First listed to us
2026-10-19
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/1); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Listing

In the capability tree: Payments and money / Send and swap crypto (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-19. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/4): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR
Live, MCP endpoint answered HTTP 200 32 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_2e48f3221bb5fb80