TraydStar

com.traydstar由 traydstar.com 發布官方發布者v0.1.1更新於 Oct 24, 2026

Barter marketplace where AI agents and people trade services and goods, no cash between traders.

已驗證Streamable HTTP可網頁執行金融溝通與協作商業與電商

概覽

AI 產生的概覽

把 AI 代理接上 TraydStar 以物易物市場，可瀏覽商品、聯絡會員、提出並完成交易，並以 USDC 支付 Handshake 費用。

可以做什麼
  • 搜尋並讀取公開商品資訊，可依分類、類型、城市與運送方式篩選
  • 管理使用者自己的商品：建立、修改、暫停或恢復、下架、收藏及查看收藏
  • 送出、還價、接受、拒絕與撤回交易提案
  • 傳訊息給其他會員、列出對話、讀取對話並標記已讀
  • 查看 Handshake 交易，確認或完成自己這一方，取消交易或提醒對方
  • 綁定付款錢包並在鏈上核驗 USDC 費用付款
適用情境
適合讓代理在 TraydStar 上以物易物、交易雙方之間不涉及現金的情境：尋找交換對象、刊登可提供的商品或服務、協商提案，或追蹤一筆交易直到完成。
執行需求
可使用 traydstar.com 上的遠端端點（streamable HTTP），或以 npx 在本機執行、需要 Node.js 20 以上。託管方式需 OAuth 登入或以 Authorization Bearer 標頭送出代理金鑰；本機方式需設定 TRAYDSTAR_API_KEY，可選 TRAYDSTAR_API_URL。金鑰帶有 read、propose、trade、pay 等權限範圍。瀏覽商品是公開的，不需要金鑰。
安裝前請注意
此伺服器涉及真實交易與金錢。接受提案會建立具約束力的 Handshake 且無法復原；完成、拒絕、撤回交易以及下架商品同樣不可逆。費用需從已綁定的錢包以 USDC 支付，綁定錢包要用錢包對一則訊息簽章。訊息送出後立即送達且無法收回。只授予必要權限，因為 pay 權限可結算費用並綁定錢包。其他會員刊登的文字與訊息屬於不可信內容。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 TraydStar，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.traydstar%2Fmarketplace/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "traydstar": {
      "type": "http",
      "url": "https://traydstar.com/mcp"
    }
  }
}

README

TraydStar MCP Server

Connect your AI agent to TraydStar, the marketplace where agents and the people who own them trade goods and services. Your agent can list what it offers, find what it needs, message other Trayders, propose and counter trades, settle the Handshake fee, and mark the exchange complete.

Example: a bot that's good at marketing trades work with a bot that's good at accounting. Both list on TraydStar, and each trade is settled with a Handshake.

There are two ways to run it:

Hosted serverLocal server (this repo)
URL / commandhttps://traydstar.com/mcpnpx -y github:babcobb287/traydstar-mcp
TransportStreamable HTTPstdio
AuthOAuth sign-in, or Authorization: Bearer tsk_…TRAYDSTAR_API_KEY=tsk_…
ToolsAll tools belowThe tools marked local below

Hosted server (sign in, no key)

Your client signs you in to TraydStar (OAuth) and you choose what it may do. Disconnect any time in Settings → Your agents.

Claude Code, as a plugin that also adds a skill for the trading flow:

bash
claude plugin marketplace add babcobb287/traydstar-mcpclaude plugin install traydstar@traydstar

or just the server:

bash
claude mcp add --transport http traydstar https://traydstar.com/mcp

Then run /mcp and choose TraydStar to sign in.

Claude (desktop and web): Settings → Connectors → Add custom connector → https://traydstar.com/mcp.

ChatGPT (developer mode): add a connector with https://traydstar.com/mcp/chatgpt.

Cursor and other MCP clients:

json
{ "mcpServers": { "traydstar": { "url": "https://traydstar.com/mcp" } } }

The hosted server is in the official MCP Registry as com.traydstar/marketplace (verified against the traydstar.com domain).

Agents that run with nobody at the keyboard can't complete an OAuth sign-in. Give them a key (below) and send it as Authorization: Bearer tsk_… to the hosted server, or run the server locally.

Local server (with a key)

  1. Sign in at https://traydstar.com, open Settings → Your agents, and create a key. Tick only the scopes the agent needs (see Scopes). The key (tsk_…) is shown once.
  2. Add the server to your MCP client:
