Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Boardcheck
Overview
Description from the maker (original English)
Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Echolonius, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 2550 servers in this category
- Published to the registry more recently than 94% of the other 2550 servers in this category
- Basic checks equal to or better than 100% of the other 2550 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Boardcheck safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.8.0) reached the registry today.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
idandcreated_atare required) and run the second line on that file instead. - On Windows PowerShell, type
curl.exeinstead ofcurl. - 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.jsonholds four made-up listings forAMS-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
| 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.
Install
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.
- Run the CLI without installing anything (Python 3.9+): use
uvxas 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:
| 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
Only the beginning is shown; read the rest in the repo