Claro Antifraud (Open Gateway)

Claro Antifraud (Open Gateway) MCP Connector for Claude

A+

Line & location security checks on the official Claro Brasil gateway: SIM swap check and last-swap date (GSMA), line-change alerts (Claro Alerta), number recycling, device location verify/retrieval and legacy LBS — OAuth client_credentials.

7 tools Official Updated Oct 1, 2026 Official Vinkius Partner

Line security and device location checks on the official Claro Brasil API gateway (Claro Insight / GSMA Open Gateway) — everything an antifraud or risk agent needs to trust (or block) a mobile line.

What you can do

  • SIM swap check — has the SIM been swapped within the last N hours (up to 2400)? The classic account-takeover signal before password resets and high-value transactions
  • SIM swap date — the exact timestamp of the last SIM change, for forensics and case review
  • Claro Alerta — line-change alerts: SIM-chip swap, device change, MSISDN change, subscription cancel
  • Number recycling — was the number assigned to a new owner since a given date? Validates stale customer databases
  • Device Location Verify — is the device inside a lat/long circle (2-200 km)? returns verificationResult true/false (LGPD consent required)
  • Device Location Retrieval — the device's last known location: circular area + timestamp
  • LBS Device Location — cell-level last position from the legacy LBS platform (coordinates, accuracy radius, validation time)

Authentication

  1. Register an app in the Claro Insight marketplace (www.claro.com.br) to get a Client ID + Client Secret and your Customer ID (trials with 1.000 requests per API)
  2. The MCP mints a token at POST https://api.claro.com.br/oauth2/v1/token (grant_type=client_credentials) and refreshes it automatically
  3. Every call carries your marketplace Customer ID as the X-CustomerID header

Who is this for?

Antifraud and risk agents, fintech onboarding flows, account-takeover detection, database hygiene and delivery/asset validation — anyone securing actions behind the trustworthiness of a phone line.

clarosim-swapaccount-takeoverantifrauddevice-locationnumber-recyclinggsmabrazil

7 tools expose this connector's capabilities to your AI agent.

get_lbs_device_location

Coarsest and cheapest of the location checks — use for asset/fleet monitoring and region-level checks. location_type "LAST" gives the most recent reading. The LBS service enforces a per-MSISDN rate ceiling: a 429 means you polled that number too often — back off rather than retry immediately. network_msisdn = country code + number, digits only ("5521912345678"). User consent applies under LGPD. Get the last known cell-level location of a Claro device via the legacy LBS platform — coordinates, area type and accuracy radius

retrieve_device_location

Use when you need where the device was (nearest-city level trust, asset tracking checks) rather than a yes/no inside-test. max_age_seconds limits how fresh the reading must be (e.g. "600" = only data up to 10 minutes old; omit for the freshest available). The device must be on the Claro mobile data network, and user consent is mandatory under LGPD — tell the user consent is required. phone_number in E.164, leading + optional. Get the last known location of a device on the Claro network (GSMA Device Location retrieval) — area and timestamp

get_sim_swap_date

Use when you need the exact moment rather than a yes/no — forensics, fraud case review, or deciding how stale a SIM-based authentication is. phone_number in E.164, leading + optional ("+5511999999999" or "5511999999999"). A response with no change date means no swap was recorded for the line. Get the timestamp of the last SIM card change on a Claro phone number (GSMA SIM Swap retrieve-date)

get_line_change_alerts

The strongest antifraud pattern: a SIM change right before a password reset or high-value transaction is classic account takeover. event_types defaults to "SIMCARD_CHANGED,DEVICE_CHANGED"; add MSISDN_CHANGED and SUBSCRIPTION_CANCELED when reviewing onboarding or fraud cases. Requires the optional credential CLARO_CUSTOMER_ID. network_msisdn = country code + number, digits only ("5521987654321"). Check recent operational changes on a Claro mobile line: SIM-chip swap, device change, number change, subscription cancel — the core account-takeover antifraud signal

check_number_recycling

Use to validate stale databases: a number that was recycled means your stored customer data no longer belongs to that line, so registrations, contacts and marketing lists built on it are pointing at a stranger. specified_date = ISO 8601 date-time (e.g. "2025-01-01T00:00:00Z"); phone_number in E.164, leading + optional. Combine with get_sim_tenure for a full picture of the line's ownership stability. Check whether a phone number was recycled (assigned to a new owner) since a given date (GSMA Number Recycling)

verify_device_location

Use for fraud checks (falsified GPS), delivery validation and geofence spot-checks. accuracy_km between 2 and 200 (bigger = more forgiving). The check only works while the phone is connected to the Claro mobile data network, and user consent is mandatory under LGPD — tell the user consent is required before running it. phone_number may be sent with or without the leading "+" ("+5511974129777" or "+5511974129777"). To get the actual coordinates instead of a yes/no, use retrieve_device_location. Verify whether a device is physically inside a given area (lat/long circle, 2-200 km radius) — returns verificationResult true/false

check_sim_swap

Use before password resets, high-value transactions and session elevation: a recent SIM swap is the classic account-takeover signal. max_age_hours = how far back to look, 1 to 2400 hours, default 240 (10 days); shorter windows are stricter. phone_number in E.164, leading + optional ("+5511999999999" or "5511999999999"). To get the exact timestamp of the last swap instead, use get_sim_swap_date. Check whether a Claro phone number had its SIM card swapped recently — the core account-takeover antifraud check (GSMA SIM Swap)

See how to talk to your AI agent using Claro Antifraud (Open Gateway).

Has the SIM of +5511999999999 been swapped in the last 24 hours?

🚨 **SIM Swap check: +5511999999999** Queried with a 24-hour window: the response carries `swapped` — true means the chip changed hands right in the danger zone for account takeover. Before allowing the password reset, also pull the exact swap timestamp with get_sim_swap_date for the case record. Want me to?

Was the number 5521912345678 recycled since January 2025?

♻️ **Number Recycling: 5521912345678** Checked ownership since 2025-01-01: the response carries `recycled`. If true, any customer data you hold for that number now belongs to a stranger — registrations, contacts and marketing lists pointing at it need re-validation. I can run get_sim_tenure on the same line to see how long the (possibly new) owner has been active. Want that?

Is the device of 5511974129777 within 5 km of -23.627, -46.655?

📍 **Device Location: 5511974129777** Circle centred on -23.627, -46.655 with a 5 km radius: the response carries `verificationResult` true/false. Remember this check needs the phone on the Claro mobile data network and the user's LGPD consent. Need the actual coordinates instead of a yes/no? I can pull the last known area with retrieve_device_location.

Register at www.claro.com.br (Marketplace API Claro) and subscribe to the APIs you need — most offer a free trial with 1.000 requests for 3 months. The marketplace issues a Client ID, Client Secret and your Customer ID. This MCP exchanges them at POST https://api.claro.com.br/oauth2/v1/token (grant_type=client_credentials) for a bearer token (24h TTL) that it refreshes automatically; the Customer ID rides along as the X-CustomerID header on every call.

Related Connectors