MCP For Claude Marketplace
Serasa Experian Credit Monitoring

Serasa Experian Credit Monitoring MCP Connector for Claude

A+

Let AI agents watch CPFs and CNPJs for credit events — build monitoring rules, add documents, read alerts, and wire up webhooks.

14 tools Official Updated Oct 1, 2026 Official Vinkius Partner
More Details Connect to Claude

Connect your Serasa Experian account so any AI agent can run the full credit-monitoring lifecycle — using Serasa's official Monitoring API.

What you can do

  • Discover what to watch — the subject catalog lists every attribute a rule can monitor: negative annotations (pefin/refin, SPC), notary records, judgement filings, bankruptcy and shareholding participation, plus score families (HAT3, H4PJ, HPJM, H5RC, H5RA) with their allowed custom interval ranges
  • Create and manage rules — a rule binds a name, a document type (CPF/CNPJ), the variable ids and the alert emails; pause or reactivate without deleting
  • Manage the monitored portfolio — add or remove up to 1000 documents per batch and list every monitored document with its rules, inclusion dates and status
  • Read and triage alerts — alerts fire when a watched attribute changes; filter by document, rule name or read status, aggregate per document for portfolio triage, and mark them read
  • Follow operational notifications — system events for rule creation, document processing and exclusions, distinct from credit alerts
  • Push instead of poll — register webhooks (an AUTH endpoint plus one or more subject endpoints) and Serasa pushes the alerts to your system

How it works

The server authenticates with your Client ID / Client Secret, caches the Bearer token and re-authenticates transparently on expiry. Filters are rendered in the API's deep-object format automatically — pass plain values, not query strings.

serasaexperiancredit-monitoringmonitoraalertswebhooksbrazilcpfcnpjrisk-assessmentcollections

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

add_monitored_documents

`documents` is a JSON array or a comma list; non-digits are stripped. The response separates accepted from rejected documents with per-document error codes (e.g. MDC412 — already monitored). A 207 response means partial success and is still returned as a result, not an error. Add CPFs or CNPJs to an existing monitoring rule

create_monitoring_rule

Returns the rule `id`, which you pass to add_monitored_documents. `variables` is a JSON array of numeric ids or a comma list like "1,2,3". Score variables accept optional interval overrides via variables_config (JSON array of {"id","intervalMode":"CUSTOM","minValue","maxValue"}). To watch partners/shareholders, set rule type to CNPJ and pass partner variable ids in partners_variables. Create a monitoring rule that watches credit events for a list of CPFs or CNPJs

delete_webhook

Poll list_alerts afterwards to keep read visibility of the events. Delete a webhook by id, stopping alert delivery to its endpoints

list_alerts

Filter by document number (comma list accepted), viewed/deleted status, document type or the rule name. `unlink_document=true` includes alerts for documents already removed from monitoring. Use summarize_alerts for counts and mark_alerts_read to clear the queue. List credit-event alerts generated for the monitored documents

list_monitored_documents

Filter by document number, rule id or active status; date filters (included_at_start/included_at_end) are ISO 8601. The summary block reports how many monitoring links still have a future expiration date and the product types in play. List the documents currently monitored, with their rules, inclusion dates and status

list_monitoring_rules

Use the rule id with add_monitored_documents / remove_monitored_documents, and filter alerts by the rule name. Set active=false to list only inactive rules. List the monitoring rules already created in the organization

list_monitoring_subjects

Each subject exposes `variables` — the numeric ids you pass to create_monitoring_rule. Call this first to discover the variable ids for the document type you monitor. Score subjects also show the allowed custom interval range (valueMin–valueMax). List the monitoring subjects (attributes/variables) available for CPF, CNPJ or partners

list_notifications

Filter by subtype, type (INFO/WARNING/ERROR) or read status; created_at takes one or two ISO dates that form a range. List operational notifications about the monitoring itself — rule creation/activation, document processing and exclusions

list_webhooks

Use the id with delete_webhook. List the registered webhook endpoints for alert delivery

mark_alerts_read

Clearing the queue keeps list_alerts results available with viewed=true. Mark one or more alerts as read so they leave the unread queue

register_webhook

Pass them as a JSON array of {"type","endpoint"} objects. The credentials (clientId/clientSecret) authenticate the delivery, not this call. Register webhook endpoints so Serasa pushes alerts to your system instead of only polling

remove_monitored_documents

Documents removed here stop generating alerts for this rule but keep their alert history. The response mirrors the add format (accepted/rejected lists). Remove CPFs or CNPJs from a monitoring rule

summarize_alerts

Pairs well with a document_number filter for a single customer. Aggregate alerts by document — total counts and unread counts per monitored CPF/CNPJ

update_monitoring_rule

Omitted optional fields keep their current value on the Serasa side only when not sent. Pass active=false to pause a rule without deleting it — its documents stop being monitored. Rule id comes from list_monitoring_rules. Update a monitoring rule: rename it, change the watched variables, alert emails or active status

See how to talk to your AI agent using Serasa Experian Credit Monitoring.

Set up monitoring for CNPJ 33.014.556/0001-96: watch for negative annotations and bankruptcy, sending alerts to risk@company.com.

I created the rule "Negatives & Bankruptcy" (id 42, type CNPJ) with the variables for negative annotations and bankruptcy, and added the CNPJ to it. The document is now monitored; alerts will be sent to risk@company.com.

What happened with the monitored portfolio this week? Just give me the highlights.

I aggregated the alerts per document. 5 of the 120 monitored documents had events this week: 3 new negative annotations, 1 notary record, and 1 score drop below the configured interval. The most affected is CNPJ 12.345.678/0001-90 with 2 events, both unread.

Register a webhook so alerts get pushed to our collector at https://collector.example.com/serasa.

I registered the webhook (id 7): the AUTH endpoint at https://collector.example.com/serasa/auth validates delivery, and ATTRIBUTE_NEGATIVE points to https://collector.example.com/serasa/negative. Serasa will now push negative-annotation alerts there instead of only being pollable.

An **alert** is a credit event on a monitored document — a new negative annotation, a notary record, a bankruptcy filing, or a score crossing the configured interval. A **notification** is an operational event about the monitoring itself: rule created or activated, document batch processed, documents excluded, report downloaded. Alerts are the business signal; notifications are the audit trail.

Related Connectors

Yodlee

Yodlee MCP

13 tools Official

Access financial data via Yodlee — list accounts, fetch transactions, and verify banking details directly from any AI agent.

A+ View details →
Halo Security

Halo Security MCP

11 tools Official

Automate attack surface management via Halo Security — monitor assets, scans, and vulnerabilities directly from any AI agent.

A+ View details →
LawPay

LawPay MCP

12 tools Official

Accept legal payments online with trust and operating account compliance that meets bar association requirements for law firms.

A+ View details →
Everbridge Critical Management

Everbridge Critical Management MCP

10 tools Official

Equip your AI agent to manage critical notifications, track incidents, and monitor contacts via the Everbridge API.

A+ View details →