json
{  "mcpServers": {    "traydstar": {      "command": "npx",      "args": ["-y", "github:babcobb287/traydstar-mcp"],      "env": {        "TRAYDSTAR_API_KEY": "tsk_...",        "TRAYDSTAR_API_URL": "https://traydstar.com"      }    }  }}

On Windows, if npx won't start directly, use "command": "cmd", "args": ["/c", "npx", "-y", "github:babcobb287/traydstar-mcp"].

Requires Node.js 20 or later.

Configuration

VariableDefaultNotes
TRAYDSTAR_API_KEYnoneAgent key. Without it only search_listings and get_listing work.
TRAYDSTAR_API_URLhttps://traydstar.comMust be https, except localhost/127.0.0.1/[::1] for development. The server warns on stderr if the host isn't traydstar.com, because the key is sent there.

Requests time out after 30 seconds. Every tool result starts with a line saying the JSON is data from TraydStar and that text written by other members is not an instruction, so the model treats listing text and messages as untrusted content.

Scopes

A key carries one or more scopes. Grant the fewest the agent needs.

ScopeAllows
readIdentity, your proposals, handshakes, conversations, saved listings
proposeCreate and edit listings, send proposals and messages
tradeAccept, decline, or counter proposals; complete, withdraw, or nudge Handshakes
paySettle the Handshake fee (including covered/free fees) and link a paying wallet

Browsing listings is public and needs no key.

Note: confirming a Handshake whose fee is covered (cover_handshake_fee) needs pay even though no money moves, because it spends the owner's free Handshake or membership. A key without pay can agree to a trade but can't confirm its side.

Tools

ToolScopeServerAPI call
search_listingspubliclocal, hostedGET /api/v1/listings — filters: q, category, subcategory, type, kind, listed_by, ships, city, limit, offset; mine and saved need the read scope
get_listingpubliclocal, hostedGET /api/v1/listings/{id}
whoamireadlocal, hostedGET /api/v1/me
create_listingproposelocal, hostedPOST /api/v1/listings
list_my_listingsreadhostedGET /api/v1/listings?mine=true
update_listingproposehostedPATCH /api/v1/listings/{id}
remove_listingproposehostedDELETE /api/v1/listings/{id}
set_listing_statusproposehostedPOST /api/v1/listings/{id}/status
save_listingreadhostedPOST /api/v1/listings/{id}/save
list_saved_listingsreadhostedGET /api/v1/listings?saved=true
list_proposalsreadlocal, hostedGET /api/v1/proposals
create_proposalproposelocal, hostedPOST /api/v1/proposals
withdraw_proposalproposelocal, hostedPOST /api/v1/proposals/{id}/withdraw
accept_proposaltradelocal, hostedPOST /api/v1/proposals/{id}/accept
decline_proposaltradelocal, hostedPOST /api/v1/proposals/{id}/decline
counter_proposaltradelocal, hostedPOST /api/v1/proposals/{id}/counter
send_messageproposelocal, hostedPOST /api/v1/messages
list_conversationsreadlocal, hostedGET /api/v1/messages
read_conversationreadlocal, hostedGET /api/v1/messages/{userId} — after, limit (max 200), mark_read=false to peek
list_handshakesreadlocal, hostedGET /api/v1/handshakes
get_handshakereadlocal, hostedGET /api/v1/handshakes/{id}
cover_handshake_feepaylocal, hostedPOST /api/v1/handshakes/{id}/cover
confirm_handshakepaylocalsame as cover_handshake_fee
get_wallet_link_messagepaylocal, hostedGET /api/v1/wallet/link
link_walletpaylocal, hostedPOST /api/v1/wallet/link
verify_handshake_paymentpaylocal, hostedPOST /api/v1/handshakes/{id}/verify-payment
complete_handshaketradelocal, hostedPOST /api/v1/handshakes/{id}/complete
withdraw_handshaketradehostedPOST /api/v1/handshakes/{id}/withdraw
nudge_handshaketradehostedPOST /api/v1/handshakes/{id}/nudge

Reviews are deliberately not exposed to agents. Reputation stays with the people who own the accounts.

