Pexcard Engineering MCP Server

@pexcard_engineering/mcp npm v1.0.3

Published by @pexcard_engineering — 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.

MCP server for PEX API - access business accounts, cards, transactions, and more

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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
A Why this grade threat 100 − adoption risk = 96/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 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. 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
−3 capability blast radius (moderate) — 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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 72

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

  • pex_get_cardholder_provisioning_modereads sensitive data
  • pex_get_token_provisioning_modereads sensitive data
  • pex_get_account_balanceno sensitive capability
  • pex_get_account_detailsno sensitive capability
  • pex_get_account_remaining_limitsno sensitive capability
  • pex_get_advanced_account_detailsno sensitive capability
  • pex_get_advanced_spending_rulesetno sensitive capability
  • pex_get_advanced_spending_ruleset_cardsno sensitive capability
  • pex_get_all_account_detailsno sensitive capability
  • pex_get_all_cardholder_transactionsno sensitive capability
Show 62 more tools ↓
  • pex_get_auth_tokensno sensitive capability
  • pex_get_billno sensitive capability
  • pex_get_bill_payment_requestno sensitive capability
  • pex_get_bill_paymentsno sensitive capability
  • pex_get_business_adminno sensitive capability
  • pex_get_business_adminsno sensitive capability
  • pex_get_business_balanceno sensitive capability
  • pex_get_business_bank_accountno sensitive capability
  • pex_get_business_billingno sensitive capability
  • pex_get_business_linkedno sensitive capability
  • pex_get_business_my_profileno sensitive capability
  • pex_get_business_one_time_transferno sensitive capability
  • pex_get_business_profileno sensitive capability
  • pex_get_business_settingsno sensitive capability
  • pex_get_business_tagno sensitive capability
  • pex_get_business_tagsno sensitive capability
  • pex_get_business_transactionno sensitive capability
  • pex_get_business_transactionsno sensitive capability
  • pex_get_callback_subscriptionno sensitive capability
  • pex_get_callback_typesno sensitive capability
  • pex_get_cardno sensitive capability
  • pex_get_card_advanced_spend_rulesno sensitive capability
  • pex_get_card_load_limit_remainingno sensitive capability
  • pex_get_card_orderno sensitive capability
  • pex_get_card_ordersno sensitive capability
  • pex_get_card_scheduled_funding_rulesno sensitive capability
  • pex_get_card_spend_rulesno sensitive capability
  • pex_get_cardholder_declinesno sensitive capability
  • pex_get_cardholder_network_transactionsno sensitive capability
  • pex_get_cardholder_purchaseno sensitive capability
  • pex_get_cardholder_purchasesno sensitive capability
  • pex_get_cardholder_transactionno sensitive capability
  • pex_get_cardholder_transactionsno sensitive capability
  • pex_get_credit_linesno sensitive capability
  • pex_get_current_tokenno sensitive capability
  • pex_get_group_cardholdersno sensitive capability
  • pex_get_invoice_allocationsno sensitive capability
  • pex_get_invoice_paymentsno sensitive capability
  • pex_get_invoicesno sensitive capability
  • pex_get_issued_tokensno sensitive capability
  • pex_get_mcc_categoriesno sensitive capability
  • pex_get_network_transactionsno sensitive capability
  • pex_get_partnerno sensitive capability
  • pex_get_payment_requestno sensitive capability
  • pex_get_payment_transferno sensitive capability
  • pex_get_paymentsno sensitive capability
  • pex_get_spending_rulesetno sensitive capability
  • pex_get_spending_ruleset_cardsno sensitive capability
  • pex_get_transaction_attachmentno sensitive capability
  • pex_get_transaction_attachmentsno sensitive capability
  • pex_get_transaction_detailno sensitive capability
  • pex_get_transaction_detailsno sensitive capability
  • pex_get_transaction_tagsno sensitive capability
  • pex_get_vendorno sensitive capability
  • pex_get_vendor_card_orderno sensitive capability
  • pex_list_advanced_spending_rulesetsno sensitive capability
  • pex_list_callback_subscriptionsno sensitive capability
  • pex_list_groupsno sensitive capability
  • pex_list_spending_rulesetsno sensitive capability
  • pex_list_tokensno sensitive capability
  • pex_list_vendorsno sensitive capability
  • pex_search_billsno sensitive capability

What this scan could not see

Versions 1

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
v1.0.3 latest A 96/100 0 1.13.0 2026-09-08

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: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/pexcard-engineering-mcp/badge.svg)](https://mcptrustchecker.com/registry/pexcard-engineering-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/pexcard-engineering-mcp"><img src="https://mcptrustchecker.com/registry/pexcard-engineering-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/pexcard-engineering-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 @pexcard_engineering/mcp --online

Use the free API → How scoring works

More in Finance & Commerce