All release walkthroughs

LIQUILENS · PLUGIN REVIEW EVIDENCE

MyQuant App Discovery

Five public research workflows, shown with actual captured MCP requests and results.

90 seconds · edited browser recording · no audio · no model API calls for this recording.

Inspect the interactive capture viewer · Case transcript · Recording manifest · Underlying service captures

What this demonstrates

The video shows direct calls to the public MCP service and preserves returned source dates, restrictions and unavailable states. It is not a native plugin-installation recording or a new model-routing test. Negative model cases remain unexecuted in this capture.

The product skill and negative model-routing cases are review expectations, not newly executed model tests. No trading, enrollment, collection, private-record access or execution was performed. NoiseFloor examples use synthetic inputs; all other values retain their service-provided dates and restrictions.

Cases shown

  1. Offline reading discovery

    Inspect MyQuant's published offline-reading capabilities and limits without checking or changing my device.

    Interpretation boundary: Explain returned features and boundaries. Do not claim that content is downloaded or available on the user's device.

  2. Topic controls

    What topic controls does MyQuant document, and which actions would still require me to use the app?

    Interpretation boundary: Describe documented controls and distinguish feature discovery from reading or changing preferences.

  3. Briefing and feed validation

    Read MyQuant's capability metadata and explain its briefing and feed-validation features and stated limits.

    Interpretation boundary: Summarize documented features without claiming to fetch a briefing, validate a particular feed or inspect on-device content.

  4. Integration surface discovery

    Identify MyQuant's documented public API and MCP surfaces and product boundaries for a possible integration.

    Interpretation boundary: Report supported surfaces and limits from metadata. Do not infer installation availability or access to private app state.

  5. Compatibility heartbeat

    Check MyQuant's non-sensitive API and MCP compatibility heartbeat and summarize its status.

    Interpretation boundary: Report returned compatibility metadata. Do not equate endpoint response with installed-app health, feed freshness or device access.

Endpoint: https://agents.seiche.info/products/myquant-app/mcp

Video SHA-256: 9ba058d77b7a306e9f261b28c0e24aa0dd906bdae08278cac06e55a00dd8ac31

Draft review evidence. This page is not an OpenAI approval or publication receipt.