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.CloudCorpRecords/payport

NPM · @RENETURCIOS/PAYPORT · 2 COMPONENTS

Customers, products, prices, invoices, and payments through the Stripe API.

64 Trust /100

Last scanned (6 hours ago)

Scores higher than 32% of npm servers

Category Finance and Payments

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1175 tokens (~55/item across 21 items; 21 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "create_refund" implies "refund" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 21 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
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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 63

    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 5 Nov 2026 · Analysed npm/@reneturcios/payport@0.1.0

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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 21 exposed · ~1,175 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
cancel_subscription ~28

Cancel a subscription in Stripe.

NameTypeReqDescription
subscriptionstringyesThe ID of the subscription to cancel.

No output schema declared.

No examples provided.

create_coupon ~140

Create a coupon in Stripe.

NameTypeReqDescription
amount_offinteger–The fixed amount off in the smallest currency unit, such as cents, when not using a percentage discount.
currencystring–The three-letter ISO currency code for a fixed-amount discount.
durationstringyesHow long the discount applies: 'once', 'repeating', or 'forever'.
duration_in_monthsinteger–The number of months the discount repeats for when duration is 'repeating'.
namestring–The name of the coupon displayed to customers on invoices.
percent_offnumber–The percentage discount the coupon applies.

No output schema declared.

No examples provided.

create_customer ~36

Create a customer in Stripe.

NameTypeReqDescription
emailstring–The customer's email address.
namestringyesThe customer's full name.

No output schema declared.

No examples provided.

create_invoice ~56

Create a draft invoice for a customer in Stripe.

NameTypeReqDescription
customerstringyesThe ID of the customer to create the invoice for.
days_until_dueinteger–The number of days from issuance until the invoice payment is due.

No output schema declared.

No examples provided.

create_invoice_item ~74

Add a priced line item to a draft invoice in Stripe.

NameTypeReqDescription
customerstringyesThe ID of the customer the invoice item belongs to.
invoicestringyesThe ID of the draft invoice to add this item to.
pricestringyesThe ID of the price that determines the invoice item amount.

No output schema declared.

No examples provided.

create_payment_link ~76

Create a payment link in Stripe for a price and quantity.

NameTypeReqDescription
pricestringyesThe ID of the price to sell through the payment link.
quantityintegeryesThe quantity of the price to include in the payment link.
redirect_urlstring–The URL to redirect the customer to after a successful payment.

No output schema declared.

No examples provided.

create_price ~69

Create a price for a product in Stripe.

NameTypeReqDescription
currencystringyesThe three-letter ISO currency code for the price.
productstringyesThe ID of the product this price belongs to.
unit_amountintegeryesThe unit amount in the smallest currency unit, such as cents.

No output schema declared.

No examples provided.

create_product ~38

Create a product in Stripe.

NameTypeReqDescription
descriptionstring–A description of the product.
namestringyesThe name of the product.

No output schema declared.

No examples provided.

create_refund ~62

Create a refund for a payment intent in Stripe.

NameTypeReqDescription
amountinteger–The amount to refund in the smallest currency unit, such as cents; omit for a full refund.
payment_intentstringyesThe ID of the payment intent to refund.

No output schema declared.

No examples provided.

finalize_invoice ~36

Finalize a draft invoice in Stripe so it can be paid.

NameTypeReqDescription
invoicestringyesThe ID of the draft invoice to finalize.

No output schema declared.

No examples provided.

list_coupons ~29

List coupons in Stripe.

NameTypeReqDescription
limitinteger–The maximum number of coupons to return.

No output schema declared.

No examples provided.

list_customers ~46

List customers in Stripe, optionally filtered by email.

NameTypeReqDescription
emailstring–Filter customers by this email address.
limitinteger–The maximum number of customers to return.

No output schema declared.

No examples provided.

list_disputes ~70

List disputes in Stripe, optionally filtered by charge or payment intent.

NameTypeReqDescription
chargestring–Filter disputes to those for this charge ID.
limitinteger–The maximum number of disputes to return.
payment_intentstring–Filter disputes to those for this payment intent ID.

No output schema declared.

No examples provided.

list_invoices ~49

List invoices in Stripe, optionally for one customer.

NameTypeReqDescription
customerstring–Filter invoices to those belonging to this customer ID.
limitinteger–The maximum number of invoices to return.

No output schema declared.

No examples provided.

list_payment_intents ~53

List payment intents in Stripe, optionally for one customer.

NameTypeReqDescription
customerstring–Filter payment intents to those belonging to this customer ID.
limitinteger–The maximum number of payment intents to return.

No output schema declared.

No examples provided.

list_prices ~48

List prices in Stripe, optionally for one product.

NameTypeReqDescription
limitinteger–The maximum number of prices to return.
productstring–Filter prices to those belonging to this product ID.

No output schema declared.

No examples provided.

list_products ~27

List products in Stripe.

NameTypeReqDescription
limitinteger–The maximum number of products to return.

No output schema declared.

No examples provided.

list_subscriptions ~64

List subscriptions in Stripe, optionally filtered by customer or status.

NameTypeReqDescription
customerstring–Filter subscriptions to those belonging to this customer ID.
limitinteger–The maximum number of subscriptions to return.
statusstring–Filter subscriptions by this subscription status.

No output schema declared.

No examples provided.

retrieve_balance ~14

Retrieve the Stripe account balance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

update_dispute ~80

Update a dispute in Stripe with evidence, optionally submitting it.

NameTypeReqDescription
disputestringyesThe ID of the dispute to update.
evidenceobject–Evidence to submit for the dispute as a map of evidence field names to their values.
submitboolean–Whether to submit the evidence to the bank and close evidence submission for the dispute.

No output schema declared.

No examples provided.

update_subscription ~80

Update a subscription in Stripe, for example its price or cancellation timing.

NameTypeReqDescription
cancel_at_period_endboolean–Whether to cancel the subscription at the end of the current billing period instead of immediately.
pricestring–The ID of the new price to switch the subscription to.
subscriptionstringyesThe ID of the subscription to update.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/payport MCP server?

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

npm · @reneturcios/payport

# add to Claude Code
claude mcp add cloudcorprecords-payport -- npx -y @reneturcios/payport
Common questions

What is the io.github.CloudCorpRecords/payport MCP server?

io.github.CloudCorpRecords/payport is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/payport. Customers, products, prices, invoices, and payments through the Stripe API. This page covers its npm package (@reneturcios/payport).

Is the io.github.CloudCorpRecords/payport MCP server safe to use?

io.github.CloudCorpRecords/payport scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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.CloudCorpRecords/payport MCP server expose?

io.github.CloudCorpRecords/payport exposes 21 tools: create_customer, list_customers, create_product, list_products, create_price, and 16 more. Their descriptions and schemas cost roughly 1,175 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/payport MCP server still maintained?

io.github.CloudCorpRecords/payport is still listed as active in the MCP registry. We last reached this channel on 5 November 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.CloudCorpRecords/payport MCP server under?

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