io.github.krunalsolanki/ofac-match
NUGET · OFACMATCH.MCP
Explainable OFAC sanctions name screening against the SDN list. Runs locally, no API key.
Available components
Last scanned (9 hours ago)
Scores higher than 47% of NuGet servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 531 tokens (~106/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +15
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.2 → 2.0.0 functional
- 3 Nov 26 57
First indexed and scored.
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 4 Nov 2026 · Analysed nuget/OfacMatch.Mcp@2.0.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | nuget |
| Reason | Signature present, unverified |
Signer
| Signed as | Repository signature, names nuget.org |
|---|---|
| Subject | CN=NuGet.org Repository by Microsoft,O=NuGet.org Repository by Microsoft,L=Redmond,ST=Washington,C=US |
| Issuer | CN=DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1,O=DigiCert\, Inc.,C=US |
| Valid from | 23 Feb 2024 |
| Valid until | 18 May 2027 |
| Service index | https://api.nuget.org/v3/index.json |
| Owners | KrunalSolanki |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
Registry declarations For information only
What the registry and the package's own manifest say about this version. The publisher or the registry writes these, nothing here is verified, and none of it affects the score.
| Repository | https://github.com/krunalsolanki/ofac-match |
|---|---|
| Repository type | git |
| Commit | 7a8c1e3d5552e6bced632c9af8aa56e7f61faf0c |
| Project URL | https://github.com/krunalsolanki/ofac-match |
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 →
compare_names Explain how two names score ~102
Scores two names against each other with the same method used for screening, and shows the whole-name score, the name-parts score and how each part paired. Useful to understand or explain a score.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | boolean | – | Treat the names as company names, ignoring legal forms such as LLC or LTD. |
| name | string | yes | The searched name. |
| otherName | string | yes | The name to compare with, e.g. a listed name or alias. |
No output schema declared.
No examples provided.
get_list_info SDN list status ~38
Reports which copy of the OFAC SDN list the server is using: number of entries, where it came from and when it was downloaded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sanctions_entry Look up an SDN entry ~73
Returns the full published record of one OFAC SDN entry by its entry number: names, aliases, type, programs, dates of birth, addresses and remarks. Use it to review a potential match.
| Name | Type | Req | Description |
|---|---|---|---|
| entryId | integer | yes | The SDN entry number (ent_num) shown in screening results. |
No output schema declared.
No examples provided.
screen_name Screen a name against the OFAC SDN list ~227
Screens one person, company, vessel or aircraft name against the U.S. Treasury OFAC SDN sanctions list and returns potential matches with scores (0-100, 100 = identical) and an explanation of each. Give year of birth and country when known so conflicts can be flagged.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string|null | – | The party's country, if known. Matches whose listed addresses are all in other countries are flagged. |
| maxResults | integer | – | Maximum number of matches to return, 1-50. Default 10. |
| minScore | number | – | Lowest score to return, 0-100. Default 85. |
| name | string | yes | The name to screen, in any order, e.g. "John Doe" or "DOE, John". |
| type | string|null | – | Only screen this kind of entry: individual, entity, vessel or aircraft. Omit to screen all. |
| yearOfBirth | integer|null | – | The party's year of birth, if known. Matches whose listed dates of birth differ by more than a year are flagged. |
No output schema declared.
No examples provided.
screen_names Screen several names ~91
Screens up to 100 names against the OFAC SDN list and returns, for each, the number of potential matches and the best one. Use screen_name for full details on any name that has matches.
| Name | Type | Req | Description |
|---|---|---|---|
| minScore | number | – | Lowest score to count as a potential match, 0-100. Default 85. |
| names | array | yes | The names to screen (at most 100). |
No output schema declared.
No examples provided.
How do I install the io.github.krunalsolanki/ofac-match MCP server?
io.github.krunalsolanki/ofac-match runs locally as a NuGet package, launched with dnx OfacMatch.Mcp@2.0.0 --yes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
nuget · OfacMatch.Mcp
claude mcp add krunalsolanki-ofac-match -- dnx OfacMatch.Mcp@2.0.0 --yes
What is the io.github.krunalsolanki/ofac-match MCP server?
io.github.krunalsolanki/ofac-match is an MCP server listed in the public MCP registry as io.github.krunalsolanki/ofac-match. Explainable OFAC sanctions name screening against the SDN list. Runs locally, no API key. This page covers its NuGet package (OfacMatch.Mcp).
Is the io.github.krunalsolanki/ofac-match MCP server safe to use?
io.github.krunalsolanki/ofac-match scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.krunalsolanki/ofac-match MCP server expose?
io.github.krunalsolanki/ofac-match exposes 5 tools: screen_name, screen_names, get_sanctions_entry, compare_names, get_list_info. Their descriptions and schemas cost roughly 531 tokens of context every time the server is loaded.
Is the io.github.krunalsolanki/ofac-match MCP server still maintained?
io.github.krunalsolanki/ofac-match is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.krunalsolanki/ofac-match MCP server under?
io.github.krunalsolanki/ofac-match declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.