Moody's Credit MCP

Get Probability of Default (Current PD, 1 year PD, 5 yr cumulative PD) with its history (monthly by default, or daily), implied rating (Current), the confidence grade and description behind the PD, the risk drivers ranked by each model input's relative contribution to the PD, Credit Default probabilities and implied ratings, the 5-year CDS-implied EDF against the 5-year CDS spread, drivers and early warning score, and Trade Credit Limits (balanced, aggressive, conservative) for a given entity ID. Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity. Any time you use data from this tool's response, always clearly state whether a value is a rating or an implied rating, and state the type of the rating (e.g., Long Term Rating, PD Implied Rating). Do not confuse implied ratings with ratings. 'Probability of Default Implied Rating' is not the same as 'Rating'. - ONLY provide 'Probability of Default Implied Rating' when the user explicitly asks for it using terms like 'Probability of Default Implied Rating', 'PD Implied Rating', or 'PD Rating' in their question. - Do not confuse ratings with 'Probability of Default Implied Rating'. - Do not provide 'Probability of Default Implied Rating' unless the user has explicitly specified it in their question.

For a given entity ID, retrieve firmographic information about the entity, including: * Legal company name, previous company name(s) and name change date(s), and alternative/ "also known as" (AKA) names * Contact information (registered address, telephone number and website) * Identifiers (Trade register number, VAT, LEI, Local National Identifiers) * Legal information (legal form, status, date of incorporation) * Standard Industry classifications (NACE, NAICS and US SIC), business description * Number of employees Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Retrieve the current Moody's roll-up Long Term Rating and Outlook, along with the ratings history since 2000, for a given entity or Structured Finance tranches (CLOs, ABS, RMBS, CMBS, etc.) to: * Understand forward-looking credit trajectory and probability of rating changes (upgrade/downgrade) * Evaluate near-to-medium term risks and opportunities * Gauge Moody's confidence level in the entity's ability to navigate business challenges Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity. Any time you use data from this tool's response, always clearly state whether a value is a rating or an implied rating, and state the type of the rating (e.g., Long Term Rating, PD Implied Rating). Do not confuse implied ratings with ratings.

