Start with the qualifier, not the number
Every score on these cards comes with a qualifier that tells you how much to trust it. Read that first.Financial health: the confidence tier
Security: what was measured
Working the financial health card
Check the tier and the trend together
Open the rationale on the weakest pillar
Check whether the inputs were peer-ranked
Read the adverse events, including the dismissed ones
Check the as-of dates before you quote a figure
Working the security posture card
Read the grade, then the factor breakdown
Open the rationale on any factor that grades poorly
p=none on the DMARC record, 1024-bit on DKIM selector selector1, a session cookie set without HttpOnly.Everything here is a public record you or the vendor can verify independently. That is what makes it usable in a conversation.Check how long the finding has been open
Compare the rating against the predictive index
Turn a finding into a question, not an accusation
p=none, so mail forged from your domain still gets delivered. Is enforcement on the roadmap?”That is a fact about a published record. The vendor can confirm it quickly, and it turns a generic security review into an answerable question.What these cards will not tell you
The same applies to financial health in a different direction: the score describes the corporate entity Coverbase bound to the vendor. If a vendor is a subsidiary and the filings belong to the parent, the score describes the parent’s balance sheet, not the entity on your contract. Check the Corporate Registration card to see which legal entity was matched.Opening the full page
Each card summarizes. Behind it sits a full page with the same data and far more of it, reached from View full analysis on the card or from the Security and Financial entries nested under Vendor Intelligence in the vendor’s left-hand navigation.Security posture
Financial health
Common questions
The vendor is public but shows Tier C. Why?
The vendor is public but shows Tier C. Why?
A security factor is missing from the breakdown.
A security factor is missing from the breakdown.
The security score moved and nothing changed at the vendor.
The security score moved and nothing changed at the vendor.
Can I dispute a finding?
Can I dispute a finding?
How often do these refresh?
How often do these refresh?
Where else this data shows up
Once enabled, both feed the rest of the platform:- Assessments consult measured posture and registry facts as authoritative evidence, ranked ahead of any web result. A control asking about email authentication gets answered from the vendor’s DNS records rather than from a marketing page.
- Intake and inherent risk score a new vendor request against its registered identity and measured posture before the web is consulted.
- MCP exposes both conversationally: “what’s the financial health score for Acme?”, “which of my vendors have DMARC set to none?”
- The API returns both on the vendor fact-sheet endpoint (the route name predates the Vendor Intelligence label). See the API reference.
Read the cards from MCP or the API
You can read both cards from an MCP client or with an API key. An MCP client reads withquery_vendors(kind="financial_health") and query_vendors(kind="security_posture"). With an API key, GET /v1/vendors/{vendor_id}/fact-sheet returns the fact sheet and POST /v1/vendors/{vendor_id}/fact-sheet/refresh regenerates it. See The vendor fact sheet.
For the full pages, see Read financial health from MCP or the API and Read and correct the scan from MCP or the API.