MCP-birix-loc (NohchiyBors/MCP-birix-loc) is an MCP server listed on the M8ven Trust Index. It scores 46 out of 100, grade D. It declares 61 tools. No publisher has claimed this listing.

Caution. Specific findings reduced this grade. They are listed on the page. 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

NohchiyBors

Source: github_code

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
🚨
Secret credentials may flow to a network call
3 flows detected: BITRIX24_CLIENT_SECRET. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 10 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 4 credentials: BITRIX24_CLIENT_SECRET, BITRIX_BACKEND_TOKEN, MCP_API_KEY, TOKENS_ENCRYPTION_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical10 high6 medium12 low

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

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

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

highaxios@1.13.5GHSA-35jp-ww65-95wh

axios Vulnerable to Full Man-in-the-Middle via Prototype Pollution Gadget in `config.proxy`

highaxios@1.13.5GHSA-3g43-6gmg-66jw

axios Vulnerable to Credential Theft and Response Hijacking via Prototype Pollution Gadget in Config Merge

highaxios@1.13.5GHSA-6chq-wfr3-2hj9

Axios: Header Injection via Prototype Pollution

highaxios@1.13.5GHSA-777c-7fjr-54vf

Allocation of Resources Without Limits or Throttling in Axios

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.
configAUTH_MODEЧто нужно настроить
configBITRIX24_CLIENT_ID
🔐 secretBITRIX24_CLIENT_SECRET
configBITRIX24_PORTALBITRIX24_PORTAL, BITRIX24_CLIENT_, BITRIX24_REDIRECT_URI
configBITRIX24_REDIRECT_URIBITRIX24_PORTAL, BITRIX24_CLIENT_, BITRIX24_REDIRECT_URI
configBITRIX24_SCOPE
configBITRIX24_WEBHOOK_URLDev/тест на одном портале, действия от одного юзера
configBITRIX_BACKEND_AUTOSTART
configBITRIX_BACKEND_SCRIPT
🔐 secretBITRIX_BACKEND_TOKEN
configBITRIX_BACKEND_URL
configINSTALL_MAX_BODY_KBInstall server. Body limit (64 KiB). Валидация member_id (без управляющих символов и /). Constant-time проверка application_token на /uninstall.
configINSTALL_SERVER_HOST
configINSTALL_SERVER_PORT
configLOG_LEVEL
🔐 secretMCP_API_KEYMCP HTTP transport. Constant-time Bearer compare. Default loopback. Запрет non-loopback без . Body limit MCP_HTTP_MAX_BODY_KB. JSON-parse → JSON-RPC Parse error -32700.
configMCP_HTTP_HOST
configMCP_HTTP_MAX_BODY_KBMCP HTTP transport. Constant-time Bearer compare. Default loopback. Запрет non-loopback без MCP_API_KEY. Body limit . JSON-parse → JSON-RPC Parse error -32700.
configMCP_HTTP_PORT
configMCP_TENANT_MEMBER_ID+ публичный HTTPS, INSTALL_SERVER_, MCP_TENANT_MEMBER_ID для обслуживания конкретного портала
configMCP_TRANSPORT
configOAUTH_CALLBACK_PORT
configTOKENS_DIR
🔐 secretTOKENS_ENCRYPTION_KEYToken store. AES-256-GCM. Ключ 32 байта (). mode 0600, atomic write через .tmp + rename. Multi-tenant вариант — sha256(member_id) как имя файла.
configTOKENS_FILE
configYEAR
// 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

61/61 tools missing one or more hints — bitrix_server_info (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bitrix_call (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); bp_workflow_list (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +58 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.

Tool inputs are validated

53/61 tool handlers declare input schemas (87%)

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

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.

Secrets not logged

2 secret values sent to log/warn

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 10 high severity in production deps — axios@1.13.5 (high), axios@1.13.5 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

1/7 production deps stale: axios-retry@2024-08-02 (2.1y)

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 8 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 Verified](https://m8ven.ai/badge/mcp/nohchiybors/mcp-birix-loc?variant=verified)](https://m8ven.ai/mcp/nohchiybors/mcp-birix-loc)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 96bef25f339964aeefe5089aa4860403a08b34b1
code hash: 92fb4ab9a02dbef8d4ab498d225955c7048ce47d0c42f9b08eb49f48a5bd1e0b
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