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.

ASG Card

NPM · @ASGCARD/MCP-SERVER · SCANNED SEP 29

Give AI agents autonomous virtual card management via x402 and Stellar USDC

Available components

npm · @asgcard/mcp-server 31
0 this week 31 Trust /100
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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects toml 3.0.0, reached via @stellar/stellar-sdk > toml. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 142 of 146 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the ASG Card MCP server?

ASG Card runs locally as an npm package, launched with npx -y @asgcard/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @asgcard/mcp-server

# add to Claude Code
claude mcp add asgcompute-asgcard-mcp-server -- npx -y @asgcard/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "asgcompute-asgcard-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@asgcard/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "asgcompute-asgcard-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@asgcard/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add asgcompute-asgcard-mcp-server -- npx -y @asgcard/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "asgcompute-asgcard-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@asgcard/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add asgcompute-asgcard-mcp-server --command npx --arg -y --arg @asgcard/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  asgcompute-asgcard-mcp-server:
    command: "npx"
    args: ["-y", "@asgcard/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "asgcompute-asgcard-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@asgcard/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add asgcompute-asgcard-mcp-server -t stdio -c npx -a -y @asgcard/mcp-server
// mcp.json
{
  "mcpServers": {
    "asgcompute-asgcard-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@asgcard/mcp-server"
      ]
    }
  }
}
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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 17 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 4 Sept 26 −2
    • CVE-2026-63376 affects this package: high ▼ security
    • CVE-2026-77465 affects this package: high ▼ security
    • Known CVEs: partial → fail ▼ security
  • 3 Sept 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 2 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 29 Sept 2026 · Analysed npm/@asgcard/mcp-server@0.5.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 2 findings
ID CVE Severity Vector Fix available
GHSA-82x6-q7mm-w9cf CVE-2026-77465 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-v5mp-jgw5-2x6j CVE-2026-63376 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 142 packages
Packages resolved 142
Deprecated 1
Stale 49
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the ASG Card MCP server?

ASG Card is an MCP server listed in the public MCP registry as io.github.ASGCompute/asgcard-mcp-server. Give AI agents autonomous virtual card management via x402 and Stellar USDC. This page covers its npm package (@asgcard/mcp-server).

Is the ASG Card MCP server safe to use?

ASG Card scores 31 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 29 September 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.

Is the ASG Card MCP server still maintained?

ASG Card is still listed as active in the MCP registry. We last reached this channel on 29 September 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 ASG Card MCP server under?

ASG Card declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.