sos-company-research

Public Risk Intelligence Company Research

Use the public-risk-intelligence MCP server as the state-policy, evidence-normalization, and investigation layer. Existing installations may expose the same compatible tools under a locally assigned sos-research alias. Prefer official sources and report uncertainty explicitly.

Workflow

1. Identify the requested state and exact company-name query. If the state is missing, ask for it because US entity names are state-scoped.
2. Call get_state_access before choosing a route.
3. When a supported official API is available, call search_business with route: "auto". Do not open a browser merely to duplicate the same result.
4. Otherwise call prepare_browser_search, then execute that plan with the host's native browser capability. Use the user's named browser when they specify one. Search only the official registry URL returned by the tool and follow its verified state recipe exactly when present.
5. Convert visible result rows into {fields, text, detail_url} records and call finalize_browser_search. Use the final browser URL as source_url. This validates the official host and returns the same normalized evidence contract as an API search.
6. If a plan has no verified recipe, call list_browser_recipe_candidates for that state. Treat a candidate as a hint only: validate its visible controls before using it. Once the official page has been searched, call record_browser_recipe_observation with only public structural metadata (search control, submit control, result selector, visible column headings, and a challenge note). Never include search results, personal details, session data, cookies, or credentials in a recipe observation.
7. If the policy is blocked, do not automate the interactive search. Explain the official bulk, paid, or manual alternative returned by the tool.
8. If the page presents a CAPTCHA or human-verification action, do not bypass it. Follow the browser client's confirmation or handoff rules and continue only if permitted.
9. Stop after collecting the requested public evidence. Do not submit filings, purchase documents, create accounts, accept paid terms, or alter registry records.
10. When the task includes multiple people, companies, or relationships, call build_investigation_report with the normalized evidence. Treat analysis.correlations as evidence-backed review leads only: inspect every cited evidence and relationship ID, consider the stated benign alternatives, and never present a correlation as proof of fraud, money laundering, stolen identity, or common control.