Skip to content

MCP servers › io.github.Echolonius › boardcheck

MCP server · registry snapshot 2026-11-12 · last checked 2026-11-12

boardcheck MCP server

Registry name io.github.Echolonius/boardcheck

by Echolonius · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Flags deceptive signals in AI-agent marketplace listings, from fake engagement to prompt injection — the publisher's description

4 of 5 record checks metversion 0.8.1Pythonstandard input/output

Summary

io.github.Echolonius/boardcheck is a local MCP server listed in the official MCP registry at version 0.8.1, under the namespace of the GitHub account Echolonius. Its linked repository, github.com/Echolonius/boardcheck, belongs to the same GitHub account.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
MCP bundle
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.8.1, published 2026-11-11 (registry, as of the 2026-11-12 snapshot)
First listed version
2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-06 to 2026-11-11; 3 in the 90 days before the 2026-11-12 snapshot.
Most recent 3 versions
  • 0.8.1 · 2026-11-11
  • 0.8.0 · 2026-11-07
  • 0.7.0 · 2026-11-06
(versions still listed in the registry only)
Registry data
snapshot 2026-11-12
Package and repository
checked 2026-11-12

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.8.0 (published 2026-11-07) → 0.8.1 (published 2026-11-11), between the registry lists of 2026-11-09 and 2026-11-12.

The publisher’s GitHub release note for v0.8.1, published 2026-11-11.

Read the release note (the publisher’s text, shown as plain text)
- AMS-006 no longer stops with an error when a listing's `title`, `description` or `instructions`
  is not text (a number, list or object). Such a value is skipped, as AMS-008 already did, in both
  the Python library and the browser version.
- **`check_listing` now also runs AMS-006 and AMS-007.** The single-listing MCP tool runs all five
  checks that need only one listing (AMS-001, AMS-004, AMS-006, AMS-007 and AMS-008), in the order
  `scan()` runs them. An agent checking one bounty now also learns about prompt-injection phrases
  in its text and about an upfront fee with no confirmed escrow. AMS-002, AMS-003 and AMS-005
  compare the listings on a board with each other, so they stay in `scan()` and `scan_listings`,
  which are unchanged.
- The tool's description, `manifest.json`, README.md, SCHEMA.md, `docs/llms.txt` and the site's
  agent instructions now say the same thing about what `check_listing` runs. A test checks those
  descriptions, and the tool lists in `manifest.json`, README.md and `docs/llms.txt`, against the
  code.
- README: new section, "Check a bounty issue before you work on it". It shows how an agent passes
  one GitHub bounty issue, or any task text, to `check_listing` as a single listing (the title as
  `title`, the raw body as `description`). `tests/test_readme_examples.py` runs the made-up example,
  so the findings shown are the ones the code returns. `docs/llms.txt` and the site's agent
  instructions have the same recipe in short form.
- Wording: the install note at the top of `agent_market_signals/mcp_server.py` used the
  repository's old name, and FLYWHEEL.md still called the MCP server a next step.


MCP Bundle: `boardcheck-mcp-0.8.1.mcpb` (SHA-256 `0c2ee61856552b960a102ad096b660cc2b9b93d57f76774ef2b36de1a8205ed1`)

The release on GitHub

Source: the official MCP Registry list on 2026-11-09 and on 2026-11-12; release notes from the GitHub Releases API, checked 2026-11-12.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • Bundle platforms (MCPB). The bundle lists platforms darwin, linux and win32 (manifest.json compatibility). Source: read 2026-11-12.
  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/Echolonius/boardcheckOpens publiclymatchesapi.github.com · 2026-11-12

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Echolonius
GitHub owner
a personal account (Echolonius)
Repository
github.com/Echolonius/boardcheck
Stars
1
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-12; security policy read from GitHub · 2026-11-07.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-12 (security policy 2026-11-07). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.Echolonius/boardcheck

Answered from the data above

Who publishes io.github.Echolonius/boardcheck?

The registry ties the namespace io.github.Echolonius to the GitHub account Echolonius; only its owner can publish under it. Its linked repository, github.com/Echolonius/boardcheck, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.Echolonius/boardcheck safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.Echolonius/boardcheck been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does io.github.Echolonius/boardcheck publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.Echolonius/boardcheck?

In github.com/Echolonius/boardcheck, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-12; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-12
Hosting type
registry · 2026-11-12
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-12
Required credentials
none declared
registry · 2026-11-12 · no declaration is not a guarantee
Package registry
registry · 2026-11-12
Freshness
0–30 days
registry updatedAt · 2026-11-12
Lifecycle status
registry · 2026-11-12
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-12
Maintenance
api.github.com · 2026-11-12
Environment
your machine
where it runs, from the hosting type · 2026-11-12

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Echolonius/boardcheck: MCP server record.” Data checked 2026-11-12. https://protocolprobe.com/mcp/servers/io.github.Echolonius/boardcheck

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Echolonius/boardcheck)](https://protocolprobe.com/mcp/servers/io.github.Echolonius/boardcheck)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology