Bootpay MCP Server

@bootpay/mcp npm v2.10.1

Published by @bootpay — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Bootpay MCP Server — 결제·커머스 개발자 문서 검색, 관리자 도구, AI 에이전트 연동

Trust grade
C
73/100
Last scanned get badge →
Trust
C · 73/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
C Why this grade threat 84 − adoption risk = 73/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 15.8 = 84. What the published surface and source actually contain:

PointsWhat was foundCategory
−9.5 Untrusted input concatenated into a command sink ×2 MTC-SRC-009 injection
−6.3 Description names a credential store the tool cannot reach MTC-INJ-SCHEMA-1 injection

2. Client adoption risk — 84 − 11 = 73. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

high Shell/command execution in server code (dist/admin/tools/auth.js)MTC-SRC-002

In the server's implementation (`dist/admin/tools/auth.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } from 'node:child_process'; import { startCallbackServer } from '../auth/callback-server.js'; import { start

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/admin/tools/auth.js

high Shell/command execution in server code (dist/admin/tools/commerce-code/index.js)MTC-SRC-002

In the server's implementation (`dist/admin/tools/commerce-code/index.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execSync } from 'node:child_process'; import { formatErrorForMcp } from '../../errors/index.js'; import { startPayment

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/admin/tools/commerce-code/index.js

medium Hardcoded egress to an external endpoint (dist/admin/tools/generate-code.js)MTC-SRC-003

In the server's implementation (`dist/admin/tools/generate-code.js:1461`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ta: any) => { fetch('https://your-server.com/api/confirm', { method: 'POST', headers:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/admin/tools/generate-code.js

medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1

Tool "list_api_scopes" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.

Evidence: KeyChain

Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.

Location: tool list_api_scopes · description

medium Untrusted input concatenated into a command sink (dist/admin/tools/auth.js)MTC-SRC-009

In the server's implementation (`dist/admin/tools/auth.js:86`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`open "${loginUrl}"`, { stdio: 'ignore' }); browserOpened = true;

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/admin/tools/auth.js

medium Untrusted input concatenated into a command sink (dist/admin/tools/commerce-code/index.js)MTC-SRC-009

In the server's implementation (`dist/admin/tools/commerce-code/index.js:223`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { execSync(`open "${pageUrl}"`, { stdio: 'ignore' }); browserOpened = true;

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/admin/tools/commerce-code/index.js

Tools 163

Each tool and what it can reach — statically extracted from the published source.

  • commerce_download_couponingests untrusted input
  • activate_payment_methodno sensitive capability
  • add_products_to_catalogno sensitive capability
  • browser_loginno sensitive capability
  • browser_select_payment_methodno sensitive capability
  • browser_select_projectno sensitive capability
  • commerce_add_cart_itemno sensitive capability
  • commerce_add_review_helpfulno sensitive capability
  • commerce_calculate_guest_delivery_feeno sensitive capability
  • commerce_calculate_point_limitno sensitive capability
