Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://bonissystems.com/api/knox/agents/ofac-sdn-screening/mcp2 tools · 279msget_sdn_list_metaReturn 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…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…
No input schema was published for this tool.
screen_sdnScreen 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…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…
| Parameter | Type | Description |
|---|---|---|
| name* | string | The name to screen (person, entity, vessel, or aircraft). |
| country | string | Optional country to narrow matches. |
| identifier | string | Optional government/registration identifier. |
| sdnType | string | Optional SDN record type. |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Screen a name against the U.S. Treasury OFAC SDN list. Information, not a compliance determination.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.