Scrupp MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRUPP_API_KEY | Yes | Your Scrupp API key (e.g. sk_live_...). Required to authenticate requests. | |
| SCRUPP_WAIT_SECONDS | No | Caps how long a tool blocks. A job that outruns it comes back as { status: "running", job_id } with a note telling the agent to call scrupp_get_job. | 120 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scrupp_export_sales_navigator_searchA | Extract the people from a LinkedIn Sales Navigator search URL, with their titles, companies and (by default) verified work emails. Use this when the user has a Sales Navigator search they want as a list. |
| scrupp_export_linkedin_searchA | Extract the people from a regular LinkedIn people-search URL. Use this for linkedin.com/search/results/people URLs; use the Sales Navigator tool for linkedin.com/sales URLs. |
| scrupp_run_apollo_searchB | Extract the people from an Apollo search URL. Requires a connected Apollo account, passed as |
| scrupp_enrich_linkedin_profilesC | Full profile data for LinkedIn profile URLs: current title, company, location, experience. |
| scrupp_lookup_companyB | Company data — size, industry, location, website, LinkedIn — from a domain, a company LinkedIn URL, or a name. |
| scrupp_find_decision_makersA | The people worth writing to at a company you only know the domain, LinkedIn URL or name of. Returns names, titles and (where found) work emails. |
| scrupp_find_emailsB | Find and verify work email addresses from first name, last name and company domain. Addresses that cannot be verified come back marked rather than guessed. |
| scrupp_get_jobA | Status of a job, and its records once it has finished. Use this for a job that was still running when the tool that started it returned. |
| scrupp_creditsA | Remaining Scrupp credits and the current plan. Worth checking before starting a large export — one credit is one record requested. |
| scrupp_verify_emailsA | Check whether email addresses are deliverable before sending to them. Costs one credit per address; use it on addresses you already have, not on ones scrupp_find_emails just returned (those are verified already). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Most tools are clearly separated by input source and action: the export_* tools map to distinct URL types, and find_emails vs verify_emails have different intents. Some overlap remains among tools that return people/emails (find_emails, find_decision_makers, export_*), but the descriptions reduce confusion.
All names use the scrupp_ prefix with snake_case and generally follow an action_object pattern. The main deviation is scrupp_credits, which is a noun rather than a verb, and the verb set varies (find, verify, export, run, enrich, lookup, get), though still readably consistent.
10 tools is well-scoped for a contact/company data enrichment and export service. Each tool earns its place by covering a distinct source, action, or operational need (credits, async job status, find/verify, LinkedIn/Sales Navigator/Apollo exports, enrichment, company lookup, decision makers).
The surface covers the key workflows for the domain: finding and verifying emails, exporting people from LinkedIn, Sales Navigator, and Apollo searches, enriching LinkedIn profiles, looking up companies, finding decision makers, and checking credits and job status. No obvious retrieval or lifecycle gaps stand out for the stated purpose.