MCP servers › com.traydstar › marketplace
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
com.traydstar/marketplace
Barter marketplace where AI agents and people trade services and goods, no cash between traders. — the publisher's description
Summary
com.traydstar/marketplace is a remote MCP server listed in the official MCP registry at version 0.1.1. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 29 tools, 0 resources and 0 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: 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: 0 stars (ranked from 10)
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
- Repository
- public
- Tools
- 29
- Described as changing data
- 18 of 29 toolsAI-classified
- Mainly works on
- accounts and data in outside web servicesAI-classified
- Topic
- commerce-and-marketingAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 16 tools whose name or declaration suggests they change data (create_listing, set_listing_status, save_listing, update_listing, remove_listing and 11 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 18 tools are described as changing something (create_listing, set_listing_status, save_listing, …): 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
- 0.1.1, published 2026-10-16 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-10-16; 2 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.1.1· 2026-10-160.1.0· 2026-10-16
- 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 0.1.1 (published 2026-10-16).
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.
18 of 29 tools are described as changing something (creating, editing, deleting, sending or running).
“Use this when the user wants to find goods or services offered for barter on TraydStar.”
Publisher declares: read-only yes · destructive no · open-world no
10 inputs
qstring“Words to look for in the title or description”categorystring“Limit to one category”subcategorystring“Limit to a subcategory within the category”typestring“Physical goods, services, or listings that offer both”listed_bystring“Only listings created by an agent acting for a member, or only those created by the member directly”kindstring“offer = things on offer; wanted = ads from members looking for something”shipsboolean“Only listings whose owner will ship”citystring“Only listings located in a city containing this text”limitinteger“How many results to return (default 20)”offsetinteger“Skip this many results, for paging; page until has_more is false”
“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.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
listing_idstringrequired“The listing's id”
“Return the TraydStar profile represented by this request's authenticated credentials.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“Use this when the user wants to offer a good or service for barter on TraydStar.”
Publisher declares: read-only no · destructive no · open-world yes
14 inputs, 4 required
titlestringrequired“Short name of what is offered”descriptionstringrequired“What is offered, in the user's words”typestringrequired“GOOD for a physical item, SERVICE for work, BOTH if it includes both”categorystringrequired“The category it belongs in”subcategorystring“A subcategory of that category, if one applies”conditionstring“Condition, for physical goods”want_tagsarray“Short tags for what the user wants in exchange”want_descriptionstring“What the user would like in exchange”stated_value_usdnumber“The user's own estimate of its value in US dollars, used to match fair trades”kindstring“offer (default) for something the user has; wanted for something the user is looking for, with want fields describing what they would give”pickupboolean“Can be handed over in person (default true)”shipsboolean“The user will ship it (default false)”location_citystring“City shown on the listing”draftboolean“true saves it unpublished; publish later with set_listing_status”
“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.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 2 required
listing_idstringrequired“The user's listing”statusstringrequired“ACTIVE to publish or resume, PAUSED to hide”
“Use this when the user wants to keep a listing to come back to.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
listing_idstringrequired“The listing to save”
“Use this to see the listings the user saved, newest first.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“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.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“Use this when the user wants to change one of their own active listings.”
Publisher declares: read-only no · destructive yes · open-world yes
10 inputs, 1 required
listing_idstringrequired“The user's listing to change”titlestring“New title”descriptionstring“New description”typestring“GOOD, SERVICE, or BOTH”categorystring“New category”subcategorystring“A subcategory of the listing's category”conditionstring“Condition, for physical goods”want_tagsarray“Replaces the tags for what the user wants in exchange”want_descriptionstring“What the user would like in exchange”stated_value_usdnumber“The user's own estimate of its value in US dollars”
“Use this when the user wants to take one of their own listings off TraydStar.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
listing_idstringrequired“The user's listing to remove”
“Use this to see the trade proposals the user has sent and received on TraydStar.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“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.”
Publisher declares: read-only no · destructive no · open-world yes
3 inputs, 1 required
receiver_listing_idstringrequired“The listing the user wants”proposer_listing_idstring“The user's own listing offered in exchange”messagestring“A note to the listing's owner”
Show 17 more tools
- counter_proposalcreates or changes datadescribed as changing data
“Use this when the user wants to answer a received proposal with different terms instead of accepting or declining it.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs, 1 required
proposal_idstringrequired“The received proposal to counter”offer_listing_idstring“One of the user's listings to give”want_listing_idstring“One of the other member's listings to ask for”messagestring“The changed terms, in the user's words”
“Use this when the user decides to accept a trade proposal they received.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
proposal_idstringrequired“The proposal to accept”
- decline_proposaldeletesdescribed as changing data
“Use this when the user decides to turn down a trade proposal they received.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
proposal_idstringrequired“The proposal to decline”
“Use this when the user wants to cancel a pending trade proposal they sent.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
proposal_idstringrequired“The pending proposal to withdraw”
“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.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 1 required
to_user_idstring“The member to message”listing_idstring“The listing the message is about; reaches its owner if to_user_id is omitted”contentstringrequired“The message text”
“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.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“Use this to read the messages between the user and one other TraydStar member, oldest first.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
user_idstringrequired“The other member in the conversation”afterstring“Only return messages after this time (ISO 8601)”limitinteger“How many messages to return (default 100, newest)”
“Use this after the user has seen the messages in a conversation, to clear its unread count.”
Publisher declares: read-only no · destructive no · open-world no
1 input, 1 required
user_idstringrequired“The other member in the conversation”
- list_handshakesreads or searches
“Use this to see the user's Handshakes on TraydStar.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
- get_handshakereads or searches
“Use this to check one Handshake (an agreed trade) and what your side still needs to do.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
handshake_idstringrequired“The Handshake's id”
- confirm_handshakecreates or changes datadescribed as changing data
“Use this to confirm the user's side of a Handshake when get_handshake reports payment.state = 'covered', meaning nothing is owed.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
handshake_idstringrequired“The Handshake to confirm”
- complete_handshakecreates or changes datadescribed as changing data
“Use this after the real-world exchange has happened and the user says their side of an active Handshake is done.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
handshake_idstringrequired“The active Handshake to mark complete”
- withdraw_handshakedeletesdescribed as changing data
“Use this when the user wants to call off a trade that hasn't been confirmed by both sides yet.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
handshake_idstringrequired“The Handshake to withdraw from”
- nudge_handshakesends messagesdescribed as changing data
“Use this when the user has done their part of a Handshake and the other side hasn't.”
Publisher declares: read-only no · destructive no · open-world yes
1 input, 1 required
handshake_idstringrequired“The Handshake the user is waiting on”
- get_wallet_link_messagereads or searches
“Use this before paying a Handshake fee in USDC for the first time.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
“Use this to link the wallet that will pay Handshake fees, by submitting a signature over the message from get_wallet_link_message.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 3 required
addressstringrequired“The wallet address”messagestringrequired“The exact message returned by get_wallet_link_message”signaturestringrequired“The EIP-191 signature of that message”
- verify_handshake_paymentcreates or changes datadescribed as changing data
“Use this after sending the USDC Handshake fee exactly as get_handshake instructed, to have the transfer checked on-chain and credited.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 2 required
handshake_idstringrequired“The Handshake the fee is for”tx_hashstringrequired“The transaction hash of the USDC transfer”
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 29 tools
- Says what it returns
- 45% of 29 tools
- States limits, defaults or errors
- 7% of 29 tools
- Says when to use it
- 95% of 22 tools
- Items covered per tool
- 2.5 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 66
- Tools with a description
- 100% of 29
- Typical description length
- 251 characters
The tool set
Counted from the listing
- Tools
- 29
- Size of the list
- about 9,108 tokens for an agent to load (characters ÷ 4)
- Naming
- 29 of 29 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 29 of 29 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://traydstar.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"marketplace": {
"url": "https://traydstar.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"marketplace": {
"type": "http",
"url": "https://traydstar.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"marketplace","type":"http","url":"https://traydstar.com/mcp"}'Claude Code
claude mcp add --transport http marketplace https://traydstar.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://traydstar.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 traydstar.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 |
| Repository github.com/babcobb287/traydstar-mcp | Opens publicly | matches | api.github.com · 2026-10-22 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.traydstar
- GitHub owner
- a personal account (babcobb287)
- Repository
- github.com/babcobb287/traydstar-mcp
- Stars
- 0
- Repository age
- 31–90 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-22; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- 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.traydstar/marketplace
Answered from the data aboveIs com.traydstar/marketplace safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 18 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.
Does com.traydstar/marketplace 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.traydstar/marketplace been security tested?
Partly. 3 of the 15 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.traydstar/marketplace do?
It lists 29 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, delete and send messages. We did not call any tool, so this describes the text, not the behaviour.
Can com.traydstar/marketplace change or delete data?
18 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.
Does com.traydstar/marketplace publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of com.traydstar/marketplace?
In github.com/babcobb287/traydstar-mcp, which opens publicly.
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
- com.mcparmory/klaviyoalso has tools that creates or changes data, deletes, reads or searches, sends messagescompare with this one
- com.mcparmory/shopify-adminalso has tools that creates or changes data, deletes, reads or searches, sends messagescompare with this one
- app.himalayas/mcpHimalayas Remote Jobsalso has tools that creates or changes data, deletes, reads or searches, sends messagescompare with this one
- io.github.benkaiser/mob-demoMob (Demo)also has tools that creates or changes data, deletes, reads or searches, sends messagescompare with this one
- io.github.DeviceIngineering/ozon-mcp-serveralso has tools that creates or changes data, deletes, reads or searches, sends messagescompare with this one
- io.github.awesomemotive/pushengage-mcpPushEngagealso has tools that creates or changes data, deletes, reads or searches, sends messagescompare 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: exercised
3 exercised12 not run (reason given)3 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 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 - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.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
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
- 1,885 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 29 tools, 0 resources, 0 prompts.
- 5,247 msFinished: 3 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.
“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.traydstar/marketplace: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.traydstar/marketplace
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.traydstar/marketplace)
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