trustsource-mcp
MCP server exposing the TrustSource suite of x402-paid domain verification APIs to any MCP-compatible client (Claude Desktop, Claude Code, Cline, Continue, etc.).
Four tools, each settled per-call in USDC on Base Mainnet. No API keys, no signups, no accounts — just a wallet.
These tools are also discoverable to autonomous agents via Coinbase's Bazaar marketplace, where AI agents browse, pay for, and call x402-enabled services.
Tools
trustsource_score | $0.003 USDC | Domain trust score 0–100 (WHOIS age, TLD, DNS, registrar) |
trustsource_ssl | $0.002 USDC | TLS certificate intelligence (chain, expiry, CA trust, TLS version) |
trustsource_headers | $0.003 USDC | HTTP security header audit (A+ to F grade) |
trustsource_robots | $0.002 USDC | robots.txt + AI bot policy across 24 known crawlers |
Install
npm install -g trustsource-mcp
Or run without installing:
npx -y trustsource-mcp
Configure
The server needs a Base Mainnet wallet private key. The wallet must hold:
USDC for per-call fees ($0.002–$0.003 per call)
ETH for gas (minimal — Base Mainnet gas is fractions of a cent per call)
Suggested starter balance: $1 USDC + 0.0005 ETH on Base Mainnet covers ~300 calls. Bridge via bridge.base.org or buy directly to a Base wallet via Coinbase.
Set the private key in your MCP client's environment, not in any committed file.
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"trustsource": {
"command": "npx",
"args": ["-y", "trustsource-mcp"],
"env": {
"WALLET_PRIVATE_KEY": "0xYOUR_BASE_MAINNET_PRIVATE_KEY"
}
}
}
}
Restart Claude Desktop. The four tools appear automatically.
Cline / Continue / other MCP clients
Add to your client's MCP server configuration:
{
"trustsource": {
"command": "npx",
"args": ["-y", "trustsource-mcp"],
"env": {
"WALLET_PRIVATE_KEY": "0x..."
}
}
}
Environment variables
WALLET_PRIVATE_KEY | yes | — | Base Mainnet wallet private key with USDC + ETH for gas |
TRUSTSOURCE_API_URL | no | https://api.trustsource.cc | Override the API base URL (useful for testing) |
How it works
- The MCP client calls a tool (e.g.
trustsource_score).
- This server makes an HTTP request to the corresponding TrustSource endpoint.
- The API returns HTTP 402 with a
PAYMENT-REQUIRED header.
x402-fetch signs an EIP-3009 USDC transferWithAuthorization for the exact amount.
- The request is retried with the signed payment in
X-PAYMENT.
- The Coinbase Developer Platform facilitator settles on-chain.
- The API returns the JSON response. The MCP client receives the result.
Total latency per call: typically 1–3 seconds including settlement.
Cost discipline
If your agent is making many calls, deduplicate by domain client-side before invoking tools. The API caches responses (1 hour for /trustscore and /sslcheck, up to 12 hours for /robots and /headers), but the cache reduces latency, not price — every call costs the same regardless of whether it hits cache.
Worst-case full domain audit: trustsource_score + trustsource_ssl + trustsource_headers + trustsource_robots = $0.010 USDC.
Build from source
git clone https://github.com/SurfEther/TrustSourceX402.git
cd TrustSourceX402/mcp-server
npm install
npm run build
npm start
Links
License
MIT