com.paladinfi/trust-check-mcp
REMOTE · TRUST.PALADINFI.COM
Free OFAC SDN wallet screen + sample preview for AI agents on Base. Read-only, no payment surface.
Available components
Last scanned (2 months ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 15 Aug 2026.
Category Security
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- 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 we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.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, or could read only part of the list.Unverified
Tool Safety–
Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 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.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool Safety in Tool SafetyNot scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 22 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 19 Aug 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Aug 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 15 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Aug 2026 · Probed https://trust.paladinfi.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trust.paladinfi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| paladinfi.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trust.paladinfi.com/mcp | Unreachable | ||
| http (plaintext) | http://trust.paladinfi.com/mcp | HTTPS enforced |
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 →
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.
How do I install the com.paladinfi/trust-check-mcp server?
com.paladinfi/trust-check-mcp is a hosted endpoint at https://trust.paladinfi.com/mcp, 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 · trust.paladinfi.com
claude mcp add --transport http com-paladinfi-trust-check-mcp 'https://trust.paladinfi.com/mcp'
What is the com.paladinfi/trust-check-mcp server?
com.paladinfi/trust-check-mcp is listed in the public MCP registry as com.paladinfi/trust-check-mcp. Free OFAC SDN wallet screen + sample preview for AI agents on Base. Read-only, no payment surface. This page covers its hosted endpoint (https://trust.paladinfi.com/mcp).
Is the com.paladinfi/trust-check-mcp server safe to use?
com.paladinfi/trust-check-mcp scores 0 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.paladinfi/trust-check-mcp server expose?
com.paladinfi/trust-check-mcp exposes 3 tools: trust_check_preview, trust_check_ofac_free, trust_check_health. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Does the com.paladinfi/trust-check-mcp server require authentication?
Its publisher declares no required credentials for com.paladinfi/trust-check-mcp. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the com.paladinfi/trust-check-mcp server still maintained?
com.paladinfi/trust-check-mcp has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 15 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.paladinfi/trust-check-mcp server?
VerifyMCP ran 3 checks on com.paladinfi/trust-check-mcp, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about com.paladinfi/trust-check-mcp: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.