Retrieve, generate, and analyze a corporate (non-bank) Moody's Scorecard for an entity through a single consolidated workflow. Replaces manually chaining `getScorecardOrganization` → `getCreditMethodology` → `runCorporateScorecardScenario` / `runCorporateScorecardSelectMethodology`. Given just `entityId`, this tool picks a mode automatically: 1. **Retrieval mode** (default — no `methodology` or `overrides`): looks up the entity's eligibility and available methodologies, then returns the full factor/subfactor breakdown and indicated outcome for its top-ranked methodology (or `methodologySlug` if given). Works for both rated and unrated entities — unrated entities still return whatever methodology detail is available, with no overall indicated outcome. 2. **Scenario mode** (`overrides` provided): runs a pure, local what-if calculation by overriding one or more subfactor values — numeric `overrideValue` for Quantitative Factor subfactors, `overrideRating` band labels (e.g. "Baa") for Qualitative Factor subfactors — and returns the recalculated rating. Omit `methodologySlug` to run across every methodology available for the entity. 3. **Hypothetical mode** (`methodology` provided): scores the entity under a methodology it is **not necessarily assigned to** (e.g. "score this entity under Homebuilding"), by borrowing that methodology's framework from a member entity and auto-filling the entity's own quantitative values where possible. Two-phase: call without `userInputs` first to discover what's missing (`status: "needs_input"`), then call again with `userInputs` covering every `needsInput` subfactor to compute (`status: "computed"`). Results are always a disclaimed hypothetical, never an official rating. `methodology` and `overrides` are mutually exclusive — pick one workflow per call. **Response modes** (all keyed by `mode`, except the shared not-found shape): * `found: false` (with `noData: true` alongside) — entity, methodology, or framework could not be resolved. * `mode: "retrieval"` — entity info plus the requested methodology's factor breakdown. * `mode: "scenario"` — `results`, one entry per evaluated methodology, each with current/scenario overall ratings (when rated) and per-subfactor ratings. * `mode: "hypothetical"`, `status: "needs_input"` — `autoFilled` and `needsInput` subfactor lists. * `mode: "hypothetical"`, `status: "computed"` — `scoredSubfactors`, `totalScore`, `indicatedOutcome`, and a `disclaimer`. Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Retrieve Moody's forward-looking view on a sector that a given entity belongs to using entity ID to: * Generate comprehensive perspective on sector-wide credit trends and dynamics * Understand structural risks and opportunities affecting all players in the industry * Identify cyclical vs. secular factors influencing sector performance * Assess regulatory, technological, and competitive forces reshaping the sector * Evaluate sovereign and macroeconomic risks that cascade through the sector * Benchmark individual entity performance against sector-wide expectations Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Get segment financials to answer questions about an entity's revenue, profit, and asset breakdown by segment (geographical, product, business, etc.). Data is sourced from the Moody's segment data tab API (industry, business, and geographic breakdowns). By default, returns the most recent 5 fiscal years of annual (YE) data. Not all companies have segment data; some report only a subset of account lines. Period filtering uses filterCriteria (aligned with getEntityFinancials_v2): - Specific years: filterCriteria: { periods: ["2024", "2023"] } - Specific quarters: filterCriteria: { periods: ["Q1 2024", "2024Q3"] } - Half-years: filterCriteria: { periods: ["H1 2024"] } - Relative quarters: filterCriteria: { periods: ["LQ", "LQ-1"] } (LQ is the most recent quarter available in the entity's data, LQ-1 the next, etc.) - Mixed: filterCriteria: { periods: ["Q1 2025", "2024", "H1 2024"] } - Annual only: filterCriteria: { excludeInterimData: true } (default when omitted) - Include interim: filterCriteria: { excludeInterimData: false } (with or without periods) LTM and YTD are not supported. Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Retrieve for a given entity details about its shareholders (owners at the first / direct level): * Shareholder name, BVD ID, country and type (corporate, individual, etc.) * Direct and total ownership percentage held by each shareholder in the entity * Information date and source Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Retrieve subsidiaries for a given entity, including: * Aggregate information for the searched entity (direct subsidiary count, corporate group size, key subsidiaries) * Subsidiary details such as legal name, location, entity type, and ownership percentages Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

For a given entity ID, retrieve the Global Ultimate Owner (GUO) — the entities or persons at the top of the ownership chain who control the company through an ownership stake meeting the minimum threshold. The minimum ownership threshold defaults to 50.01% and can be lowered to 25.01%. GUO information includes: * GUO name, BVD ID, country and type (corporate, individual, etc.) * Direct and total ownership percentage * Information date and source Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Get Shell Company Indicators (SCI) for an entity: director anomalies (flagged/atypical directorships), jurisdictional risk disparity between the entity and its subsidiaries, mass-registration patterns (shared director/address/company name), circular ownership, outlier-age key individuals (ultimate beneficial owners and beneficial owners), dormancy history, and financial anomalies (abnormal revenue-per-employee). These are corporate-structure red flags used to assess whether an entity's registry/ownership profile resembles a shell company. Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Search all the documents across all sectors or for a given entity. This tool should be used over `getEntitySectorOutlook` when no entity is specified for the question. Optional `chunks` and `pages` tune how much text is pulled per publication from the semantic index; specifying either disables LLM chunk reranking (relevance ranking then follows retrieval scores and budgets only). Note: This tool may require entity ID(s). If you need to get specific entity research and the input to this tool does not include entity ID(s), you must first call the findEntity tool to search for and obtain the appropriate entity ID(s). When the user mentions a sector or region in the prompt, pass the term verbatim via filter.sectors / filter.regions; the tool resolves names to taxonomy OWL IDs server-side, and any unresolved names are silently dropped from the filter. Any time you use data from this tool's response, always clearly state whether a value is a rating or an implied rating, and state the type of the rating (e.g., Long Term Rating, PD Implied Rating). Do not confuse implied ratings with ratings.

