Structured output for tooling and recordkeeping
Use JSON when the report needs to move into a review workflow, audit trail, or downstream analysis step.
Output surface
Reports that stay readable after the scan ends.
Veridicus Scan turns the scan result into a report users can act on: risk score, risk band, findings, guidance, and coverage notes, followed by JSON or PDF export for sharing, review, or documented handoff. The same report surface is available to premium MCP workflows through Get Report and Export Report.
What the report contains
The decision surface should be compact, not vague.
A useful scan report does not bury the answer. It needs to summarize risk quickly, show what was found, and explain the scan boundary clearly enough that a user can justify what happens next.
Risk summary
- Risk score and band for fast triage
- Finding count and severity cues
- Clear action language for the next step
Evidence layer
- Evidence-backed findings instead of generic warnings
- Signal details grounded in what the scan saw
- Coverage notes when the scan was partial
Handoff path
- Share flow for JSON or PDF export
- Review-friendly output for teammates
- Local-first posture carried into the export step
Readable proof
The report should answer what happened, where, and what to do now.
This is where the score becomes usable. Findings, evidence wording, coverage state, and action guidance all need to stay legible under pressure.
REPORT / FINDINGS / LOCAL EXPORT
risk band
elevated
coverage
complete URL scan, strict redirect mode
finding
directive-style instruction hidden in parser-visible content
guidance
review before forwarding into an assistant or internal AI workflow
Export behavior
Share the outcome without oversharing the suspicious content.
The export layer exists for review and evidence handling. The default is conservative: enough report detail to collaborate, without forcing the full suspicious text into every handoff.
Readable output for human review
Use PDF when the handoff needs a stable, shareable report surface that preserves the main decision points clearly.
Evidence stays bounded until a user opts into more detail
Evidence snippets begin redacted by default so the export can communicate risk without becoming an accidental content dump.
Next step
Take the report into URL policy, automation, or the workflow that needs the result.
Move from the report into redirect handling, local MCP automation, or the concrete use case that depends on the output.