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.

OFAC SDN Screening

REMOTE · BONISSYSTEMS.COM

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

Available components

0 this week 78 Trust /100

Last scanned (20 hours ago)

Scores higher than 71% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 320 tokens (~160/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

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 21 Nov 2026 · Probed https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bonissystems.com CN=YE1,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 6d0f95770f49dd11e184ecfd671219da122
SANs: *.bonissystems.com, bonissystems.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bonissystems.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
bonissystems.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.gstatic.com https://images.dmca.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://res.cloudinary.com https://utfs.io https://uploadthing.com https://lh3.googleusercontent.com https://storage.googleapis.com https://blockstream.info https://images.dmca.com https://*.tile.openstreetmap.org; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' blob: https://api.anthropic.com https://bonissystems.com https://cloudflareinsights.com https://*.cloudinary.com https://*.polyhaven.org https://www.gstatic.com https://storage.googleapis.com https://blockstream.info https://*.livekit.cloud wss://*.livekit.cloud; media-src 'self' blob: https://res.cloudinary.com https://storage.googleapis.com; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp Verified 200
http (plaintext) http://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp HTTPS enforced 302 https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp
MCP tools · 2 exposed · ~242 tokens

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 →

Tool Tokens
get_sdn_list_meta ~99

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

screen_sdn ~143

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.

NameTypeReqDescription
countrystring–Optional country to narrow matches.
identifierstring–Optional government/registration identifier.
namestringyesThe name to screen (person, entity, vessel, or aircraft).
sdnTypestring–Optional SDN record type.

No output schema declared.

No examples provided.

Install

How do I install the OFAC SDN Screening MCP server?

OFAC SDN Screening is a hosted endpoint at https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · bonissystems.com

# add to Claude Code
claude mcp add --transport http com-bonissystems-ofac-sdn-screening 'https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp'
Common questions

What is the OFAC SDN Screening MCP server?

OFAC SDN Screening is an MCP server listed in the public MCP registry as com.bonissystems/ofac-sdn-screening. Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination. This page covers its hosted endpoint (https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp).

Is the OFAC SDN Screening MCP server safe to use?

OFAC SDN Screening scores 78 out of 100 on VerifyMCP. 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 OFAC SDN Screening MCP server expose?

OFAC SDN Screening exposes 2 tools: get_sdn_list_meta, screen_sdn. Their descriptions and schemas cost roughly 242 tokens of context every time the server is loaded.

Does the OFAC SDN Screening MCP server require authentication?

No. We connected to OFAC SDN Screening without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the OFAC SDN Screening MCP server still maintained?

OFAC SDN Screening is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the OFAC SDN Screening MCP server?

VerifyMCP ran 12 checks on OFAC SDN Screening, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about OFAC SDN Screening: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.