boondmanager-mcp-server (fauguste/boondmanager-mcp-server) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: we have no way to read this server ourselves. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

boondmanager-mcp-server

MCP Server for BoondManager API - 182 tools, 12 prompts, 22 resources (ERP/CRM)

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

fauguste

Source: npm · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 1 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 5 credentials: BOOND_API_TOKEN, BOOND_CLIENT_KEY, BOOND_CLIENT_TOKEN, BOOND_PASSWORD, BOOND_USER_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@4.0.18GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretBOOND_API_TOKENclaude mcp add --transport stdio --env =votre_token_jwt \
configBOOND_BASE_URL"": "https://votre-instance.boondmanager.com/api"
🔐 secretBOOND_CLIENT_KEY"": "<votre_client_key>"
🔐 secretBOOND_CLIENT_TOKEN"": "<votre_client_token>",
configBOOND_DICTIONARY_OVERRIDESle mapping libellé→ID via (JSON inline ou chemin
configBOOND_DICTIONARY_TTL_MS3600000 (1 h) Durée de vie du cache du dictionnaire, en millisecondes. Une valeur non numérique ou ≤ 0 retombe sur le défaut.
configBOOND_DISABLE_UPDATE_CHECK
configBOOND_HTTP_MAX_RETRIES2 Nombre maximal de tentatives supplementaires (3 essais au total). 0 desactive entierement les retries.
configBOOND_HTTP_RATE_LIMIT_BURST20 Capacite du bucket = taille maximale de rafale immediate.
configBOOND_HTTP_RATE_LIMIT_RPS10 Debit soutenu (requetes/seconde). 0 desactive completement.
configBOOND_HTTP_RETRY_BASE_MS200 Delai de base utilise pour le backoff exponentiel (base 2^attempt, avec jitter).
configBOOND_HTTP_RETRY_MAX_MSL'en-tete Retry-After (en secondes ou en HTTP-date) est honore et plafonne a .
configBOOND_HTTP_TIMEOUT_MSexport =60000 # 60 s
configBOOND_MCP_CONFIRM_DELETE
configBOOND_OAUTH_AUTHORIZATION_SERVER
configBOOND_OAUTH_SCOPES_(vide)_ Scopes annonces dans scopes_supported (espace ou virgule). Vide = le client negocie directement avec Boond.
🔐 secretBOOND_PASSWORDenv =votre_mot_de_passe \
configBOOND_USERenv =votre_login \
🔐 secretBOOND_USER_TOKEN"": "<votre_user_token>",
configLOG_FORMAT(auto) json pour JSON pur, sinon pino-pretty en dev
configLOG_LEVELinfo Niveau de log : trace, debug, info, warn, error, fatal
configMCP_HTTP_ALLOWED_HOSTS_(auto)_ Liste blanche du header Host (anti DNS rebinding, CVE-2025-66414). pour desactiver explicitement.
configMCP_HTTP_HOSTexport =0.0.0.0 # defaut: 127.0.0.1
configMCP_HTTP_JSON_RESPONSEfalse true pour forcer des reponses JSON (sans SSE)
configMCP_HTTP_PATHexport =/mcp # defaut: /mcp
configMCP_HTTP_PORTexport =3000 # defaut: 3000
configMCP_HTTP_PUBLIC_URLexport =https://mcp.votre-domaine.com/mcp
configMCP_HTTP_SESSION_SWEEP_INTERVAL_MS300000 (5 min) Frequence de balayage des sessions inactives.
configMCP_HTTP_SESSION_TTL_MS1800000 (30 min) En mode stateful, duree d'inactivite au-dela de laquelle une session est fermee.
configMCP_HTTP_STATEFULfalse true pour activer le mode stateful (session Mcp-Session-Id)
configMCP_TRANSPORTLe serveur supporte deux transports MCP, selectionnables via la variable d'environnement .
// quality suggestions

Tool annotations

42/45 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/45 tools missing one or more hints — boond_x_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); boond_x_create (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); boond_x_delete (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/42 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/42 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

15/45 tools referenced in tests (33%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 7 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/boondmanager-mcp-server-gy1ann)](https://m8ven.ai/mcp/boondmanager-mcp-server-gy1ann)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a3046bf00926d808d158246d89c3c1edd7df9ccc
code hash: 437ea7b086d1d1d4c4381415888330f0210c763a43be5655e1696a570b5df9b6
verified: 6/26/2026, 9:51:37 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client