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.

Maxwell Directory (x402 + MCP)

NPM · @MAXWELLINTL/X402-MCP · 2 COMPONENTS · SCANNED OCT 8

Local providers worldwide, plus travel and public data. Free search; paid answers via x402.

Available components

remote · api.maxwellinternational.ai 62 npm · @maxwellintl/x402-mcp 30
+10 this week 30 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 Security82
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 184 of 349 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 184 of 349 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency6
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 6 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.Unverified
Stability & Change Management0
  • Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 4 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the Maxwell Directory (x402 + MCP) server?

Maxwell Directory (x402 + MCP) runs locally as an npm package, launched with npx -y @maxwellintl/x402-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @maxwellintl/x402-mcp

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

  • 8 Oct 26 −1

    No change was recorded against any check on this day. Supply Chain Security went from 85 to 82.

  • 5 Oct 26 −4
    • Known CVEs: pass → partial ▼ security
    • Dependency health: 0.94 → partial functional
  • 2 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 1 Oct 26 20

    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 8 Oct 2026 · Analysed npm/@maxwellintl/x402-mcp@0.2.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 →

Dependencies 184 packages
Packages resolved 184
Stale 31
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 →

The sandbox run completed and this package exposed no tools.

Common questions

What is the Maxwell Directory (x402 + MCP) server?

Maxwell Directory (x402 + MCP) is listed in the public MCP registry as ai.maxwellinternational/data. Local providers worldwide, plus travel and public data. Free search; paid answers via x402. This page covers its npm package (@maxwellintl/x402-mcp).

Is the Maxwell Directory (x402 + MCP) server safe to use?

Maxwell Directory (x402 + MCP) scores 30 out of 100 on VerifyMCP. 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 Maxwell Directory (x402 + MCP) server expose?

Maxwell Directory (x402 + MCP) exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the Maxwell Directory (x402 + MCP) server still maintained?

Maxwell Directory (x402 + MCP) is still listed as active in the MCP registry. We last reached this channel on 8 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.