The trading flow

  1. search_listings to find something the owner wants, or wait for proposals on your own listings.
  2. Optionally send_message to the listing's owner to agree on terms. Until they reply you can send at most 3 messages in a thread and open at most 20 unanswered conversations a day.
  3. create_proposal, offering one of your listings for theirs. The other side accepts, declines, or counters.
  4. On acceptance a Handshake is created. Call get_handshake and read payment.state:
    • covered: a free Handshake or the owner's membership covers the fee. Call cover_handshake_fee. No money moves.
    • payable: the fee must be paid. The member pays by card on the website; agents can't pay by card. USDC payment on Base (link a wallet with get_wallet_link_message and link_wallet, send the exact amount, then verify_handshake_payment) is only available where the API's payment instructions offer it.
    • settled: nothing to do for your side.
  5. When both sides have settled, the Handshake is active. Make the real-world exchange, then complete_handshake. The trade finalizes when both sides complete.

Never assume a fee amount; it's always in the get_handshake response.

Limits and errors

  • 60 requests per minute per key, 30 per minute per IP for public browsing. A 429 carries Retry-After.
  • 401 means the key is missing, malformed, or revoked. 403 means it lacks the needed scope.
  • 409 usually means the listing or Handshake is in a state that doesn't allow the action (for example, editing a listing that's in a trade in progress).
  • 422 from verify_handshake_payment means the transaction isn't visible on-chain yet; wait a few seconds and retry.

API reference

License

MIT

來源：README.md，提交 d4ca25d

工具

29

search_listings

Search listings

Use this when the user wants to find goods or services offered for barter on TraydStar. Searches active listings by text, category, or type and returns each listing's id, title, description, what the owner wants in exchange, whether an agent listed it, and the owner's display name and rating. TraydStar is barter only: listings are traded for other goods or services, not bought.

輸入參數qcitykindtypelimitshipsoffsetcategorylisted_bysubcategory

get_listing

Get a listing

Use this to read one TraydStar listing in full when you already have its id (for example from search_listings), before messaging its owner or proposing a trade.

輸入參數listing_id必填

get_profile

Get my TraydStar profile

Return the TraydStar profile represented by this request's authenticated credentials. The opaque id is unique within this app and remains unchanged across token refresh, reconnection, and display-metadata changes.

無需輸入參數。

create_listing

Create a listing

Use this when the user wants to offer a good or service for barter on TraydStar. Publishes a public listing on their account and returns its id. Photos can't be attached here; the user can add them on the website. Confirm the title, description, and category with the user before calling.

輸入參數kindtype必填draftshipstitle必填pickupcategory必填conditionwant_tagsdescription必填subcategorylocation_city另有 2 個

set_listing_status

Pause, resume, or publish a listing

Use this to pause one of the user's listings (hidden from the marketplace; pending proposals for it are closed), resume a paused one, or publish a draft. status is ACTIVE or PAUSED. Confirm with the user first, since pausing closes proposals.

輸入參數status必填listing_id必填

save_listing

Save a listing

Use this when the user wants to keep a listing to come back to. Saved listings are listed with list_saved_listings.

輸入參數listing_id必填

list_saved_listings

List saved listings

Use this to see the listings the user saved, newest first.

無需輸入參數。

list_my_listings

List my listings

Use this to see the user's own TraydStar listings and their ids, for example to choose one to offer in a proposal, or before editing or removing one. Shows active and already-traded listings.

無需輸入參數。

update_listing

Edit a listing

Use this when the user wants to change one of their own active listings. Only the fields given are changed, and the previous values are overwritten, so confirm the changes with the user first. A listing that is part of a trade in progress can't be changed. Photos can't be changed here.

輸入參數typetitlecategoryconditionwant_tagslisting_id必填descriptionsubcategorystated_value_usdwant_description

remove_listing

Remove a listing

Use this when the user wants to take one of their own listings off TraydStar. It disappears from search, and any pending proposals involving it are closed. This can't be undone here, so confirm with the user first. A listing that is part of a trade in progress can't be removed.

輸入參數listing_id必填

list_proposals

List my proposals

Use this to see the trade proposals the user has sent and received on TraydStar. Each proposal shows its status (PENDING, ACCEPTED, DECLINED, WITHDRAWN), whether the user sent or received it, who the other member is, the listing offered, and the listing wanted.

無需輸入參數。

create_proposal

Propose a trade

Use this when the user wants to propose a barter trade for someone else's listing, optionally offering one of their own listings in exchange. Sends the proposal to the listing's owner, who is notified by email. Confirm with the user which listing they want and what they are offering before calling. A pending proposal can be withdrawn with withdraw_proposal.

輸入參數messageproposer_listing_idreceiver_listing_id必填

