Global Intel Exchange

io.github.Joseph-CEOPublished by GitHub account Joseph-CEOv0.1.1Updated Oct 25, 2026

Real-time sanctions screening, CVE, and company registry checks for agents.

The publisher's own server: Exchange.news — Crypto offers, campaigns and news

Overview

AI-generated overview

A local MCP server that gives an assistant real-time sanctions screening, CVE lookups and company registry checks.

What you can do
Screen names and entities against sanctions lists in real time, according to the registry description, which is the only source available for its capabilities. Look up CVE vulnerability information. Check company registry records. The manifest lists no tools, so the exact operations and their inputs are not documented here.
When to use it
Worth considering when an assistant needs compliance-style checks, such as screening a party against sanctions lists, looking up a CVE, or verifying a company's registry details during a workflow.
Requirements
Runs as a local process over stdio, installed from the npm package global-intel-exchange-mcp, so Node.js and npm are needed. No authentication, environment variables or headers are declared. Network access is implied by the real-time lookups but not stated.
Before you install
The manifest declares no credentials, but the server performs live lookups against third-party sanctions, CVE and company registry sources, so the queries you make may be sent to those services. No tool list or documentation is provided, so what data it sends and whether it writes anything cannot be verified before installing.

Installation

In SourceWeft

  1. Open Global Intel Exchange in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Exchange integrations