Lead Enrich (carsonlabs/leadenrich-mcp) is an MCP server listed on the M8ven Trust Index. It scores 34 out of 100, grade F. It declares 6 tools. No publisher has claimed this listing.

Warning

34/100

Lead Enrich

Item: Lead Enrich
Rating: 34
Author: M8ven

Cascading lead enrichment through Apollo, Clearbit, and Hunter for maximum coverage.

→ carsonlabs/leadenrich-mcp · listed on pulsemcp

Warning. Serious findings were identified. Review the full report before connecting. 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 push why connect →

Who stands behind it

carsonlabs

Source: PulseMCP · 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 →

⚡ Connect GitHub for Live Monitored

Install from

PulseMCPnot scored here 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

🚨

Hardcoded credentials detected

1 live-looking API key in source: 1 Stripe publishable (live)

🔐

You'll be asked for 7 credentials: APOLLO_API_KEY, CLEARBIT_API_KEY, HUNTER_API_KEY, LEADENRICH_API_KEY, MCPIZE_LICENSE_KEY, STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET

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.

🔐 secretAPOLLO_API_KEYApollo.io API key No

🔐 secretCLEARBIT_API_KEYClearbit API key No

🔐 secretHUNTER_API_KEYHunter.io API key No

🔐 secretLEADENRICH_API_KEYClient auth key for usage metering No

🔐 secretMCPIZE_LICENSE_KEY

configHOST

🔐 secretSTRIPE_SECRET_KEY

🔐 secretSTRIPE_WEBHOOK_SECRET

configLEADENRICH_USAGE_DIR

configLEADENRICH_FREE_TIER_LIMITFree tier limit (default: 50) No

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

6/6 tools missing one or more hints — enrich_lead (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); find_email (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); enrich_company (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 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.).

No hardcoded API keys

1 live-looking API key in source: 1 Stripe publishable (live)

Move secrets to environment variables (process.env.X) or your secret manager.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

7 secret values sent to log.info/log.error

Redact or omit secret values from log output.

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/carsonlabs/leadenrich-mcp?variant=verified)](https://m8ven.ai/mcp/carsonlabs/leadenrich-mcp)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 8c278d1714e05f1b723f30ee543335971e2f45f7

code hash: 95ad23a63927ffdd63d04e0ce5c30e7af5efbd901dc6cd16ea3b70de6459a9ff

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