All release walkthroughs

LIQUILENS · PLUGIN REVIEW EVIDENCE

MyQuant Editorial

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. Recent stories

    Retrieve five recent MyQuant archive stories and summarize their evidence, publication dates and limitations.

    Interpretation boundary: Use limit 5, preserve source and evidence clocks, and report unavailable feeds explicitly rather than inventing stories.

  2. Plain-text search

    Search the MyQuant archive for 'dollar funding' and show up to five matching stories with source links.

    Interpretation boundary: Use query dollar funding and limit 5. Explain empty results without inventing matches or treating text matching as semantic ranking.

  3. Exact story retrieval

    List the newest available MyQuant story, then retrieve it using the exact returned story ID and summarize its evidence limits.

    Interpretation boundary: Discover the ID with limit 1 and copy it exactly into get_story. If no story is returned, stop and report the gap.

  4. Archive capabilities

    Inspect MyQuant Editorial's supported content tools, API routes and content limits before I build an archive-reading workflow.

    Interpretation boundary: Describe returned capabilities and distribution boundaries; do not claim this discovery call retrieved stories.

  5. Connection compatibility

    Check MyQuant Editorial's API and MCP compatibility metadata and report its deployed source identity if available.

    Interpretation boundary: Report returned versions, checked_at and source identity when present. Endpoint compatibility is separate from feed freshness.

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

Video SHA-256: a9a659499db9eb8e86d6dd79b27e934a4d2274769aa011e8361a5a865f1a5741

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