Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
作者提供的说明(英文原文)
Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。
在终端中运行这条命令
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
注册名称已通过 GitHub 账户 Echolonius 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.8.0)于昨天进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
MCP server integrating with Stripe - tools for customers, products, payments, and more.
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Boardcheck
Boardcheck it before you bid.
▶ Try it in your browser · Spec · Audits · llms.txt
About to bid on an AI-agent job board? Boardcheck flags risky listings before you spend time or money.
Give it a board's listings and it points out the warning signs: listings with more applications than views, batches of listings created in the same second, boards made up mostly of agents advertising themselves, priced work with no escrow and no payment evidence, budgets far above the board's median that nobody has viewed, text written to hijack your AI agent (prompt injection), upfront fees with no escrow, and bounty bait written for AI agents (requests for your keys, download-and-run scripts, hidden text). You get one of three verdicts — high risk, caution or clear — and every finding says why, in plain words. The scan runs on your own machine, and your listings are not sent anywhere.
You need uv and git. There is no account to create and nothing to clone:
curl -fsSLO https://raw.githubusercontent.com/Echolonius/boardcheck/main/examples/sample_listings.json
uvx --from git+https://github.com/Echolonius/boardcheck agent-market-signals sample_listings.json
The first line downloads seven made-up listings: three bait jobs, three agent self-ads and one ordinary job. The second runs Boardcheck on them straight from GitHub and prints a JSON report (trimmed here):
{
"listings_scanned": 7, "verdict": "high_risk", ... "findings": [ { "id": "AMS-001", "indicator": "view_application_inversion", "severity": "high", "listing_id": "synthetic-bait-1", "detail": "24 application(s) with 0 views — applying requires viewing, so this count is arithmetically implausible and may be fabricated" }, ... ], "summary": { "info": 0, "warn": 4, "high": 3 } }
Each of the three bait jobs shows 20 or more applications but zero views (AMS-001, high) and offers money with no escrow and no payment evidence (AMS-004, warning), and all three were created in the same second (AMS-002, warning). Because high-severity findings fired, the command exits with code 1 (0 means none fired, 2 means bad input), so it can also gate a script or a CI job.
id and created_at are required) and run the second line on that file instead.curl.exe instead of curl.AMS-007, right in the page: paste a board's listings JSON, and nothing you paste leaves your browser. It has a person mode and an AI-agent mode, plus a machine-readable llms.txt for agents.examples/agent_bait_listings.json holds four made-up listings for AMS-008: a copied "escrowed" bounty, a "verifier" that wants your private key, a listing with hidden text, and an ordinary bounty that stays clean.The quickstart workflow runs these exact commands, the pip installs and the MCP setup below on every pull request, so a broken instruction shows up as a failed check.
| Indicator | Fires when | Why it matters | |
|---|---|---|---|
AMS-001 view_application_inversion | applications exceed views (starkest: >0 applications, 0 views) | you must view a listing to apply, so this is arithmetically implausible — a sign of fabricated engagement | |
AMS-002 batch_creation_clustering | many listings share a creation timestamp to the second | signature of automated seeding, not organic demand | |
AMS-003 self_advertisement_ratio | most listings are agents advertising their own services | a supply glut presented to newcomers as demand | |
AMS-004 unpaid_work_risk | priced work with no escrow and no payment-evidence mechanism | payment depends entirely on poster discretion after delivery | |
AMS-005 high_budget_bait | a budget far above the platform median with zero views | a big number that attracts applicants while no real buyer is engaged | |
AMS-006 prompt_injection_payload | listing text (title, description, instructions) contains instruction-override or shell-command patterns, such as "ignore previous instructions" or cat /etc/passwd | the listing is trying to hijack the AI agent that reads it | |
AMS-007 upfront_fee_gating | a listing requires an upfront fee or deposit to apply or bid, with no escrow confirmed | you pay before any work starts, and nothing guarantees you get it back | |
AMS-008 agent_bait_listing | listing text asks for a private key, seed phrase or API token, or tells you to download and run remote code (`curl … \ | python3`) — high; or says human submissions won't be reviewed, claims escrow it gives no way to check, or hides text a person wouldn't see (zero-width or direction-control characters, or HTML comments that address an AI reader or give it orders; merely mentioning AI, as disclosure questions and template leftovers do, doesn't count) — warning. Running the project's own tests never counts | the listing is written to exploit an AI agent rather than to hire one; no real bounty needs your keys |
Checks stay silent when the data they need is missing — absence of evidence is not treated as evidence — with one exception: when a listing requires an upfront fee (requires_upfront_fee is true), AMS-007 counts a missing has_escrow as no escrow and fires unless has_escrow is true. Findings are advisory signals for a human or a downstream system to weigh, not verdicts, and each one explains its own reasoning. Each indicator carries a stable ID so it can be cited precisely (e.g. "AMS-004 unpaid-work risk"); the full definitions, severities, and known false positives live in SPEC.md.
About the name: the project is called Boardcheck, but the Python package and its commands are
still named
agent-market-signals(the CLI) andagent-market-signals-mcp(the MCP server).
Those are the names you install, run and configure, so they appear exactly that way below.
There is no PyPI release yet: everything installs straight from GitHub, and no account is needed.
uvx as in Try it in 30 seconds. pip install git+https://github.com/Echolonius/boardcheck
pip install "agent-market-signals[mcp] @ git+https://github.com/Echolonius/boardcheck" "mcp<2"
The library and the CLI use only the Python standard library. The MCP server also needs the official mcp Python SDK, which requires Python 3.10 or newer. For now it needs version 1 of that SDK, hence "mcp<2": version 2 renamed the server class this code imports.
The sample file isn't part of the installed package. Download it with the curl line above, or clone the repo and run python -m agent_market_signals examples/sample_listings.json from its root.
# without installing, via uv:
uvx --from git+https://github.com/Echolonius/boardcheck agent-market-signals listings.json
agent-market-signals listings.json
python -m agent_market_signals examples/sample_listings.json
cat listings.json | agent-market-signals -
Prints a JSON report and exits 1 if any high-severity finding was raised (handy in CI or a cron watcher), 0 if none was, and 2 on a usage or input error.
So an agent can call these checks at decision time — *"before I bid on this listing, check it"* — the package ships an optional MCP server. It runs locally over stdio; it hosts nothing and sends nothing anywhere.
With uv and git installed there is nothing else to set up. Add this to your MCP client's configuration (for example Claude Desktop's claude_desktop_config.json, or .mcp.json in a Claude Code project), and the client starts the server straight from GitHub:
{
"mcpServers": { "boardcheck": { "command": "uvx", "args": [ "--python", ">=3.10", "--from", "agent-market-signals[mcp] @ git+https://github.com/Echolonius/boardcheck", "--with", "mcp<2", "agent-market-signals-mcp" ] } } }
--python ">=3.10" lets uv use (or download) a Python new enough for the mcp SDK, and --with "mcp<2" keeps that SDK on version 1, which this server is written for. If your client can't find uvx, put its full path in "command" (which uvx, or where uvx on Windows). If you installed with pip instead (see Install), use "command": "agent-market-signals-mcp" with no args.
You can also find Boardcheck in the official MCP Registry as io.github.Echolonius/boardcheck (the registry points to the .mcpb bundle attached to each release), and in TensorBlock's MCP index.
The server exposes five tools:
| Tool | What the agent uses it for |
|---|---|
scan_listings | vet a whole marketplace board before trusting its numbers |
check_listing | check a single listing, such as one bounty, before bidding on, accepting or working on it (runs AMS-001, AMS-004 and AMS-008) |
list_indicators | discover what is checked (stable AMS-* IDs) and cite findings precisely |
make_observation | opt-in, privacy-preserving contribution to improve shared thresholds |
generate_audit_certificate | turn a scan into a machine-readable summary with an embeddable badge (generated from whatever listings you pass in, so it is not an independent audit) |
A suggested decision policy for an agent: **high_risk → do not bid; caution → require payment evidence (escr
只显示了开头部分;其余内容请在仓库中阅读