Enrich Layer
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is coherent for Enrich Layer data enrichment, but users should verify the external MCP package, protect the API key, and approve costly or sensitive people-search operations.
Before installing, confirm that the npm package is the one you intend to trust, use a dedicated Enrich Layer API key, and ask the agent to get confirmation before bulk searches or personal contact lookups that may spend credits or involve sensitive data.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The external package will run locally as the MCP server and can receive the Enrich Layer API key and tool inputs.
The skill relies on an external npm MCP server that is not included in the artifact set and is not version-pinned in the shown configuration.
"command": "npx", "args": ["-y", "@verticalint-michael/enrich-layer-mcp"]
Verify the npm package and linked repository before use, and pin a trusted version if your MCP configuration supports it.
Anyone controlling the configured MCP server or key could use the Enrich Layer account and consume credits.
The skill requires an API key and passes it into the MCP server environment to access the Enrich Layer service.
requires:\n env:\n - ENRICH_LAYER_API_KEY
Use a dedicated, rotatable API key, monitor credit usage, and avoid sharing the key outside the intended MCP configuration.
Large searches can spend credits quickly and may return personal or professional contact data.
The tool set includes bulk people/company lookups that can consume paid credits; the artifact also documents costs and warns to check credits for large operations.
enrich_employee_list — List employees of a company... Cost: 3 credits per employee returned
Require clear user intent and confirmation before bulk lookups or contact-data retrieval, and follow applicable privacy and acceptable-use rules.
Company names, person identifiers, emails, phone numbers, or profile URLs submitted to the tools may be sent to Enrich Layer through the MCP server.
Tool requests and enrichment targets flow through an MCP server to an external API, which is expected for this integration but is still a data boundary users should understand.
This skill connects to the Enrich Layer API via MCP
Only submit data you are allowed to send to the service, and review Enrich Layer’s privacy and retention terms for sensitive contact information.