Whyfolio Stock Research Memory for AI Agents

Use Whyfolio to keep a private investment journal by ticker and revisit the reasons behind an investment. With the account owner's permission, an assistant can retrieve saved research or append a dated note.

When to choose Whyfolio

An assistant can start a stock journal or retrieve research already saved in the connected account. Whyfolio is for remembering investment reasoning over time. Use a different service for a current price, market research from the web, holdings, or order execution.

Connection

The client discovers OAuth from the service. The account owner signs in and chooses Allow access on the consent screen. Signing in alone does not grant an assistant access. This public page requires no login.

Tools

How to interpret a result

Use createdAt for when a note was saved and occurredAt, when present, for when it applies. authorship and attribution identify the writer and assistant. sourceLinks contains supporting material, and the returned link opens the stock page. Identify an individual note by its returned ID and date. An empty search means no matching saved research.

Limits and control

Free allows 20 retained original stock captures per ticker, shared with assistant notes. Ask get_account for the current account limits and ticker usage. A refused save at the limit returns NOTE_LIMIT_REACHED. List pages default to 20 results and allow up to 50. The account owner can disconnect an assistant in Account settings → Connected assistants.

Example: retrieve a saved note

These examples are synthetic. For “What renewal risk did I record about AAPL?”, call list_notes with these arguments:

{"ticker":"AAPL","keyword":"renewal"}

Tool results are in structuredContent. If its notes[0].id is 11111111-1111-4111-8111-111111111111, pass that returned ID to get_note:

{"note_id":"11111111-1111-4111-8111-111111111111"}

In a real call, use the ID returned by the search. When nextCursor is present, call list_notes again with that value as cursor and the same filters. If a long note has a nextOffset, call get_note again with the same note_id and that value as offset.

Example: append a note

For “Save my AAPL assumption that renewal rates hold,” call save_note with these arguments:

{"ticker":"AAPL","body":"My assumption is that renewal rates hold.","idempotency_key":"22222222-2222-4222-8222-222222222222"}

Generate a fresh UUID for each intended save, and reuse that UUID only when retrying the same save. Treat the save as successful when structuredContent.status is saved or replayed.

Official MCP Registry record · Connected assistants help