com.paladinfi/trust-check-mcp
REMOTE · TRUST.PALADINFI.COM · SCANNED AUG 3
Free OFAC SDN wallet screen + sample preview for AI agents on Base. Read-only, no payment surface.
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 →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 799 tokens (~266/item across 3 items; 3 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 Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · trust.paladinfi.com
claude mcp add --transport http com-paladinfi-trust-check-mcp https://trust.paladinfi.com/mcp
[mcp_servers.com-paladinfi-trust-check-mcp] url = "https://trust.paladinfi.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-paladinfi-trust-check-mcp": {
"type": "remote",
"url": "https://trust.paladinfi.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-paladinfi-trust-check-mcp --url https://trust.paladinfi.com/mcp --transport streamable-http
mcp_servers:
com-paladinfi-trust-check-mcp:
url: "https://trust.paladinfi.com/mcp" {
"mcpServers": {
"com-paladinfi-trust-check-mcp": {
"type": "http",
"url": "https://trust.paladinfi.com/mcp"
}
}
} 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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
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 3 Aug 2026 · Probed https://trust.paladinfi.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=trust.paladinfi.com | CN=YE2,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6b95857c3de9eae533e97e1d4b02f91f490 |
| SANs: trust.paladinfi.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 |
DNSSEC insecure
Validation of trust.paladinfi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| paladinfi.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 | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trust.paladinfi.com/mcp | Verified | 200 | |
| http (plaintext) | http://trust.paladinfi.com/mcp | HTTPS enforced | 301 | https://trust.paladinfi.com/mcp |
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.
trust_check_health Trust Check Service Health ~82
Return service health, supported chains, OFAC list refresh timestamp + size. Pure introspection — no external API calls, no money handling. Returns: dict with `status`, `supportedChains`, `version`, and (when the OFAC list is loaded) an `ofac_list` block with `updated_at` + `sdn_count`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
trust_check_ofac_free Wallet OFAC SDN Screen (Free, Real Data) ~233
Free wallet-address OFAC SDN screen on Base. Live US Treasury OFAC SDN list lookup. Anonymous (no API key, no signup). Rate-limited at 1 request per second + burst 3 + 3 concurrent per IP. Refreshed daily from the Treasury XML feed. Scope: US OFAC SDN wallet/EOA addresses only (~93 entries at last refresh). Returns a binary `allow` / `block` verdict — no `warn` state on this endpoint. No token-contract risk evaluation, no GoPlus signals, no Etherscan verification, no anomaly heuristics — those are paid-endpoint features not exposed through this MCP. No money handling. No calldata. No signing surface. No transaction execution. Pure information retrieval.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet/EOA address to screen (0x-prefixed 40 hex chars; must match `^0x[a-fA-F0-9]{40}$`) |
| chainId | integer | — | EVM chain ID (default 8453 = Base; only chain supported) |
Structured output declared, but exposes no named fields.
No examples provided.
trust_check_preview Token Trust Check (Preview) ~304
Get a SAMPLE-FIXTURE preview of the PaladinFi token-contract trust check. ⚠️ NOT a real evaluation. Returns fixed sample data with `_preview: true`, every factor marked `real: false`, and recommendation prefixed `sample-` (`sample-allow` / `sample-warn` / `sample-block`). Use this for shape-testing your integration; DO NOT use the verdict to gate real swaps, signing, or any production agent decision. **Programmatic safety check**: before consuming any field of this response, agents should test `resp.get("_real") is True` (top-level) — preview always returns `_real: false`. Substring-matching on `recommendation` (e.g. `"allow" in resp["trust"]["recommendation"]`) will INCORRECTLY match `sample-allow`; use exact-equality (`resp["trust"]["recommendation"] == "allow"`) or test the `_real` field instead. For free real-data wallet-OFAC screening (binary allow/block, anonymous, no payment), use `trust_check_ofac_free` from this same MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | ERC20 contract address to evaluate (Base 8453 only currently; must match `^0x[a-fA-F0-9]{40}$`) |
| chainId | integer | — | EVM chain ID (default 8453 = Base; only chain supported) |
Structured output declared, but exposes no named fields.
No examples provided.