Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Boardcheck
개요
제작자가 쓴 설명(영어 원문)
Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection
PopNx MCP의 세 기둥
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
- 사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
- 우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
- 사용 정도i아직 측정 안 함★ –
할 수 있는 일
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
- 연결 방식: 내 컴퓨터에서 실행
- 전송 방식: stdio
- 카테고리: 온라인 쇼핑몰 및 결제
설치
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
설치하기 전에
- 기본 점검: 1개 중 1개 통과
- 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
- 레지스트리에 입력해야 할 키가 나와 있지 않아요.
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
링크는 제작자의 파일로 바로 연결돼요. 우리가 보관하거나 다시 패키징하지 않아요. 파일을 열면 Claude Desktop이 설치해요.
터미널에서 이 명령어를 실행하세요
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
할 수 있는 일
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
기본 점검i
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
- ✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 Echolonius 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
- … 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- … 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- – 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
- – 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
- … 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
온라인 쇼핑몰 및 결제 카테고리의 다른 서버와 비교i
- 이 카테고리의 다른 서버 2550개 중 0%보다 스타가 많아요
- 이 카테고리의 다른 서버 2550개 중 94%보다 최근에 레지스트리에 공개됐어요
- 기본 점검 결과가 이 카테고리의 다른 서버 2550개 중 100%와 같거나 더 좋아요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
자주 묻는 질문
Boardcheck, 안전한가요?
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
어떤 키나 코드가 필요한가요?
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
아직 관리되고 있나요?
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.8.0)은 오늘 레지스트리에 올라왔어요.
어떤 앱에서 쓸 수 있나요?
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 MCPB도 있어야 해요.
대신 쓸 수 있는 건 뭐가 있나요?
같은 카테고리에는: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
대안
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
제작자의 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
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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요