scamgate
Related Servers
Alternatives to scamgate
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and apps to check URLs, domains, IP addresses, phone numbers, emails, crypto wallets, IBANs, mobile apps, and payment handles for scam, phishing, and fraud risk, returning verdicts, probabilities, facts, and reason codes.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to run pre-sign risk checks on transactions, approvals, EIP-712 signatures, token addresses, wallet approvals, sanctions screening, and prompt-injection texts, returning green/orange/red verdicts with machine-readable reason codes before signing.1AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check trustworthiness before recommending URLs, products, or organizations, with fail-closed pass/fail verdicts and attested-only recommendations.MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to perform pay-per-call security verification of wallets, tokens, contracts, dApps, agents, and more via a remote endpoint with no installation.2MIT
- AlicenseNot gradedqualityDmaintenanceSecurity layer for AI agents that evaluates transaction intents and returns verdicts (ALLOW/WARN/DENY) using deterministic rules, on-chain checks, and simulation.15 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to perform token security audits, honeypot detection, liquidity analysis, and risk scoring to avoid crypto scams.1ISC
TDQS
Scored across 3 tools
Each tool targets a distinct object and action: verifying a URL, verifying a payment, and refreshing phishing feeds. An agent can never confuse check_url with check_payment, and update_feeds is clearly a maintenance operation gated on stale/missing list status.
All three names follow the same verb_noun snake_case pattern (check_url, check_payment, update_feeds). The shared check_ prefix for the two verdict tools even reinforces the shared output contract.
Three tools is a narrow but coherent surface for a scam-verdict service, and each one earns its place with no filler. It sits at the low edge of the comfortable range, leaving little room for additional check types.
The core lifecycle is covered: verdicts for links and payments plus a way to remediate stale feed data, with consistent allow/ask/deny semantics. Gaps exist for other scam vectors (email senders, phone numbers, domains, QR/app downloads), which agents would have to handle elsewhere.