A
licenseNot graded
qualityC
maintenanceEnables querying SEON fraud and digital-footprint data for email addresses, phone numbers, and IPs. Also provides aggregate fraud scoring with applied rules.
314 npm
MIT
LayerCall
Server Details
Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- Repository
- LayerCall/layercall-sdk
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
A4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool is anchored to a distinct input type: phone number, device fingerprint, domain, IP, aggregate user context, cryptographic agent signature, or email. The only mild conceptual overlap (domain checks inside verify_email) is clearly scoped by the intended resource, so an agent should not misselect.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case: lookup_, score_, verify_. Different verbs map to different intents and the nouns name exactly the resource each call evaluates, making behavior predictable.
Tool Count5/5
Seven tools is well-scoped for a fraud/risk intelligence surface: individual signals, one aggregate user call, and one proof-based verification. There is no bloat, and each tool appears necessary to cover the advertised workflows.
Completeness4/5
The set covers the major signup-risk signals: IP, email, phone, device, domain, and an aggregating user score, plus a cryptographic agent proof. Minor gaps such as inspecting past verdicts or device history are workarounds rather than hard blockers.
Available Tools
7 toolslookup_phoneValidate a phone numberAInspect
Validate a phone number worldwide against its national numbering plan. Returns E.164, country, line type (mobile/fixed/VoIP/toll-free/premium) and a risk score. Works globally, not US-only.
Inputs: phone (required), country, strictness.
score_deviceScore a device fingerprintAInspect
Judge a browser fingerprint from /fp.js: headless detection, automation frameworks (Selenium, Puppeteer, Playwright), timezone-versus-IP mismatch and repeat-device history. Note the ceiling honestly — the declared signals it relies on are the first thing stealth tooling patches, so a clean result is weaker evidence than a dirty one.
Inputs: device_id (required), ip.
score_domainScore a domainAInspect
Profile a domain: registration date from RDAP, registrar, MX/SPF/DMARC configuration, disposable-mail and risky-TLD detection. newly_registered is null when the age genuinely could not be determined — treat that as unknown, not as 'established'.
Inputs: domain (required).
score_ipScore an IP addressAInspect
Risk-score an IPv4 or IPv6 address. Detects commercial VPNs (naming the provider where its own published list confirms it), proxies, Tor exit nodes and datacenter hosting, and returns geolocation, ASN and a 0-100 risk score with an allow/review/block verdict.
Inputs: ip (required), strictness.
score_userScore a whole signupAInspect
Score an entire signup in one call — any combination of IP, email, phone and domain — returning a single weighted risk score, a verdict, and the top contributing signals. A hard block on any component is never averaged away. This is the tool to use when judging a person rather than a value. Costs one lookup PER COMPONENT supplied, not one per call, so four identifiers cost four; the response reports the exact figure as billable_lookups, and cached components are refunded.
Inputs: ip, email, phone, strictness, +1 more.
verify_agentVerify a signed AI agent (Web Bot Auth)AInspect
Cryptographically verify a Web Bot Auth signature (RFC 9421) — proof of WHICH agent is calling, not a guess from the user-agent. Returns verified true/false plus the agent's identity and declared purpose. This is the only check here that proves rather than infers, so it carries no score and no verdict: a verified assistant acting for a real user is usually welcome, a verified scraper usually is not, and that policy is the caller's. Pass the request the agent made to YOU — the signature covers its method, authority and path.
Inputs: url (required), headers (required), method.
verify_emailVerify an email addressAInspect
Check an email for syntax, MX records, disposable/throwaway providers, role accounts (info@, admin@), homograph lookalikes and domain age. Returns a 0-100 risk score and an allow/review/block verdict.
Inputs: email (required), strictness.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Fraud risk score for signups and orders from email, IP, phone and user-agent
Signup fraud checks: score emails and IPs, look up IPs and manage your blocklist.
Verify emails, validate phone numbers, look up carriers and score IP addresses.
IP geolocation, ASN and a 0-100 risk score (VPN, proxy, Tor, datacenter) for any IP address.
Related MCP 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 IP address lookups and risk assessments for IPv4/IPv6, providing geolocation, ISP/ASN, and security flags such as VPN, proxy, Tor, datacenter, and mobile with a risk score.132 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables phone number intelligence and spam-risk detection by combining metadata, FTC complaint history, and IPQS reputation into explainable risk scores with confidence levels.1-
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.