Skills/npm/contact-verify-mcp

contact-verify-mcp@1.1.0

VERIFIED

Publisher claims: "Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher workers · publishing for 37 daysInstalls 0Last detonated 5 h ago
$claude mcp add contact-verify-mcp -- npx -y contact-verify-mcp
WatchReport an issue

Coverage

Server started and answered tools/list.
Tested
MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested
what the tools do when called with real credentials

Before you give it your token

It will ask for
EVM_PRIVATE_KEY
Where it talks to
no vendor host named in the codeAlso workers.dev — not the publisher's domain; check what for before connecting.
What we saw when it ran
no credential files read · no network
What we could not test
what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names workers.dev as well as its own vendor. The guard injects EVM_PRIVATE_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

$vet-skills run --net declared -- npx -y contact-verify-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-22 and scored it 93/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 57 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
36sprocessdependency install exit 0
56sclaimed7 tools: verify_email, verify_email_basic, verify_email_batch, preview_email, verify_domain, verify_sender, lookup_phone
56stoolsf42534ddbca70709
56stools01dc96faa05fc1fa
56stools8cea7fede4baff9b
56stoolsbe20fdb4d9106fec
56stools86796fb72c15a33b
56stoolsffb347c73c7211c6
56stoolsb14c7cbbd0ca2385
56sprocessscript backend runs setup only
56sprocessno install scripts to re-run

Static findings

No findings across 847 lines in 18 files.

Cost to the agent

Instructions loaded
≈72 tok
1 file · 18 in bundle
Tool list per prompt
≈1,152 tok
7 tools · 165 per tool
Handshake
1245 ms
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 233

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for contact-verify-mcp@1.1.0 as of 5 h ago. This is the package itself, not its dependencies.

contact-verify-mcp@1.1.0 safety verdict: Verified — KillerSkills