Methodology and operating model

MCP methodology

Read-only Model Context Protocol access to public 13FLOW resources. Private and payment tools are absent from the default public Registry profile.

publictracked funds

MCPfilings or tools

fail-closedquality posture

292bf187d3d5served SHA

Method

Public tools must not require browser auth, cookies or checkout.
Private tools must be absent from the default public MCP profile.
MCP responses must expose product status, validation boundary and data-quality warnings.
Tool output must not claim validated alpha, probabilities or expected returns.
Agent statistics must remain aggregate-only and must never retain IP addresses, User-Agents, client versions, arguments, prompts, responses or keys.
Private MCP tools call the isolated private API service rather than reading the private DB directly.

01Start from the live/status surface and confirm the data quarter.

02Use fund, stock and signal pages to inspect source-linked evidence.

03Read validation status before treating a score as decision support.

04Keep 13F delay, Form 4 scope and quality warnings in the note.

Validation status: see API contract