trust-check-mcp
Server Details
Free OFAC SDN wallet screen + sample preview for AI agents on Base. Read-only, no payment surface.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- paladinfi/trust-check-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
3 toolstrust_check_healthTrust Check Service HealthRead-onlyInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
trust_check_ofac_freeWallet OFAC SDN Screen (Free, Real Data)Read-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| address | Yes | Wallet/EOA address to screen (0x-prefixed 40 hex chars; must match `^0x[a-fA-F0-9]{40}$`) | |
| chainId | No | EVM chain ID (default 8453 = Base; only chain supported) |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
trust_check_previewToken Trust Check (Preview)Read-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| address | Yes | ERC20 contract address to evaluate (Base 8453 only currently; must match `^0x[a-fA-F0-9]{40}$`) | |
| chainId | No | EVM chain ID (default 8453 = Base; only chain supported) |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!