Trust Score API MCP Server

Use this when you need to compare the trustworthiness of multiple domains, URLs, or wallets and pick the safest option. Accepts 2-5 targets and returns trust scores for all, sorted from most to least trusted. Returns: { mostTrusted: "...", leastTrusted: "...", results: [{ compositeScore, grade, verdict, subscores }] } Use cases: - Comparing API providers before choosing one - Verifying multiple domains from a search result - Ranking wallet addresses by on-chain reputation - Due diligence on a list of services Do NOT use for single targets -- use trust_score_evaluate instead (cheaper at $0.01 vs $0.02).

Use this when you need to check if a domain, website, API endpoint, or crypto wallet is safe to interact with. Returns a composite trust score 0-100 with letter grade (A+ to F), verdict (trusted/moderate/suspicious/dangerous), and 5 sub-scores: 1. SSL/TLS (25%): certificate validity, HSTS, expiry, issuer 2. DNS (15%): A/AAAA/MX/NS records, SPF, DMARC, DNSSEC 3. WHOIS (25%): domain age, registrar reputation, expiry, suspicious TLDs 4. Security Headers (20%): CSP, X-Frame-Options, HSTS, Referrer-Policy, Permissions-Policy 5. Content (15%): reachability, latency, status code, robots.txt, CORS For wallet addresses (0x...): returns on-chain trust based on transaction count, ETH/USDC balance, contract status on Base L2. Example output: { compositeScore: 82, grade: "A", verdict: "trusted", subscores: { ssl: { score: 90, ... }, dns: { score: 85, ... }, ... } } Use this BEFORE making payments, sending sensitive data, or trusting any external service. Essential for agent safety. Do NOT use for SEO analysis -- use seo_audit_page instead. Do NOT use for email validation -- use email_verify_address instead. Do NOT use for tech stack detection -- use website_detect_tech_stack instead. Do NOT use for port scanning -- use network_scan_ports instead.