Planfix MCP Server (popstas/planfix-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 50 out of 100, grade D. It declares 18 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
50/100

Planfix MCP Server

Enables integration with Planfix CRM and task management system, allowing lead management, contact/company management, task creation/search/commenting, and report generation via the Planfix REST API v2.0.

→ popstas/planfix-mcp-server· listed on glama

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

⚡ 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

popstas

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

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
1 flow detected: AMOCRM_ACCESS_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🚨
Known vulnerabilities in dependencies: 1 critical, 12 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: AMOCRM_ACCESS_TOKEN, PLANFIX_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 critical12 high14 low

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

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

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

high@modelcontextprotocol/sdk@1.15.1GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.15.1GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.15.1GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highjs-yaml@4.1.0GHSA-2883-xcg3-v3hh

js-yaml: maxTotalMergeKeys does not limit CPU use for empty merge sources

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.
🔐 secretAMOCRM_ACCESS_TOKEN
configPLANFIX_ACCOUNTYour Planfix account name (e.g., yourcompany)
configPLANFIX_ACCOUNT_URL(optional) Override the web origin used for human-facing links (task/contact/user pages). Defaults to PLANFIX_BASE_URL without the trailing /rest/
configPLANFIX_BASE_URL(optional) Override the REST API base URL. Defaults to https://<PLANFIX_ACCOUNT>.planfix.com/rest/. Set this for .ru and other regional installations, e.g. https://yourcompany.planfix.ru/rest/
configPLANFIX_CONFIGflag or the environment variable. You can also specify a
configPLANFIX_DRY_RUN
configPLANFIX_FIELD_ID_AGENCYCustom field ID for agency
configPLANFIX_FIELD_ID_CLIENTCustom field ID for client
configPLANFIX_FIELD_ID_EMAILCustom field ID for email
configPLANFIX_FIELD_ID_EMAIL_ADDITIONALis set, against that custom field (filter
configPLANFIX_FIELD_ID_LEAD_IDCustom field ID for external lead ID
configPLANFIX_FIELD_ID_LEAD_SOURCECustom field ID for lead source
configPLANFIX_FIELD_ID_MANAGERCustom field ID for manager
configPLANFIX_FIELD_ID_PHONECustom field ID for phone
configPLANFIX_FIELD_ID_PIPELINECustom field ID for pipeline
configPLANFIX_FIELD_ID_SERVICE_MATRIX
configPLANFIX_FIELD_ID_TAGSCustom field ID for task tags
configPLANFIX_FIELD_ID_TELEGRAMSet any value to use the system Telegram field
configPLANFIX_FIELD_ID_TELEGRAM_CUSTOMCustom field ID for Telegram when using the custom field
configPLANFIX_TASK_TITLE_TEMPLATE
🔐 secretPLANFIX_TOKENPlanfix API token with necessary permissions
configZAPIER_INPUT_AMOCRM
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

18/18 tools missing one or more hints — planfix_add_to_lead_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); planfix_create_comment (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); planfix_create_contact (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +15 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.).

Secrets stay with their owner

1 secret sent to a request target we could not resolve (AMOCRM_ACCESS_TOKEN → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Production dependencies are patched

0 critical, 11 high severity in production deps — @modelcontextprotocol/sdk@1.15.1 (high), @modelcontextprotocol/sdk@1.15.1 (high)

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

Dev dependencies

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

Upgrade dev dependencies when convenient.

Dependency freshness

1/12 production deps stale: node-fetch@2023-11-30 (2.8y)

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 6 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/popstas/planfix-mcp-server?variant=verified)](https://m8ven.ai/mcp/popstas/planfix-mcp-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: fba7111860cb89009ff9ed5622bb97e0c70eec08
code hash: 8de27f06410407d8babfa2ce6149600e73ed6fd1c51350e1946f6affae34e79f
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