contact-verify-mcp

MCPcommunity

v1.1.0dev.workers.okwithit9.verify-x402MITUpdated 8d agonpm

Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

367Downloads/wk

8d agoLast update

Needs 1 credential before it runs

EVM_PRIVATE_KEYAPI keyrequired
Base mainnet wallet private key. The server spends USDC from this wallet.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package

Authordev.workers.okwithit9.verify-x402

LicenseMIT

Version1.1.0

Sourcenpm+mcp-registry

npmcontact-verify-mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface8 tools · none privileged

Security scan✓ Cleanv1.1.0 · 7d agoHow well does this scan work?

EvalsNone

IndexedOct 17, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged

Statically extracted from the published packagev1.1.0 · 7d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

verify_emailNo description published

This tool published no description. Forge does not invent one.

verify_email_basicNo description published

This tool published no description. Forge does not invent one.

verify_email_batchNo description published

This tool published no description. Forge does not invent one.

preview_emailNo description published

This tool published no description. Forge does not invent one.

verify_domainNo description published

This tool published no description. Forge does not invent one.

verify_senderNo description published

This tool published no description. Forge does not invent one.

verify_breachNo description published

This tool published no description. Forge does not invent one.

lookup_phoneNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Contact Verify (verify-x402). Basic $0.002, domain $0.02, sender $0.025.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

8 tools · none privileged · observed 2026-10-19 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

verify_email
verify_email_basic
verify_email_batch
preview_email
verify_domain
verify_sender
verify_breach
lookup_phone

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-19 — observed resolution, not a publisher declaration.

60 packages resolved · 6 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod3.25.76
viem2.57.78 dependencies
- ox0.14.56+4 not drawn4 dependencies
  - @scure/bip321.7.0+2 not drawn1 dependency
    @noble/hashes1.8.0
  - @scure/bip391.6.0+1 not drawn1 dependency
    @noble/hashes1.8.0shown above
  - @noble/curves1.9.11 dependency
    @noble/hashes1.8.0shown above
  - @noble/hashes1.8.0shown above
- ws8.21.0
- isows1.0.7
- abitype1.2.3
- @scure/bip321.7.0shown above+2 not drawn
- @scure/bip391.6.0shown above+1 not drawn
- @noble/curves1.9.1shown above
- @noble/hashes1.8.0shown above
@x402/evm2.28.03 dependencies
- zod3.25.76shown above
- viem2.57.7shown above
- @x402/core2.28.01 dependency
  - zod3.25.76shown above
@x402/core2.28.0shown above
@x402/fetch2.28.01 dependency
- @x402/core2.28.0shown above
@modelcontextprotocol/sdk1.32.1+7 not drawn10 dependencies
- ajv8.20.0+4 not drawn
- zod4.6.7
- cors2.8.6+2 not drawn
- hono4.13.13
- jose6.2.12
- express5.3.0incomplete+20 not drawn
- raw-body3.0.2incomplete
- ajv-formats3.0.1incomplete
- cross-spawn7.0.6incomplete
- eventsource3.0.7incomplete

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

59 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 59

escape-html ^1.0.3 — required by express@5.3.0package cap reached
http-errors ^2.0.0 — required by express@5.3.0package cap reached
on-finished ^2.4.1 — required by express@5.3.0package cap reached
content-type ^2.0.0 — required by express@5.3.0package cap reached
finalhandler ^2.1.0 — required by express@5.3.0package cap reached
range-parser ^1.2.1 — required by express@5.3.0package cap reached
serve-static ^2.2.0 — required by express@5.3.0package cap reached
cookie-signature ^1.2.1 — required by express@5.3.0package cap reached
merge-descriptors ^2.0.0 — required by express@5.3.0package cap reached
content-disposition ^2.0.1 — required by express@5.3.0package cap reached
bytes ~3.1.2 — required by raw-body@3.0.2package cap reached
unpipe ~1.0.0 — required by raw-body@3.0.2package cap reached

+47 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.