原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Boardcheck

作者:Echolonius版本 0.8.0i★ –i在你的电脑上运行
注册名称io.github.Echolonius/boardcheck

安装

概览

作者提供的说明(英文原文)

Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 网店与支付

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 注册中心没有列出需要填写的密钥。

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

下载作者的 .mcpb 文件

链接指向作者自己的文件;我们不托管也不重新打包它。打开文件后,Claude Desktop 会进行安装。

在终端中运行这条命令

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 Echolonius 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“网店与支付”中的其他服务器比较i

  • 星标数多于此分类中其他 2546 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2546 个服务器的 94% 更新
  • 基础检查结果等于或优于此分类中其他 2546 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Boardcheck 安全吗?

它在 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

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Stripe MCP

作者:stripe

MCP server integrating with Stripe - tools for customers, products, payments, and more.

在云端运行★ 2,043MIT12个月前更新
安装

MCP Cn Commerce

作者:TonyWang-hub

8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending

在你的电脑上运行★ 96MIT29天前更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。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.

Try it in 30 seconds

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.

  • Your own listings: save them as a JSON array (fields in SCHEMA.md; only id and created_at are required) and run the second line on that file instead.
  • On Windows PowerShell, type curl.exe instead of curl.
  • No terminal? The browser version runs the same checks, except 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.
  • Using an AI agent? Give it these checks as tools through the MCP server.
  • Bounty bait aimed at 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.

What it checks

IndicatorFires whenWhy it matters
AMS-001 view_application_inversionapplications 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_clusteringmany listings share a creation timestamp to the secondsignature of automated seeding, not organic demand
AMS-003 self_advertisement_ratiomost listings are agents advertising their own servicesa supply glut presented to newcomers as demand
AMS-004 unpaid_work_riskpriced work with no escrow and no payment-evidence mechanismpayment depends entirely on poster discretion after delivery
AMS-005 high_budget_baita budget far above the platform median with zero viewsa big number that attracts applicants while no real buyer is engaged
AMS-006 prompt_injection_payloadlisting text (title, description, instructions) contains instruction-override or shell-command patterns, such as "ignore previous instructions" or cat /etc/passwdthe listing is trying to hijack the AI agent that reads it
AMS-007 upfront_fee_gatinga listing requires an upfront fee or deposit to apply or bid, with no escrow confirmedyou pay before any work starts, and nothing guarantees you get it back
AMS-008 agent_bait_listinglisting 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 countsthe 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.

Install

About the name: the project is called Boardcheck, but the Python package and its commands are

still named agent-market-signals (the CLI) and agent-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.

  • Run the CLI without installing anything (Python 3.9+): use uvx as in Try it in 30 seconds.
  • Install the library and the CLI (Python 3.9+):
  pip install git+https://github.com/Echolonius/boardcheck
  • Install them with the MCP server (Python 3.10+):
  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.

Use it from the command line

# without installing, via uv:

uvx --from git+https://github.com/Echolonius/boardcheck agent-market-signals listings.json

after pip install:

agent-market-signals listings.json

from a clone of this repo:

python -m agent_market_signals examples/sample_listings.json

reading the listings from stdin:

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.

Use it from an AI agent (MCP server)

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:

ToolWhat the agent uses it for
scan_listingsvet a whole marketplace board before trusting its numbers
check_listingcheck a single listing, such as one bounty, before bidding on, accepting or working on it (runs AMS-001, AMS-004 and AMS-008)
list_indicatorsdiscover what is checked (stable AMS-* IDs) and cite findings precisely
make_observationopt-in, privacy-preserving contribution to improve shared thresholds
generate_audit_certificateturn 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

只显示了开头部分;其余内容请在仓库中阅读

问 PopNx