finding

When to Use

• Record an insight or issue discovered during analysis
• Create an evidence-backed finding that persists across sessions
• Review previously created findings for a site

Creating Findings

1. Has a clear, descriptive title
2. References specific observation IDs as evidence
3. Includes a synthesis explaining the pattern or issue

Workflow

1. Query observations to identify patterns:

get_observations({ host: "example.com", source: "extension", limit: 50 })

1. Identify the pattern — look for recurring issues, framework signals, error patterns, or notable behaviors.
2. Create the finding with evidence:

create_finding({
  title: "Mixed content: HTTP images on HTTPS page",
  url: "https://example.com",
  evidence: ["obs_a3f7b2c1", "obs_b4e8c3d2"],
  synthesis: "Homepage loads 3 images over HTTP despite serving over HTTPS. Network observations show requests to http://cdn.example.com/img/ which should use HTTPS. This triggers mixed content warnings in Chrome and may cause images to be blocked in strict mode."
})

Parameters

title

url

evidence

obs_xxx

synthesis

Finding Quality Checklist

• Title: Is it specific? "Mixed content on homepage" > "Issue found"
• Evidence: Do the observation IDs actually support the claim?
• Synthesis: Does it explain why this matters, not just what was observed?
• URL: Is it scoped to the right page or left empty for site-wide findings?

Querying Findings

All Findings

get_findings({})

Findings for a Specific Host

get_findings({ host: "example.com" })

Recent Findings

get_findings({ limit: 10 })

Finding Categories

Tips

• Create findings as you analyze, not all at the end — they persist across sessions
• Reference multiple observation IDs when a finding draws from several data points
• Use synthesis to explain the impact, not just restate the observation
• Findings with evidence chains are much more useful than findings without