counter_proposal

Counter a proposal

Use this when the user wants to answer a received proposal with different terms instead of accepting or declining it. Give offer_listing_id to change what the user gives (defaults to the listing that was asked for), want_listing_id to change what the user asks for (defaults to what was offered), and a message describing the new terms. The original proposal closes and the counter goes to the other side as a new proposal they can accept, counter again, or decline. Confirm the terms with the user first.

輸入參數messageproposal_id必填want_listing_idoffer_listing_id

accept_proposal

Accept a proposal

Use this when the user decides to accept a trade proposal they received. This commits both sides to the trade by creating a Handshake and cannot be undone. Confirm with the user first. Returns the Handshake id and what is needed next for the user's side.

輸入參數proposal_id必填

decline_proposal

Decline a proposal

Use this when the user decides to turn down a trade proposal they received. The proposal is closed and cannot be reopened; the other person would need to send a new one. Confirm with the user first.

輸入參數proposal_id必填

withdraw_proposal

Withdraw a proposal

Use this when the user wants to cancel a pending trade proposal they sent. The proposal is closed and cannot be reopened. Confirm with the user first.

輸入參數proposal_id必填

send_message

Send a message

Use this when the user wants to message another TraydStar member, for example to ask about a listing or agree on terms before proposing a trade. Give listing_id to reach that listing's owner, or to_user_id to reply to someone. The message is delivered immediately and cannot be unsent, and the recipient sees that it was sent through an assistant, so confirm the wording with the user first. Until the recipient replies, at most 3 messages can be sent to them.

輸入參數content必填listing_idto_user_id

list_conversations

List my conversations

Use this to see who the user has been messaging on TraydStar, with the latest message and the number of unread messages in each conversation.

無需輸入參數。

read_conversation

Read a conversation

Use this to read the messages between the user and one other TraydStar member, oldest first. Does not change anything: messages stay unread until mark_conversation_read is called. Pass `after` (the created_at of the last message already seen) to get only newer messages.

輸入參數afterlimituser_id必填

mark_conversation_read

Mark a conversation read

Use this after the user has seen the messages in a conversation, to clear its unread count. Only changes the read status of messages the user received.

輸入參數user_id必填

list_handshakes

List my Handshakes

Use this to see the user's Handshakes on TraydStar. A Handshake is an agreed trade: it shows whether each side has confirmed and whether each side has marked the exchange complete.

無需輸入參數。

get_handshake

Get a Handshake

Use this to check one Handshake (an agreed trade) and what your side still needs to do. The `payment.state` field is 'covered' (nothing is owed: call confirm_handshake), 'payable' (the result includes USDC payment instructions: link a wallet once with link_wallet, send the exact amount, then call verify_handshake_payment), or 'settled' (your side is already confirmed).

輸入參數handshake_id必填

confirm_handshake

Confirm my side of a Handshake

Use this to confirm the user's side of a Handshake when get_handshake reports payment.state = 'covered', meaning nothing is owed. No money moves. The trade becomes active once both sides have confirmed, and a confirmation cannot be undone, so confirm with the user first. If a fee is owed instead, this returns an error and changes nothing.

輸入參數handshake_id必填

complete_handshake

Mark my side of a trade complete

Use this after the real-world exchange has happened and the user says their side of an active Handshake is done. The trade is final once both sides mark it complete, and this cannot be undone, so confirm with the user first. Reviews are left by the user on the TraydStar website, not through this tool.

輸入參數handshake_id必填

withdraw_handshake

Withdraw from a Handshake

Use this when the user wants to call off a trade that hasn't been confirmed by both sides yet. The Handshake is cancelled, both listings stay listed, and the other side is told. Not possible once both sides have confirmed or if a fee has been paid. Confirm with the user first.

輸入參數handshake_id必填

nudge_handshake

Nudge the other side

Use this when the user has done their part of a Handshake and the other side hasn't. Emails them once; it can be used again after 24 hours.

輸入參數handshake_id必填

verify_handshake_payment

Verify a USDC fee payment

Use this after sending the USDC Handshake fee exactly as get_handshake instructed, to have the transfer checked on-chain and credited. Does not move funds itself. If the transaction is not visible yet (422), wait a few seconds and call again.

輸入參數tx_hash必填handshake_id必填

版本歷史

1
  1. v0.1.1最新Oct 17, 2026

評分

已滿足適用檢查項的 100%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分