io.github.IntelagentStudios/mcp-enrichment
NPM · @INTELAGENT/MCP-ENRICHMENT · SCANNED SEP 20
Multi-source entity enrichment: company data, contacts, email verification, and phone validation
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 188 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 500 tokens (~71/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.IntelagentStudios/mcp-enrichment server?
io.github.IntelagentStudios/mcp-enrichment runs locally as an npm package, launched with npx -y @intelagent/mcp-enrichment. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @intelagent/mcp-enrichment
claude mcp add intelagentstudios-mcp-enrichment -- npx -y @intelagent/mcp-enrichment
{
"mcpServers": {
"intelagentstudios-mcp-enrichment": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
]
}
}
} {
"servers": {
"intelagentstudios-mcp-enrichment": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
]
}
}
} codex mcp add intelagentstudios-mcp-enrichment -- npx -y @intelagent/mcp-enrichment
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"intelagentstudios-mcp-enrichment": {
"type": "local",
"command": [
"npx",
"-y",
"@intelagent/mcp-enrichment"
],
"enabled": true
}
}
} openclaw mcp add intelagentstudios-mcp-enrichment --command npx --arg -y --arg @intelagent/mcp-enrichment
mcp_servers:
intelagentstudios-mcp-enrichment:
command: "npx"
args: ["-y", "@intelagent/mcp-enrichment"] {
"McpServers": {
"intelagentstudios-mcp-enrichment": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@intelagent/mcp-enrichment"
]
}
}
} assistant mcp add intelagentstudios-mcp-enrichment -t stdio -c npx -a -y @intelagent/mcp-enrichment
{
"mcpServers": {
"intelagentstudios-mcp-enrichment": {
"command": "npx",
"args": [
"-y",
"@intelagent/mcp-enrichment"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@intelagent/mcp-enrichment@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
enrich_company ~86
Enrich company data from a domain name or company name. Returns industry, employee count, funding, tech stack, social profiles, and more. Uses Clearbit API (falls back to mock data if no API key configured).
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | – | Company name (used if domain not provided) |
| domain | string | – | Company website domain (e.g. "stripe.com") |
No output schema declared.
No examples provided.
enrich_contact ~127
Enrich contact/person data from an email address or LinkedIn URL. Returns name, title, seniority, department, social profiles, and company info. Uses Clearbit API.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | Company name (optional hint) |
| domain | string | – | Company domain (optional hint) |
| string | – | Email address of the person to look up | |
| firstName | string | – | First name (optional hint) |
| lastName | string | – | Last name (optional hint) |
| linkedinUrl | string | – | LinkedIn profile URL (used if email not provided) |
No output schema declared.
No examples provided.
find_email ~88
Find the email address for a specific person at a company. Provide their first name, last name, and the company domain. Returns the most likely email and a confidence score. Uses Hunter.io API.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain (e.g. "stripe.com") |
| firstName | string | yes | Person's first name |
| lastName | string | yes | Person's last name |
No output schema declared.
No examples provided.
server_info ~31
Returns server metadata: name, version, registered tools, and registered resources. Useful for introspection and health checks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_email ~56
Verify an email address for deliverability. Returns validity, deliverability score, disposable/free provider detection, role-based detection, MX records check, and SMTP validation. Uses Hunter.io API.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to verify |
No output schema declared.
No examples provided.
verify_phone ~97
Validate and look up a phone number. Returns validity, formatted number, line type (mobile/landline/voip), carrier info, and location. Uses Twilio Lookup API.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Country dialing code without + (e.g. "1" for US, "44" for UK). Defaults to "44". |
| phone | string | yes | Phone number to verify (any format, E.164 preferred) |
No output schema declared.
No examples provided.
What is the io.github.IntelagentStudios/mcp-enrichment server?
io.github.IntelagentStudios/mcp-enrichment is listed in the public MCP registry as io.github.IntelagentStudios/mcp-enrichment. Multi-source entity enrichment: company data, contacts, email verification, and phone validation. This page covers its npm package (@intelagent/mcp-enrichment).
Is the io.github.IntelagentStudios/mcp-enrichment server safe to use?
io.github.IntelagentStudios/mcp-enrichment scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.IntelagentStudios/mcp-enrichment server expose?
io.github.IntelagentStudios/mcp-enrichment exposes 6 tools: enrich_company, enrich_contact, verify_email, verify_phone, find_email, server_info. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the io.github.IntelagentStudios/mcp-enrichment server still maintained?
io.github.IntelagentStudios/mcp-enrichment is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.IntelagentStudios/mcp-enrichment server under?
io.github.IntelagentStudios/mcp-enrichment declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.