npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

global-intel-exchange-mcp

v0.1.1

Published

MCP server exposing the Global Intelligence Exchange x402 API (US sanctions screening, NVD CVE lookups, SEC/Companies House company checks) as tools for Claude and other MCP hosts. Pays per query with your own wallet via x402/USDC on Base.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jkigimajkigima

Keywords

mcpmodel-context-protocolx402sanctionscvecomplianceclaudeagent

Readme

global-intel-exchange-mcp

MCP server for the Global Intelligence Exchange x402 API — exposes real US sanctions screening, NVD CVE lookups, and SEC/Companies House company checks as tools any MCP-compatible agent (Claude Desktop, Claude Code, and others) can call directly.

Every call is a real, paid request — settled in USDC on Base, using a wallet you control. This server never holds funds itself.

Tools

  • sanctions_screening — US Consolidated Screening List (OFAC SDN, BIS Denied Persons/Entity List, State Dept lists)
  • cve_lookup — NIST National Vulnerability Database
  • company_registry_check — SEC EDGAR (US) + UK Companies House, checked in parallel

Setup

1. Get a wallet with USDC on Base

Create a new wallet (Coinbase Wallet or MetaMask), export its private key (0x...), and fund it with a small amount of USDC on Base mainnet (each query costs $0.02–$0.05). Use a dedicated wallet, not your main one.

2. Install

npm install -g global-intel-exchange-mcp

3. Configure Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (Mac) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "global-intel-exchange": {
      "command": "global-intel-exchange-mcp",
      "env": {
        "WALLET_PRIVATE_KEY": "0xyour-private-key-here"
      }
    }
  }
}

Restart Claude Desktop. The three tools will now be available.

4. Configure Claude Code

claude mcp add global-intel-exchange \
  -e WALLET_PRIVATE_KEY=0xyour-private-key-here \
  -- global-intel-exchange-mcp

Security

Your private key is only used locally to sign x402 payment authorizations. It is never sent to Global Intelligence Exchange. Fund the wallet with only what you're comfortable spending — there is no spending cap enforced by this server. Treat WALLET_PRIVATE_KEY like any other secret.

Data accuracy

Every response includes dataSource: LIVE_VERIFIED or dataSource: AI_ESTIMATE_UNVERIFIED — never mistake an unverified estimate for a real registry finding. See DATA_SOURCES.md for full coverage details per vector.

Links