原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Trust Check MCP

✓ paladinfi.com

作者:paladinfi版本 0.1.0i★ 0i在云端运行官方网站 ↗
注册名称com.paladinfi/trust-check-mcp

安装方法

What it does

Free OFAC SDN wallet screen + sample preview for AI agents on Base. Read-only, no payment surface.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 网店与支付

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度3/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分3/100

质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 2/3 项检查 · 在你的电脑上运行

我们隐藏了部分命令

通过地址连接:检查时服务器地址没有响应

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Trust Check MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 Trust Check MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 网店与支付 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Trust Check MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 Trust Check MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 Trust Check MCP

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 Trust Check MCP 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ paladinfi.com
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
发布到注册中心i
2026年5月25日
代码最后更新i
2026年6月1日
最近检查
2026年11月15日
作者
paladinfi
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

我们上次检查时服务器没有响应,所以无法读取它的工具。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 paladinfi.com 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于6个月前

  • – 不适用

    有许可证

    不适用:由 paladinfi.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✕ 未通过

    端点有响应

    我们检查时,6 秒内没有响应

  • – 不适用

    使用 OAuth 登录

    我们检查时,6 秒内没有响应

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/paladinfi-trust-check-mcp.svg)](https://mcp.popnx.com/en/servers/paladinfi-trust-check-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“网店与支付”中的其他服务器比较i

  • 星标数多于此分类中其他 2932 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2932 个服务器的 7% 更新
  • 基础检查结果等于或优于此分类中其他 2932 个服务器的 59%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Trust Check MCP 安全吗?

它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于6个月前,最新版本(0.1.0)于6个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Stripe MCP

MCP server integrating with Stripe - tools for customers, products, payments, and more.

作者:stripe广泛使用★ 207213个月前更新

在云端运行✓ 服务方 · stripe.com

flightclaw

Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.

作者:flightclaw正在增长★ 862个月前更新

在云端运行✓ 服务方 · flightclaw.com

Trade It

Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.

作者:trade-it-inc起步阶段★ 6234天前更新

在云端运行✓ 服务方 · tradeit.app

idealo MCP Server

Search products, compare prices and discover deals across 6 European markets with your AI assistant.

作者:idealo起步阶段★ 286个月前更新

在云端运行✓ 服务方 · mcp.idealo.com
与相似项目对比
本项
Trust Check MCP
Stripe MCPflightclawTrade ItMarketplace Ad Pros: Amazon Ads & Seller Centralidealo MCP Server
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否是否否否否
基础检查2/34/44/45/54/44/4
许可证MITMITMITCC0-1.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

trust-check-mcp

Open client and API spec for [PaladinFi Trust Check](https://paladinfi.com/trust-check/) — free wallet-OFAC SDN screening and sample-fixture trust-check preview for AI agents on Base. This repository contains the public REST and MCP API specification, working code examples, and thin client wrappers. The hosted backend is proprietary.

Operated by Malcontent Games LLC, doing business as PaladinFi.


What is PaladinFi Trust Check?

A free wallet-OFAC-SDN screening surface for AI agents on Base. Single MCP tool call returns a binary allow / block verdict against the US Treasury OFAC SDN list.

  • No auth surface. No API key, no signup, no billing.
  • Live US Treasury OFAC SDN data. Refreshed daily from the Treasury XML feed.
  • Freshness metadata per response. _ofac_list_updated_at (ISO timestamp) and _ofac_sdn_count exposed in every response (inside the trust block); callers can verify staleness without trusting our bookkeeping.
  • Signed responses. Every /ofac response carries an Ed25519 signature (_signature, _signature_alg, _signature_pubkey_hex) over the canonical JSON body, so a consumer can verify origin integrity.
  • Rate limit. 1 request per second per IP + burst 3 + 3 concurrent connections per IP.
  • Non-custodial, read-only. No money handling, no calldata, no signing surface, no transaction execution.

This MCP is the off-chain HTTP surface for sanctions screening. For in-contract gate logic (Solidity modifiers running inside settlement contracts), on-chain sanctions oracles remain the canonical surface.

Install (MCP)

For Claude Code or any MCP-compatible client supporting Streamable-HTTP transport:

claude mcp add --transport http --scope user paladin-trust https://trust.paladinfi.com/mcp

Verify the host is up before adding:

curl -i https://trust.paladinfi.com/health

Expect: HTTP/1.1 200 OK

After mcp add, restart your client. Three tools become available:

  • trust_check_ofac_free(address, chainId?) — live US Treasury OFAC SDN wallet-screen. Returns recommendation: "allow" | "block" with _real: true plus freshness metadata.
  • trust_check_preview(address, chainId?) — sample-fixture preview of the broader trust-check response shape. The trust block carries _preview: true, every factor is real: false, and recommendation is prefixed sample-. Do not use the preview verdict to gate real swaps, signing, or any production agent decision.
  • trust_check_health() — liveness, supported chains, OFAC list refresh timestamp + size.

See mcp-tools.json for the full tool schemas.

REST API

The MCP server fronts three REST endpoints. The backend is hosted alongside other PaladinFi services on a shared origin (swap.paladinfi.com); this MCP is scoped to read-only OFAC screening and does not expose calldata, signing, or transaction surfaces from the broader platform. The REST endpoints can be called directly via curl:

# Free OFAC SDN screen

curl -X POST https://swap.paladinfi.com/v1/trust-check/ofac \ -H "content-type: application/json" \ -d '{"chainId": 8453, "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

Sample-fixture preview

curl -X POST https://swap.paladinfi.com/v1/trust-check/preview \ -H "content-type: application/json" \ -d '{"chainId": 8453, "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'

See openapi.yaml for the full schemas.

`chainId` note: the OFAC SDN screen is wallet-address-level and chain-agnostic — the same 0x address is listed (or not) regardless of network. chainId is accepted for consistency with the full /v1/trust-check endpoint; it does not scope the OFAC match.

Coverage and limits

DimensionValue
ChainBase mainnet (chainId 8453)
SourceUS Treasury OFAC SDN XML feed
JurisdictionUS OFAC SDN only. No EU, UN, UK, or other sanctions regimes; callers in non-US jurisdictions are responsible for screening against locally-applicable lists.
Refresh cadenceDaily from the Treasury XML feed
List size~93 wallet/EOA addresses (see live _ofac_sdn_count)
Rate limit1 req/sec + burst 3 + 3 concurrent per IP
AuthAnonymous (no API key, no signup)
CostFree

Response shape

trust_check_ofac_free

The freshness + scope markers live inside the `trust` block. The top level also carries an Ed25519 signature and a pointer to the paid full-composition endpoint.

{

"address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913", "chainId": 8453, "trust": { "recommendation": "allow", "factors": [ { "source": "ofac", "signal": "not_listed", "weight": 0, "details": "", "real": true } ], "version": "1.1", "_real": true, "_scope": "ofac-only (wallet-address screen; use /v1/trust-check for full composition: GoPlus + Etherscan + anomaly heuristics)", "_ofac_list_updated_at": "2026-05-31T04:08:06Z", "_ofac_sdn_count": 93 }, "_signature": " ", "_signature_alg": "ed25519", "_signature_pubkey_hex": "272b6b62230d9da810f3ed64b5e5147f1ae062cb46ad7f25044b0aab1d18fb6f" }

A sanctioned address returns the same shape with trust.recommendation: "block" and a factor { "source": "ofac", "signal": "sdn_listed" }.

Programmatic safety check before consuming the verdict:

resp = httpx.post("https://swap.paladinfi.com/v1/trust-check/ofac",

json={"chainId": 8453, "address": addr}).json() trust = resp["trust"] assert trust["_real"] is True # not a fixture assert trust["_scope"].startswith("ofac-only") # not a different evaluation path verdict = trust["recommendation"] # "allow" or "block"

trust_check_preview

A SAMPLE FIXTURE — not a live evaluation. Same envelope (address, chainId, trust, plus top-level request_id and _mcp_paid_endpoint_info), but inside trust: _preview: true, recommendation is prefixed sample- (e.g. "sample-allow"), risk_score is null, every factor is real: false, and trust._message carries a do-not-use-as-real-verdict banner. There is no _real field on preview — the _preview: true marker and the sample- prefix are how you tell a fixture from a real screen.

Refresh cadence

The OFAC SDN list is fetched from https://www.treasury.gov/ofac/downloads/sdn.xml daily. The exact timestamp of the in-memory list is returned per-response in trust._ofac_list_updated_at, so callers can detect stale data without trusting a separate bookkeeping layer.

If the source feed is unreachable, the in-memory list is held over and _ofac_list_updated_at continues to reflect the last successful refresh. Stale lists do not auto-degrade to block — callers responsible for enforcing maximum-acceptable staleness check _ofac_list_updated_at themselves.

Logging and retention

The server records request timestamp, source IP (for rate-limit accounting only), and the queried address in standard nginx access logs. Logs are retained for 30 days for operational debugging and then rotated. No persistent association is built between caller identity and queried addresses beyond the rate-limit window. No analytics, no third-party tracking, no PII enrichment.

Rate-limit behavior

Requests exceeding 1 r/s + burst 3 receive HTTP 429. The rate-limit window is per-IP; there is no IP ban or escalating block — the next request after the window clears is served normally. The Retry-After header indicates when to retry.

Use of this endpoint is subject to the PaladinFi Terms.

Related packages

For evaluations that compose multiple signals (OFAC + GoPlus token security + Etherscan source verification + anomaly heuristics), PaladinFi offers other npm packages — see paladinfi.com/trust-check for details. Migration from this MCP to one of the multi-signal packages: install the chosen npm package alongside (or instead of) this MCP; tool names overlap so callers can migrate without rewriting call sites.

When to use this vs. an on-chain sanctions oracle

On-chain oracletrust_check_ofac_free
AccessSolidity call on a settlement contractHTTP POST (anonymous)
Best forIn-contract gate logic (modifiers)Off-chain agents, bots, web apps, MCP clients
ResponseBare boolStructured JSON with freshness metadata
CostGas per callFree + rate-limited
CoverageOften multi-jurisdictionUS OFAC SDN only

These are complementary surfaces: an off-chain HTTP screen for agent / web-UI display, and an on-chain modifier for the settlement contract.

Examples

Zero-dependency, copy-paste runnable. Each defaults to screening one clean address and one genuinely OFAC-listed address, so you see both an allow and a block on first run. Pass your own addresses as arguments. Exit code: 0 all clean, 1 any address listed, 2 request error — drops straight into CI or a pre-send gate.

For a browser/React integration of the same endpoint, see the tutorial at paladinfi.com/docs/screen-wallets/.

Documentation

Contact

Legal

Operated by Malcontent Games LLC, doing business as PaladinFi. The hosted backend at swap.paladinfi.com and the MCP server at trust.paladinfi.com are proprietary; this repository covers the client-facing spec and examples under MIT.