Fullenrich MCP

Live

API KEY

SALES INTELLIGENCE

CRM & Sales

Your agent finds verified emails and mobile numbers for any prospect using Fullenrich's waterfall enrichment across 20+ data vendors.

  • Acts as the user. Every enrichment call carries the user's API key, not a shared service token.
  • Credentials stay vaulted. AES-256 at rest, resolved at request time, never written to context.
  • Scoped before every call. Per-user permissions enforced with a 90-day audit trail.
Fullenrich MCP
agent · Acme Q3
Run
Find the email and phone for Sarah Chen at Acme Corp.
S
fullenrich_person_enrich
85ms
Fullenrich enrichment agent
Found 2 results. Email: s.chen@acme.com (94% confidence). Mobile: +1-415-555-0182. Sourced via 3 vendors.
Sources: 3 vendors, waterfall match
fullenrichmcp
1 person enriched
18:29
Message Claude...

Tools your prospecting agent reaches for on Fullenrich MCP, scoped per user.

CALL ANY TOOL
Each tool maps to a Fullenrich API endpoint and runs under the authenticated user's key.
fullenrichmcp_enrich_bulk
Enrich Bulk
Launch an asynchronous bulk enrichment job for a list of contacts, retrieving professional email addresses or phone numbers. Returns an enrichment ID and URL to track results.
Parameters
Name
Type
Required
Description
contacts
string
Required
List of contacts to enrich
fields
string
Required
Enrichment fields to request
name
string
Required
Short human-readable label for this enrichment (e.g. Google Engineers Emails)
fullenrichmcp_enrich_personal_email_bulk
Enrich Personal Email Bulk
fullenrichmcp_enrich_search_contact
Enrich Search Contact
fullenrichmcp_export_companies
Export Companies
fullenrichmcp_export_contacts
Export Contacts
fullenrichmcp_export_enrichment_results
Export Enrichment Results
fullenrichmcp_get_credits
Get Credits
fullenrichmcp_get_enrichment_results
Get Enrichment Results
fullenrichmcp_list_industries
List Industries
fullenrichmcp_search_companies
Search Companies
fullenrichmcp_search_contact_by_email
Search Contact By Email
fullenrichmcp_search_people
Search People
Build your Agent
One auth setup wires Fullenrich MCP into every major agent framework without touching your enrichment logic.
Python · LlamaIndex
Try these prompts
Drop any of these into your agent to start enriching prospects immediately.
Prospect enrichment
Copy the prompt
Copied
Find the work email and mobile for [first name] [last name] at [company].
Copy the prompt
Copied
Enrich all contacts in my CSV who are missing phone numbers.
Copy the prompt
Copied
What is the confidence score for the email you just found?
Bulk operations
Copy the prompt
Copied
Submit these 200 LinkedIn URLs for batch enrichment.
Copy the prompt
Copied
How many credits do I have left before my next refill?
Copy the prompt
Copied
Check the status of my enrichment job from this morning.
Copy the prompt
Copied
Download results for job ID [job_id] and push them to HubSpot.
Pipeline research
Copy the prompt
Copied
Find direct dials for all open opportunities in my pipeline over $20K.
Copy the prompt
Copied
Enrich the attendee list from last week's webinar and format it as a CSV.
Copy the prompt
Copied
Which EMEA prospects are missing phone numbers? Enrich them now.
SEE HOW AUTH WORKS
The user connects their Fullenrich API key once; every agent call after resolves their credential at runtime with scope enforcement.
1
Authorize
Your user connects
Fullenrich MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Fullenrich MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Fullenrich MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Fullenrich MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
See the same per-user auth pattern working across sales intelligence, CRM, and outreach connectors.
GTM
CRM AI agent
Log calls, update opportunity stages, and surface stalled deals across HubSpot or Salesforce. No manual data entry.
SALES
Deal intelligence agent
Combine Gong, Attio, and Slack signals to surface deal risks and next-best actions. Updated after every call.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Most enrichment integrations pass a single shared API key that breaks attribution the moment two users touch the agent.
01.
Shared tokens break per-user analytics
A shared Fullenrich key looks fine in a demo. In production, every enrichment call is billed to one account and credited to no one. Scalekit resolves the real user credential so usage, cost, and attribution stay accurate.
// shared key
enrichment → api_key_team_shared
audit → service_account

// scalekit
enrichment → api_key_user_abc
audit → user_abc ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Fullenrich MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does every user need their own Fullenrich API key, or can I use one shared key?
Each user connects their own Fullenrich API key through Scalekit's vault. This preserves per-user credit usage, billing attribution, and audit logs. Shared keys collapse all activity into a single account and break any per-seat reporting Fullenrich provides.
How does Scalekit store my users' Fullenrich API keys?
Keys are encrypted with AES-256 at rest and stored in Scalekit's credential vault. They are decrypted in memory only at the moment of an API call and are never written into agent context, logs, or prompt history.
Can I limit which Fullenrich tools a specific agent or role can call?
Yes. Scalekit's listScopedTools returns only the tools the authenticated user is permitted to call based on their role and your tenant configuration. An agent presented with a restricted scope will not see fullenrich_bulk_enrich unless that tool is explicitly allowed for that user.
What happens if a user revokes their Fullenrich API key or their account is deprovisioned?
Scalekit detects the revocation on the next credential resolution attempt. Subsequent tool calls for that user return an auth error immediately rather than making a live Fullenrich request. You can also proactively delete the credential from the vault via the Scalekit API when deprovisioning users from your app.
Fullenrich charges per enrichment credit — how do I prevent agents from over-consuming a user's quota?
You can set tool-level rate limits and call budgets in Scalekit's connector configuration. Combined with the fullenrich_credits_balance tool, your agent can check remaining credits before submitting bulk jobs and surface a warning to the user before credits run out.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""fullenrichmcp"": {
""url"": ""https://mcp.scalekit.com/fullenrichmcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.fullenrichmcp]
url = ""https://mcp.scalekit.com/fullenrichmcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""fullenrichmcp"": {
""url"": ""https://mcp.scalekit.com/fullenrichmcp"",
""type"": ""http""
}
}
}