LayerCall
Score IP addresses, emails, phones and devices for fraud risk with detailed signals.
Detects fraudulent signups and transactions by analyzing IP geolocation and VPN use, email validity and age, phone number validation, domain reputation, browser fingerprints and device history. Returns risk scores and allow/review/block verdicts to help Muse protect accounts and payments.
Try asking Muse: "Check if this email and IP look suspicious before I complete a purchase."
Source: Found in the official MCP Registry (com.layercall/trust-api) · First listed September 24, 2026
Last 24 hours
Each bar is one check, every 15 minutes. Green means it answered. Last checked 51 min ago.
Is it safe to connect?
What Muse can see: You sign in to your own account with it, so Muse can reach what that account allows. Read what it asks for before you agree.
Before it acts: Read what Muse plans to do before you approve it, and remove the app from Muse when you stop using it.
Sensitive: this app deals with your money. Only connect it if you are comfortable with Muse reading that information.
musedirectory.ai is not part of Meta. More about how Muse handles your information
How to add it to Muse
Not in Muse's Connectors list yet, but Muse can still use it. Copy the request below and paste it into Muse. Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
https://www.layercall.com/api/mcpNot in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
Technical details: safety screening, tools, response time and recent checks
Response time at the last check: 1104ms. Worked in 100% of checks over 30 days.
Screening · September 24, 2026
Screened, no issues found
Screening looks for known threats and hidden instructions at the time of the check, and runs again weekly and whenever the tool list changes. It cannot see the server's code, so only connect what you need and review what Muse asks to do. How screening works.
Tools · 7
score_ipRisk-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.verify_emailCheck 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.lookup_phoneValidate 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.score_domainProfile 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'.score_deviceJudge 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, verify_agentCryptographically 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 nscore_userScore 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 thRecent checks
Link
https://www.layercall.com/api/mcpQuestions about LayerCall in Muse
How do I connect LayerCall to Muse?
Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use LayerCall to help me. It is a free service with an MCP server at https://www.layercall.com/api/mcp. It needs an API key from LayerCall; ask me to enter it through your secure credential prompt. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.
Is LayerCall working right now?
At the last check (September 28, 2026, 08:16 UTC) the endpoint was working, answering in 1104ms. Over the last 7 days it answered 100% of health checks. It is checked every 15 minutes.
Is LayerCall safe to connect to Muse?
It was screened on September 24, 2026 with the result "screened, no issues found". Screening checks the domain against threat feeds and reads the tools for hidden instructions and requests for passwords or card numbers. It cannot see the server's code, so grant only the access you need.
What can LayerCall do in Muse?
It exposes 7 tools, including score_ip, verify_email, lookup_phone, score_domain. For example, you could ask Muse: "Check if this email and IP look suspicious before I complete a purchase."
Follow LayerCall
Made this app? Claim it or get a status badge
Is this yours?
This listing was added from public sources (Found in the official MCP Registry (com.layercall/trust-api)). If you build LayerCall, claim it to correct the details and get your badge.
Paste this on your site or README. It always shows the latest check.
<a href="https://musedirectory.ai/connector/layercall"><img src="https://musedirectory.ai/badge/layercall.svg" alt="LayerCall on musedirectory.ai" width="236" height="40"></a>