com.edgethirteen.www/sanctions
REMOTE · WWW.EDGETHIRTEEN.COM · SCANNED SEP 24
Screen a name against OFAC's SDN and Consolidated Sanctions lists before a transaction.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the com.edgethirteen.www/sanctions MCP server?
com.edgethirteen.www/sanctions is a hosted endpoint at https://www.edgethirteen.com/api/mcp/sanctions, 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 · www.edgethirteen.com
claude mcp add --transport http com-edgethirteen-www-sanctions 'https://www.edgethirteen.com/api/mcp/sanctions'
{
"mcpServers": {
"com-edgethirteen-www-sanctions": {
"url": "https://www.edgethirteen.com/api/mcp/sanctions"
}
}
} {
"servers": {
"com-edgethirteen-www-sanctions": {
"type": "http",
"url": "https://www.edgethirteen.com/api/mcp/sanctions"
}
}
} [mcp_servers.com-edgethirteen-www-sanctions] url = "https://www.edgethirteen.com/api/mcp/sanctions"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-edgethirteen-www-sanctions": {
"type": "remote",
"url": "https://www.edgethirteen.com/api/mcp/sanctions",
"enabled": true
}
}
} openclaw mcp add com-edgethirteen-www-sanctions --url 'https://www.edgethirteen.com/api/mcp/sanctions' --transport streamable-http
mcp_servers:
com-edgethirteen-www-sanctions:
url: "https://www.edgethirteen.com/api/mcp/sanctions" {
"McpServers": {
"com-edgethirteen-www-sanctions": {
"Transport": "http",
"Url": "https://www.edgethirteen.com/api/mcp/sanctions"
}
}
} assistant mcp add com-edgethirteen-www-sanctions -t streamable-http -u 'https://www.edgethirteen.com/api/mcp/sanctions'
{
"mcpServers": {
"com-edgethirteen-www-sanctions": {
"type": "http",
"url": "https://www.edgethirteen.com/api/mcp/sanctions"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 23 Sept 26 −50
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 74
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 24 Sept 2026 · Probed https://www.edgethirteen.com/api/mcp/sanctions
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.edgethirteen.com | CN=YR1,O=Let's Encrypt,C=US | 24 Aug 2026 | 22 Nov 2026 | RSA 2048 | SHA256-RSA | 6839f6f39d66a38fe8deece9986a25a4546 |
| SANs: www.edgethirteen.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.edgethirteen.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| edgethirteen.com. | absent | 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 | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.edgethirteen.com/api/mcp/sanctions | HTTP error | 404 | |
| http (plaintext) | http://www.edgethirteen.com/api/mcp/sanctions | HTTPS enforced | 308 | https://www.edgethirteen.com/api/mcp/sanctions |
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 →
get_sanctionrail_info ~72
Get details and pricing for SanctionRail: fuzzy-match name screening against the US Treasury OFAC Specially Designated Nationals (SDN) list and Consolidated Sanctions List, for an agent that needs to check a counterparty before completing a transaction, onboarding a vendor, or approving a payment.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_name ~133
Screen a person or company name against OFAC's SDN and Consolidated Sanctions lists (19,874 entities, 21,320 aliases). Returns fuzzy matches banded exact/strong/probable/weak, with the sanctions programme, source list, and a common-name-collision flag so a common name like 'Maria Garcia' is surfaced, not silently suppressed. Free tier: 25 lookups/day per caller IP, no key required. Handles aliases, transliteration, and legal-form variants (JSC / S.A. / GmbH).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Person or company name to screen. |
No output schema declared.
No examples provided.
What is the com.edgethirteen.www/sanctions MCP server?
com.edgethirteen.www/sanctions is an MCP server listed in the public MCP registry as com.edgethirteen.www/sanctions. Screen a name against OFAC's SDN and Consolidated Sanctions lists before a transaction. This page covers its hosted endpoint (https://www.edgethirteen.com/api/mcp/sanctions).
Is the com.edgethirteen.www/sanctions MCP server safe to use?
com.edgethirteen.www/sanctions scores 25 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 com.edgethirteen.www/sanctions MCP server expose?
com.edgethirteen.www/sanctions exposes 2 tools: get_sanctionrail_info, screen_name. Their descriptions and schemas cost roughly 205 tokens of context every time the server is loaded.
Does the com.edgethirteen.www/sanctions MCP server require authentication?
No. We connected to com.edgethirteen.www/sanctions without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.edgethirteen.www/sanctions MCP server still maintained?
com.edgethirteen.www/sanctions is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.