Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.wismhero-maker/scrupp

NPM · SCRUPP-MCP-SERVER

Export LinkedIn, Sales Navigator and Apollo searches; find decision makers and verified work emails

Available components

70 Trust /100

Last scanned (23 hours ago)

Scores higher than 40% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1036 tokens (~103/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 14 Oct 26 +42
    • Injection markers: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Dependency health: unverified → 0.85 ▲ functional
    • First check of Tool coverage: 97 functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 13 Oct 26 28

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Analysed npm/scrupp-mcp-server@0.2.3

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 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~972 tokens

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 →

Tool Tokens
scrupp_credits ~34

Remaining Scrupp credits and the current plan. Worth checking before starting a large export — one credit is one record requested.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scrupp_enrich_linkedin_profiles ~96

Full profile data for LinkedIn profile URLs: current title, company, location, experience.

NameTypeReqDescription
profile_urlsarrayyesLinkedIn profile URLs.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).
with_emailsboolean–Also find and verify work emails (billed per enriched profile plus per email found). Defaults to false.

No output schema declared.

No examples provided.

scrupp_export_linkedin_search ~149

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.

NameTypeReqDescription
accountstring–Connected account email to run the search with.
maxinteger–Upper bound on records. Drives the credit hold; unused credits are refunded. Defaults to 100.
urlstringyesThe search URL, copied from the platform after building the filters.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).
with_emailsboolean–Also find work email addresses. Defaults to true.

No output schema declared.

No examples provided.

scrupp_export_sales_navigator_search ~157

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.

NameTypeReqDescription
accountstring–Connected account email to run the search with.
maxinteger–Upper bound on records. Drives the credit hold; unused credits are refunded. Defaults to 100.
urlstringyesThe search URL, copied from the platform after building the filters.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).
with_emailsboolean–Also find work email addresses. Defaults to true.

No output schema declared.

No examples provided.

scrupp_find_decision_makers ~116

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.

NameTypeReqDescription
companiesarrayyesDomains, LinkedIn URLs or names.
find_bystringyesWhat the values in `companies` are.
maxinteger–Decision makers per company. Defaults to 10.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).

No output schema declared.

No examples provided.

scrupp_find_emails ~70

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.

NameTypeReqDescription
peoplearrayyes–
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).

No output schema declared.

No examples provided.

scrupp_get_job ~56

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.

NameTypeReqDescription
job_idintegeryesThe job id returned by an extraction tool.

No output schema declared.

No examples provided.

scrupp_lookup_company ~92

Company data — size, industry, location, website, LinkedIn — from a domain, a company LinkedIn URL, or a name.

NameTypeReqDescription
companiesarrayyesDomains, LinkedIn URLs or names.
lookup_bystringyesWhat the values in `companies` are.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).

No output schema declared.

No examples provided.

scrupp_run_apollo_search ~132

Extract the people from an Apollo search URL. Requires a connected Apollo account, passed as `account`.

NameTypeReqDescription
accountstringyesConnected Apollo account email. Required.
maxinteger–Upper bound on records. Drives the credit hold; unused credits are refunded. Defaults to 100.
urlstringyesThe search URL, copied from the platform after building the filters.
wait_secondsinteger–How long to wait for the job before returning its id instead (default 120).
with_emailsboolean–Also find work email addresses. Defaults to true.

No output schema declared.

No examples provided.

scrupp_verify_emails ~70

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).

NameTypeReqDescription
emailsarrayyesAddresses to verify, at most 100 per call.

No output schema declared.

No examples provided.

Install

How do I install the io.github.wismhero-maker/scrupp MCP server?

io.github.wismhero-maker/scrupp runs locally as an npm package, launched with npx -y scrupp-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · scrupp-mcp-server

# add to Claude Code
claude mcp add wismhero-maker-scrupp -- npx -y scrupp-mcp-server
Common questions

What is the io.github.wismhero-maker/scrupp MCP server?

io.github.wismhero-maker/scrupp is an MCP server listed in the public MCP registry as io.github.wismhero-maker/scrupp. Export LinkedIn, Sales Navigator and Apollo searches; find decision makers and verified work emails. This page covers its npm package (scrupp-mcp-server).

Is the io.github.wismhero-maker/scrupp MCP server safe to use?

io.github.wismhero-maker/scrupp scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.wismhero-maker/scrupp MCP server expose?

io.github.wismhero-maker/scrupp exposes 10 tools: scrupp_export_sales_navigator_search, scrupp_export_linkedin_search, scrupp_run_apollo_search, scrupp_enrich_linkedin_profiles, scrupp_lookup_company, and 5 more. Their descriptions and schemas cost roughly 972 tokens of context every time the server is loaded.

Is the io.github.wismhero-maker/scrupp MCP server still maintained?

io.github.wismhero-maker/scrupp is still listed as active in the MCP registry. We last reached this channel on 17 October 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.wismhero-maker/scrupp MCP server under?

io.github.wismhero-maker/scrupp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.