npm:opensanctions-mcp

Item: npm:opensanctions-mcp
Rating: 74
Author: wmcp.sh

https://www.npmjs.com/package/opensanctions-mcp

74/100 · MCP Trust Grade · checked 4h ago · MCP 0.1.2

What it offers — 6 tools · Database

search_entities

Search the OpenSanctions database by name or keyword. Returns matching entities ordered by relevance. Use this for exploratory queries:

match_entity

Screen a person or company against sanctions and PEP (Politically Exposed Person) lists using structured properties. This is the primary screening too

get_entity

Fetch complete details for a specific entity by ID, including all properties, dataset memberships, and relationships to other entities. Use this after

list_datasets

List available sanctions and PEP datasets in OpenSanctions. No API key required. Returns dataset names, titles, summaries, and entity counts. Use the

get_dataset

Get full details about a specific dataset: description, publisher, entity count, last updated, and coverage information. No API key required. Use list

investigate_entity

Run a multi-step compliance investigation on a person or company. This is the most powerful tool \u2014 it combines matching, entity details, and rela

Spec / packaging20%100

✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 6 tool(s) detected in source

Security (OWASP MCP)30%25

⚠ references sensitive file paths / env secrets
scanned 1 source file

Maintenance / popularity20%92

published within 90 days
3 published versions

Tool hygiene15%95

✓ ships TypeScript types
2 runtime deps

Transparency / provenance15%90

✓ public repository linked
✓ MIT license

Findings

WARNMCP08 References sensitive file paths / environment secrets.

INFO Static analysis of npm package opensanctions-mcp@0.1.2 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.

Grade another server

We re-grade npm:opensanctions-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — npm:opensanctions-mcp grade C

Share on X Open card image

https://wmcp.sh/mcp/grade/npm%3Aopensanctions-mcp

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade C](https://wmcp.sh/mcp/grade/npm%3Aopensanctions-mcp/badge.svg)](https://wmcp.sh/mcp/grade/npm%3Aopensanctions-mcp)

HTML

<a href="https://wmcp.sh/mcp/grade/npm%3Aopensanctions-mcp"><img src="https://wmcp.sh/mcp/grade/npm%3Aopensanctions-mcp/badge.svg" alt="MCP Trust Grade C · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.