OFAC SDN Screening

com.bonissystemsPublished by bonissystems.comOfficial publisherv1.0.0Updated Oct 24, 2026

Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.

The publisher's own server: Booking Request

VerifiedStreamable HTTPWeb executableFinance Security & Monitoring

Server details

Identifier: com.bonissystems/ofac-sdn-screening
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to bonissystems.com, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.bonissystems%2Fofac-sdn-screening.svg)](https://sourceweft.com/mcp/com.bonissystems%2Fofac-sdn-screening?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant screen a name against a dated snapshot of the public U.S. Treasury OFAC SDN list and check the snapshot's provenance and freshness.

What you can do: Provides two tools. screen_sdn screens a name against a dated snapshot of the public OFAC SDN list and returns one of three verdicts — match, possible_match, or no_match — with ranked matches, the OFAC list entry, and the field that matched. get_sdn_list_meta reports the snapshot's provenance and freshness: source URL, publish date, record count, fetch time, source and index content hashes, and how many days old the snapshot is against a 14-day staleness threshold. The server presents information, not a compliance determination.
When to use it: Useful when an assistant needs a quick first-pass name check against the OFAC SDN list, or needs to confirm how current and where the underlying list snapshot came from before relying on a result. Results are informational and are meant to feed human review rather than replace it.
Requirements: A remote streamable HTTP endpoint at bonissystems.com; no packages, environment variables, headers, or authentication are declared. Network access to the endpoint is required.

Before you install

A potential match requires human review and the output is information, not a compliance determination, so do not treat verdicts as legal or regulatory clearance. Screening queries are sent to a third-party remote service; the screen_sdn path states the query is not stored or anchored, but the meta tool's freshness flag keys on fetch age rather than publish age, so check snapshot age before relying on results.

Installation

In SourceWeft

Open OFAC SDN Screening in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bonissystems%2Fofac-sdn-screening/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ofac-sdn-screening": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp"
    }
  }
}

Tools

get_sdn_list_meta

Return the provenance AND the freshness of the loaded OFAC SDN list: source URL, publish date, record count, fetch time, the source + index content hashes, and how many days old the snapshot is against a 14-day staleness threshold (the flag keys on fetch age, not publish age). No input, no PII. Use this to confirm which list version a screening ran against, and how current it is.

Takes no parameters.

screen_sdn

Screen a name against a dated snapshot of the public OFAC SDN list. Returns one of three verdicts — match, possible_match, or no_match — and ranked matches with the OFAC list entry and the field that matched. The query is NOT stored or anchored on this path. A potential match requires human review — it is information, not a legal or compliance determination.

ParametersnamerequiredcountrysdnTypeidentifier

Version history

v1.0.0LatestSep 16, 2026

Score

83% 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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.