Show 153 more tools ↓
  • commerce_calculate_priceno sensitive capability
  • commerce_calculate_subscription_cancelno sensitive capability
  • commerce_check_business_number_existno sensitive capability
  • commerce_check_email_existno sensitive capability
  • commerce_check_id_existno sensitive capability
  • commerce_check_phone_existno sensitive capability
  • commerce_check_review_helpfulno sensitive capability
  • commerce_checkout_cartno sensitive capability
  • commerce_clear_cartno sensitive capability
  • commerce_create_order_cancelno sensitive capability
  • commerce_create_order_receiptno sensitive capability
  • commerce_create_productno sensitive capability
  • commerce_create_product_reviewno sensitive capability
  • commerce_create_review_replyno sensitive capability
  • commerce_delete_product_reviewno sensitive capability
  • commerce_delete_review_replyno sensitive capability
  • commerce_get_cartno sensitive capability
  • commerce_get_my_orderno sensitive capability
  • commerce_get_my_subscriptionno sensitive capability
  • commerce_get_order_receipt_previewno sensitive capability
  • commerce_get_order_resultno sensitive capability
  • commerce_get_order_subscription_resultno sensitive capability
  • commerce_get_point_balanceno sensitive capability
  • commerce_get_productno sensitive capability
  • commerce_get_productsno sensitive capability
  • commerce_get_review_replyno sensitive capability
  • commerce_get_review_statsno sensitive capability
  • commerce_get_reviewsno sensitive capability
  • commerce_get_sessionno sensitive capability
  • commerce_get_storeno sensitive capability
  • commerce_get_store_detailno sensitive capability
  • commerce_get_subscription_recovery_infono sensitive capability
  • commerce_get_termsno sensitive capability
  • commerce_joinno sensitive capability
  • commerce_list_available_couponsno sensitive capability
  • commerce_list_categoriesno sensitive capability
  • commerce_list_couponsno sensitive capability
  • commerce_list_my_ordersno sensitive capability
  • commerce_list_my_subscriptionsno sensitive capability
  • commerce_list_point_transactionsno sensitive capability
  • commerce_list_product_reviewsno sensitive capability
  • commerce_list_productsno sensitive capability
  • commerce_loginno sensitive capability
  • commerce_logoutno sensitive capability
  • commerce_merge_guest_cartno sensitive capability
  • commerce_pause_my_subscriptionno sensitive capability
  • commerce_prepare_orderno sensitive capability
  • commerce_preview_coupon_discountno sensitive capability
  • commerce_preview_guest_orderno sensitive capability
  • commerce_preview_point_usageno sensitive capability
  • commerce_recover_my_subscriptionno sensitive capability
  • commerce_remove_cart_itemno sensitive capability
  • commerce_remove_review_helpfulno sensitive capability
  • commerce_report_reviewno sensitive capability
  • commerce_request_subscription_cancel_approvalno sensitive capability
  • commerce_resume_my_subscriptionno sensitive capability
  • commerce_retry_my_subscription_billno sensitive capability
  • commerce_statusno sensitive capability
  • commerce_update_cart_itemno sensitive capability
  • commerce_update_cart_item_periodno sensitive capability
  • commerce_update_my_order_addressno sensitive capability
  • commerce_update_my_subscriptionno sensitive capability
  • commerce_update_productno sensitive capability
  • commerce_update_product_reviewno sensitive capability
  • commerce_update_review_replyno sensitive capability
  • commerce_validate_cart_itemsno sensitive capability
  • commerce_validate_credentialsno sensitive capability
  • commerce_verify_order_receiptno sensitive capability
  • configure_widgetno sensitive capability
  • create_catalogno sensitive capability
  • create_categoryno sensitive capability
  • create_content_blockno sensitive capability
  • create_content_templateno sensitive capability
  • create_delivery_shippingno sensitive capability
  • create_keychainno sensitive capability
  • create_productno sensitive capability
  • create_projectno sensitive capability
  • create_sellerno sensitive capability
  • create_subscription_settingno sensitive capability
  • create_test_productsno sensitive capability
  • create_widgetno sensitive capability
  • delete_catalogno sensitive capability
  • delete_categoryno sensitive capability
  • delete_content_blockno sensitive capability
  • delete_content_templateno sensitive capability
  • delete_keychainno sensitive capability
  • delete_productno sensitive capability
  • delete_widgetno sensitive capability
  • detect_project_stackno sensitive capability
  • disable_digital_codeno sensitive capability
  • generate_commerce_codeno sensitive capability
  • generate_payment_codeno sensitive capability
  • get_auth_statusno sensitive capability
  • get_catalogno sensitive capability
  • get_commerce_contextno sensitive capability
  • get_commerce_keysno sensitive capability
  • get_cs_guideno sensitive capability
  • get_csp_allowlistno sensitive capability
  • get_docno sensitive capability
  • get_integration_contextno sensitive capability
  • get_mall_settingno sensitive capability
  • get_payment_settingsno sensitive capability
  • get_productno sensitive capability
  • get_product_form_settingno sensitive capability
  • get_product_info_notice_formsno sensitive capability
  • get_sdk_versionsno sensitive capability
  • get_sellerno sensitive capability
  • get_setup_checklistno sensitive capability
  • get_troubleshootingno sensitive capability
  • get_widgetno sensitive capability
  • get_widget_default_stylesno sensitive capability
  • list_api_scopesno sensitive capability
  • list_catalogsno sensitive capability
  • list_categoriesno sensitive capability
  • list_content_block_productsno sensitive capability
  • list_content_blocksno sensitive capability
  • list_content_templatesno sensitive capability
  • list_delivery_shipping_bundlesno sensitive capability
  • list_delivery_shippingsno sensitive capability
  • list_digital_codesno sensitive capability
  • list_docsno sensitive capability
  • list_keychainsno sensitive capability
  • list_productsno sensitive capability
  • list_projectsno sensitive capability
  • list_subscription_settingsno sensitive capability
  • list_widgetsno sensitive capability
  • loginno sensitive capability
  • logoutno sensitive capability
  • register_digital_codesno sensitive capability
  • reorder_categoriesno sensitive capability
  • search_docsno sensitive capability
  • search_sellersno sensitive capability
  • set_commerce_credentialsno sensitive capability
  • set_payment_modeno sensitive capability
  • set_sandbox_modeno sensitive capability
  • set_tokenno sensitive capability
  • setup_test_mall_catalogsno sensitive capability
  • setup_test_mall_categoriesno sensitive capability
  • setup_test_mall_deliveryno sensitive capability
  • setup_test_mall_productsno sensitive capability
  • setup_test_mall_resetno sensitive capability
  • setup_test_mall_statusno sensitive capability
  • switch_projectno sensitive capability
  • update_catalogno sensitive capability
  • update_categoryno sensitive capability
  • update_content_blockno sensitive capability
  • update_mall_settingno sensitive capability
  • update_payment_resourceno sensitive capability
  • update_productno sensitive capability
  • update_sellerno sensitive capability
  • update_test_mall_discountsno sensitive capability
  • update_widgetno sensitive capability
  • upload_product_imagesno sensitive capability

What this scan could not see

Versions 5

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.10.1 latest C 73/100 6 1.13.0 2026-09-07
v2.10.0 C 73/100 6 1.13.0 2026-09-01
v2.6.3 C 73/100 6 1.13.0 2026-08-25
v2.6.1 C 73/100 6 1.12.1 2026-08-25
v2.1.0 C 73/100 6 1.12.1 2026-08-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: C · 73/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/bootpay-mcp/badge.svg)](https://mcptrustchecker.com/registry/bootpay-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/bootpay-mcp"><img src="https://mcptrustchecker.com/registry/bootpay-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bootpay-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @bootpay/mcp --online

Use the free API → How scoring works

More in Learning & Documentation