@easylabs/mcp-server

MCPcommunitylive
v0.5.0UnknownMITUpdated 6d agonpmGitHub

Easy Labs MCP Server - Payment processing tools for AI agents

Endpoint healthlive
checked 3 days ago · 204ms · 2 endpoints
100% of the last 1 check reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). 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 →
337Downloads/wk
6d agoLast update
Reads these credentials
  • EASY_API_KEYAPI keyoptional

    Easy API key (sk_...). Omit and set EASY_ENVIRONMENT=demo to explore sample data with no account.

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
AuthorUnknown
LicenseMIT
Version0.5.0
Sourcenpm+mcp-registry
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 surface14 tools · none privileged
Security scan✓ Cleanv0.5.0 · 4d agoHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

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

Tools

14 tools · none privileged
Statically extracted from the published packagev0.5.0 · 4d 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.

find_customerFind a customer by email or name (case-insensitive substring match) and show the best match's profile with recent payment activity. Use get_customer only when you already have a customer id.

Find a customer by email or name (case-insensitive substring match) and show the best match's profile with recent payment activity. Use get_customer only when you already have a customer id.

No input schema was published for this tool.

get_balance_transferGet a balance transfer by ID.

Get a balance transfer by ID.

No input schema was published for this tool.

get_customerGet a customer by ID.

Get a customer by ID.

No input schema was published for this tool.

get_disputeGet a single dispute by ID.

Get a single dispute by ID.

No input schema was published for this tool.

get_settlementGet a single settlement by ID.

Get a single settlement by ID.

No input schema was published for this tool.

get_transferGet a single transfer by ID.

Get a single transfer by ID.

No input schema was published for this tool.

list_balance_transfersList balance transfers.

List balance transfers.

No input schema was published for this tool.

list_customersList customers with pagination.

List customers with pagination.

No input schema was published for this tool.

list_disputesList disputes with optional state filter.

List disputes with optional state filter.

No input schema was published for this tool.

list_settlementsList settlements with pagination.

List settlements with pagination.

No input schema was published for this tool.

list_transfersList recent transfers with optional filters.

List recent transfers with optional filters.

No input schema was published for this tool.

merchant_application_checklistEverything a business needs to gather before applying for an Easy merchant account — the 7 application steps with required information for each. Use this to prepare someone so the application takes ~10 minutes in one sitting. Do NOT collect SSN/EIN/bank details in conversation; the checklist explai…

Everything a business needs to gather before applying for an Easy merchant account — the 7 application steps with required information for each. Use this to prepare someone so the application takes ~10 minutes in one sitting. Do NOT collect SSN/EIN/bank details in conversation; the checklist explai…

No input schema was published for this tool.

explain_application_stepExplains one step of the Easy merchant application in plain English: what's asked, why it's required (KYB/underwriting context), and what to have ready. Steps 1-7: business details, business type, tax details, owners, merchant settings, processing volume, review & terms.

Explains one step of the Easy merchant application in plain English: what's asked, why it's required (KYB/underwriting context), and what to have ready. Steps 1-7: business details, business type, tax details, owners, merchant settings, processing volume, review & terms.

No input schema was published for this tool.

revenue_summaryRevenue summary for a period (7d, 30d, 90d, 6m, 12m, or mtd): gross volume, transfer counts by status, average ticket, and change versus the previous equal-length period. Use this before reaching for list_transfers when the question is about overall performance.

Revenue summary for a period (7d, 30d, 90d, 6m, 12m, or mtd): gross volume, transfer counts by status, average ticket, and change versus the previous equal-length period. Use this before reaching for list_transfers when the question is about overall performance.

No input schema was published for this tool.

14 of 14 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

Easy Labs MCP Server - Payment processing tools for AI agents

Keywords
mcppaymentseasy-labs
Alternatives
Comparing tool surfaces…

Dependency tree

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

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

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

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

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

+41 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.

Topics

Related in payments & commerce