Spree Commerce: open-source B2B and marketplace ecommerce
Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Beschreibung vom Entwickler (englisches Original)
Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Die .mcpb-Datei des Entwicklers herunterladen
Der Link führt zur Datei des Entwicklers selbst; wir hosten sie nicht und verpacken sie nicht neu. Öffne die Datei, dann installiert Claude Desktop sie.
Führe das in deinem Terminal aus
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 10. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto Echolonius bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (0.8.0) kam vorgestern in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du MCPB auf deinem Computer.
In derselben Kategorie: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:↓ Downloads pro Wochei★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
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
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
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
Nur der Anfang wird gezeigt; den Rest findest du im Repo