BOSSCORE MCP PACK (bosserpnext/bosscore-mcp-pack) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 62 tools. No publisher has claimed this listing.

C
Limited view
71/100
1 month ago

BOSSCORE MCP PACK

Modular MCP capabilities package for the BOSS ecosystem, enabling WordPress site management, file reading, and cPanel deployment with 63 tools across three profiles (wordpress, files, full) and two transport modes (stdio and HTTP/SSE).

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for this stack is partially covered.

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

bosserpnext

Source: 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
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 3 credentials: DEPLOY_TOKEN, BOSSCORE_MCP_OAUTH_CLIENT_SECRET, WORDPRESS_APP_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configBOSSCORE_MCP_SERVER_URL
configBOSSCORE_MCP_ENFORCE_AUTHEn production, activer =1.
configBOSSCORE_MCP_PROFILE
configBOSSCORE_WORKSPACE$env: = "H:\...\companies"
🔐 secretDEPLOY_TOKEN$env: = "..."
configDEPLOY_URL
configBOSSCORE_MCP_STORE_DIR1. doit pointer vers un répertoire persistant et
configBOSSCORE_MCP_ALLOWED_ORIGINS
configBOSSCORE_MCP_ACCESS_TOKEN_TTL
configBOSSCORE_MCP_REFRESH_TOKEN_TTL
configBOSSCORE_MCP_AUTH_CODE_TTL
configBOSSCORE_MCP_OAUTH_STORE
configBOSSCORE_MCP_OAUTH_CLIENT_ID
🔐 secretBOSSCORE_MCP_OAUTH_CLIENT_SECRET
configBOSSCORE_MCP_OAUTH_REDIRECT_URIS
configBOSSCORE_MCP_OAUTH_SCOPES
configBOSSCORE_PLAN_STORE_LOCK_TIMEOUT
configBOSSCORE_DEPLOY_PLAN_TTL2. vaut 1800 secondes par défaut.
configWORDPRESS_URL$env: = "https://core.bosserpnext.com"
configBOSSCORE_EXEC_ALLOWED_PATHS
configBOSSCORE_EXEC_MAX_OUTPUT
configBOSSCORE_EXEC_TIMEOUT
configBOSSCORE_EXEC_PLAN_TTL
configBOSSCORE_FILE_ROOTS
configWORDPRESS_USERNAME$env: = "boss"
🔐 secretWORDPRESS_APP_PASSWORD$env: = "..."
configBOSSCORE_MAX_FILE_BYTES
configBOSSCORE_MAX_OUTPUT_CHARS
configOLLAMA_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

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

All four hints declared on every tool

62/62 tools missing one or more hints — wp_list_pages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp_get_page (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); wp_create_page (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +59 more. 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

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.

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 5 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/bosserpnext/bosscore-mcp-pack)](https://m8ven.ai/mcp/bosserpnext/bosscore-mcp-pack)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: a29d781c1cdc3b4d5d7fd7687974e14ca1bcdf95
code hash: 18ac6912bc0313d0b5764eaba132d5bd5922d33e8938bf09457a195a1840712b
verified: 7/25/2026, 8:47:30 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