MCP servers › com.paidhandshake › exchange
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
com.paidhandshake/exchange
Verified agent commerce plus worker-published structured intelligence and machine payments. — the publisher's description
Summary
com.paidhandshake/exchange is a remote MCP server listed in the official MCP registry at version 2.9.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 18 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 18
- Described as changing data
- 4 of 18 toolsAI-classified
- Mainly works on
- accounts and data in outside web services; money, payments or tradingAI-classified
- Topic
- commerce-and-marketingAI-classified
- Pricing
- usage-basedAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (create_checkout, create_recurring_paid_watch, set_recurring_paid_watch). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 4 tools are described as changing something (create_checkout, submit_paid_machine_job, create_recurring_paid_watch, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 2.9.0, published 2026-10-07 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-05 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 14 versions listed, 2026-10-05 to 2026-10-07; 14 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 12 versions
2.9.0· 2026-10-072.8.0· 2026-10-062.7.1· 2026-10-062.7.0· 2026-10-062.6.2· 2026-10-062.6.1· 2026-10-062.6.0· 2026-10-062.5.1· 2026-10-052.5.0· 2026-10-052.4.1· 2026-10-052.4.0· 2026-10-052.3.3· 2026-10-05
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-22
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 2.9.0 (published 2026-10-07).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services; money, payments or trading.
4 of 18 tools are described as changing something (creating, editing, deleting, sending or running).
- get_fulfillment_proofreads or searches
“Free, read-only operational proof that PaidHandshake has active fulfillment capacity.”
Takes no inputs.
- get_live_inventoryreads or searches
“Free, read-only snapshot of canonical PaidHandshake inventory feeds, including paid-eligible counts, quality holds, freshness, prices and sample URLs.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_published_intelligence_catalogreads or searches
“Free, read-only catalog of structured intelligence products published by connected workers, including paid-eligible counts, prices, sample paths and x402 purchase routes.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_published_intelligence_samplereads or searches
“Free, read-only sample of one worker-published intelligence product.”
1 input, 1 required
productstringrequired“Exact published-intelligence product key from get_published_intelligence_catalog.”
- get_free_data_samplereads or searches
“Free, read-only preview of one canonical PaidHandshake inventory feed.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
feedstringrequired“PaidHandshake feed slug”
“Read-only discovery search across current public or authorized web information when the request is not already covered by a known PaidHandshake inventory product.”
1 input, 1 required
querystringrequired“Natural-language discovery request, 3-600 characters.”
- get_unlock_quotereads or searches
“Free, read-only pricing lookup for locked results from an existing search_matches search.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
search_idstringrequired“Reusable PaidHandshake search identifier returned by search_matches.”
“Create a Stripe Checkout URL after a PaidHandshake search when a buyer wants to authorize access to locked results.”
3 inputs, 2 required
search_idstringrequired“Reusable search identifier returned by search_matches for the result set being purchased.”packagestringrequired“Result package to purchase: single unlocks one selected result, top3 unlocks the next three ranked results, and full unlocks the full available result pack.”result_idinteger“Required only when package=single.”
- quote_paid_machine_jobreads or searches
“Free, read-only price estimate for delegated machine work before any job is submitted or money is reserved.”
2 inputs, 1 required
task_typestringrequired“Requested work category or intent label, such as event_search, bid_search, vendor_search, grant_search, deep_research, or another descriptive task label.”constraintsobject“Optional task-specific requirements such as location, date range, maximum results, verification requirements, exclusions, budget, or other execution constraint…”
- get_machine_payment_optionsreads or searches
“Free, read-only discovery of machine payment rails available or activation-ready for PaidHandshake, including Stripe-funded delegated wallets and x402 Base-USDC where active.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_machine_onboardingreads or searches
“Free, read-only onboarding guide for autonomous buyers.”
Takes no inputs.
- submit_paid_machine_jobdescribed as changing data
“Authenticated paid mutation that submits a one-time machine job after the buyer has accepted the task and spending cap.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 2 required
querystringrequired“Natural-language task to execute.”task_typestring“Optional routing label describing the work category or intent.”max_price_centsintegerrequired“Maximum amount in USD cents this machine authorizes for this single job.”idempotency_keystring“Optional caller-generated stable key for the same intended paid submission.”constraintsobject“Optional structured task requirements such as location, date range, maximum results, verification requirements, exclusions, budget or other execution limits.”
Show 6 more tools
- get_paid_machine_jobreads or searches
“Authenticated, read-only polling for a previously submitted paid machine job.”
1 input, 1 required
job_idstringrequired“PaidHandshake job identifier returned by submit_paid_machine_job.”
- create_recurring_paid_watchcreates or changes datadescribed as changing data
“Authenticated: create a new recurring paid watch for repeated research or monitoring.”
7 inputs, 2 required
namestring“Optional human-readable label for the watch.”querystringrequired“The recurring research or monitoring request to execute on each scheduled run.”task_typestring“Optional execution category used to route each run to a compatible worker; omit when the query itself is sufficient for routing.”constraintsobject“Optional reusable execution constraints applied to every run, such as location, filters, maximum results, verification requirements, or exclusions.”cadence_minutesinteger“Minutes between scheduled runs.”max_price_centsintegerrequired“Maximum price in USD cents allowed for each individual run before the job is rejected rather than overspending.”run_immediatelyboolean“If true, request an initial run immediately after watch creation; if false or omitted, wait for the normal cadence.”
- list_recurring_paid_watchesreads or searches
“Authenticated, read-only listing of recurring paid watches belonging to the current machine buyer.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- set_recurring_paid_watchcreates or changes datadescribed as changing data
“Authenticated state change for an existing recurring paid watch.”
2 inputs, 2 required
watch_idstringrequired“Existing recurring watch identifier, typically returned by create_recurring_paid_watch or list_recurring_paid_watches.”enabledbooleanrequired“true enables future scheduled executions; false disables future scheduled executions for this watch.”
- get_machine_walletreads or searches
“Authenticated, read-only wallet status for the current machine buyer.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_paidhandshake_capabilitiesreads or searches
“Free, read-only capability map for PaidHandshake Exchange.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 18 tools
- Says what it returns
- 100% of 15 tools
- States limits, defaults or errors
- 100% of 1 tool
- Says when to use it
- 100% of 18 tools
- Items covered per tool
- 4.0 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 24
- Tools with a description
- 100% of 18
- Typical description length
- 359 characters
The tool set
Counted from the listing
- Tools
- 18
- Size of the list
- about 3,652 tokens for an agent to load (characters ÷ 4)
- Naming
- 18 of 18 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 18 of 18 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://paidhandshake.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"exchange": {
"url": "https://paidhandshake.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"exchange": {
"type": "http",
"url": "https://paidhandshake.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"exchange","type":"http","url":"https://paidhandshake.com/mcp"}'Claude Code
claude mcp add --transport http exchange https://paidhandshake.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://paidhandshake.com/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint paidhandshake.com/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about com.paidhandshake/exchange
Answered from the data aboveIs com.paidhandshake/exchange safe to install?
We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 4 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is com.paidhandshake/exchange free to use?
Its website (paidhandshake.com/) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Does com.paidhandshake/exchange need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.paidhandshake/exchange been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
What can com.paidhandshake/exchange do?
It lists 18 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data and move money. We did not call any tool, so this describes the text, not the behaviour.
Can com.paidhandshake/exchange change or delete data?
4 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.Dudude-bit/yandex-lavka-mcpalso has tools that creates or changes data, moves money, reads or searchescompare with this one
- app.himalayas/mcpHimalayas Remote Jobsalso has tools that creates or changes data, moves money, reads or searchescompare with this one
- io.github.YawLabs/lemonsqueezy-mcpLemonSqueezy MCP Serveralso has tools that creates or changes data, moves money, reads or searchescompare with this one
- io.github.markswendsen-code/ubereatsalso has tools that creates or changes data, moves money, reads or searchescompare with this one
- io.github.hermoso-ai/hermosoHermosoalso has tools that creates or changes data, moves money, reads or searchescompare with this one
- io.github.the402ai/mcp-serveralso has tools that creates or changes data, moves money, reads or searchescompare with this one
Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 2,838 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 18 tools, 0 resources, 0 prompts.
- 7,378 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Start free. Pay only when the extra verified depth is useful.”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.paidhandshake/exchange: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.paidhandshake/exchange
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.paidhandshake/exchange)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology