Methodology and operating model

MCP methodology

Read-only Model Context Protocol access to public 13FLOW resources, plus gated Pro tools that require an existing Pro API key or configured paid settlement path.

Machine-readable contract Validation boundary Developer docs

publictracked funds

MCPfilings or tools

fail-closedquality posture

d002a2dd2ffcserved SHA

Method

Public tools must not require browser auth, cookies or checkout.
Private tools must fail closed without a valid operator-issued credential.
MCP responses must expose product status, validation boundary and data-quality warnings.
Tool output must not claim validated alpha, probabilities or expected returns.
Private MCP tools call the isolated private API service rather than reading the private DB directly.

How to read 13FLOW output

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.

Sources and contracts

Interpretation boundary

Run public smoke after deployment.
Verify MCP tools/list public contract.
Verify private MCP tools fail closed without a valid operator-issued key.
Run a valid private key probe before claiming private MCP readiness.
Record key id, scopes, limits and rotation date in the operator note.

Validation status: see API contract