Search company filings and earnings call materials: annual (e.g. 10-K/20-F), interim (e.g. 10-Q/6-K), or earnings_call_transcript. You may combine multiple filing types as separate entries. A non-empty `query` string is required to search document content. Search returns semantic chunks from upstream; citation URLs come from the AIDI endpoint. Optional `reportYears` (four-digit strings, e.g. "2025") and optional `reportQuarters` ("Q1"–"Q4") scope the search. For earnings call types, these are fiscal year and quarter (available from 2020 onward). `reportQuarters` applies to interim and earnings call types and must be combined with `reportYears`; it is ignored for annual filings and when no `reportYears` is provided. When either is omitted, the latest available report is returned. `results` is always an array. When documents are still ingesting upstream, you get one row per requested entity with the same fields as `getCompanyFilings` for an ingesting response (`title`, `text`, `status`, `message`, `metadata`), plus `entityId`, and the polling guidance in `text` / `message`. When the search returns no hits for an entity, you get one `not_found` row per such entity with that same shape as `getCompanyFilings` when no filing exists (`entityId`, `title`, `text`, `status`, `message`, empty `metadata`). If the tool reports that filings are being ingested, that indicates ingestion is in progress, not a generic error—the files are typically ready in approximately 3 minutes. For MCP servers and clients: when you receive that ingestion-in-progress message, keep calling this tool with the same inputs every 30 seconds until it returns a normal successful result, then stop polling. When multiple filing types are requested (e.g. annual and interim together), each upstream search runs as a separate HTTP call to the filings service. Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity.

Search all the documents for a given entity Note: This tool requires entity ID(s) in the Base64URL-encoded entityId produced by the findEntity tool. If the input to this tool does not include a valid entity ID from the findEntity tool, you must first call the findEntity tool to search for and obtain the appropriate Base64URL-encoded entityId(s). findEntity must be called at most once per user query — if multiple entities need to be resolved, include all entity names in a single findEntity call rather than making separate calls for each entity. Any time you use data from this tool's response, always clearly state whether a value is a rating or an implied rating, and state the type of the rating (e.g., Long Term Rating, PD Implied Rating). Do not confuse implied ratings with ratings.

Search for news articles using entity IDs, keywords, or both (at least one required). Track developments, identify trends, and monitor narratives for entities or topics. Important — subjectCodes and searchType: If you pass subjectCodes and at least one value resolves to a news taxonomy ID, the run is always keyword-only (Boolean subject filter). Any requested hybrid or semantic searchType is overridden for that call; omit subjectCodes when you must keep hybrid or semantic. A warning is logged when a non-keyword searchType was requested and overridden. * Time Period: Specify dateRange (exact dates) or timeRange (preset like past7days). dateRange overrides timeRange. Default: past30days. Time period is helpful when you want to search for news articles that are within a specific time period. * timeFilterField: Which date field time range filters apply to. received_date: filter by when the article was ingested. publication_date: filter by when the article was published. Default: publication_date. * sortBy: Specifies the field by which the client wants articles to be sorted. Independent of timeFilterField. Options: relevancy (default; sends no sort_by, so the news provider applies its own default ordering, newest first), recency (newest by publication date), received_date, or publication_date. * Entity importance (optional): Per entity, mention vs significance sets the minimum entity-article relevance. The minimum is applied by the keyword search only; with searchType hybrid or semantic, results can also include articles tagged with the entity that score below it. Use searchType keyword when every result must meet the minimum. * Subject codes (optional): subjectCodes narrows results to validated news taxonomy IDs; only pass when the user explicitly asked for specific subjects—do not invent codes. If every code is invalid after validation, the tool returns no news (no widening to the default subject universe). When codes resolve, searchType is forced to keyword (see important note above). * Relaxed retry: if a search using subjectCodes or importance returns no articles, it is retried once with those filters dropped. Results in that case are broader than requested, so do not present them as satisfying the subject or relevance constraint. Usage Patterns: * Entity-specific: Search news for specific entities. If entity IDs are not provided, call the findEntity tool first to obtain the required entity IDs. * Topic-based: Search by query/keywords only without entity IDs for general news on any topic. * Combined: Use both to filter entity news by keywords.

Search Moody's Précis research for themes, topics, and insights on sovereigns from all reports since 2024.