Does an MCP Scan Save Reddit Threads to My Monitor Dashboard?

No. RedditScanner's scan_reddit MCP method returns scored threads in the request response, but it does not save them to a dashboard monitor. If you need a lasting research record, capture the returned URLs yourself. An MCP result is not a new row in your monitor history.

I traced the MCP, REST, and dashboard scan routes in the repository on October 29, 2026. This describes their code paths, not a live scan or a guarantee about Reddit search coverage. New accounts currently redirect to a closed-accounts page, so this is a guide to the implementation rather than an invitation to create an account.

Follow a result through each route

The MCP documentation exposes scan_reddit with a keyword, optional subreddits, and a minimum score. The method calls the shared scanner and returns its opportunities as JSON. It never receives a monitor ID or writes an opportunity row. The separate GET /api/v1/opportunities REST endpoint also runs the shared scanner and returns JSON without storing the matches.

The dashboard takes a different path. Its results screen first reads stored opportunities for one monitor ID. When a user starts a manual scan, the screen sends that monitor ID, its keyword, subreddits, and score floor to POST /api/scan. If the authenticated request finds at least one opportunity, that route loads existing rows for the monitor, adds a snapshot to each matching row or creates one for a new thread, and upserts those rows by monitor ID and Reddit post ID. It then updates the monitor's last-scan timestamp. The screen reloads its stored rows after the request succeeds.

This is a code-path comparison, not a claim that every dashboard scan saves a result. When a scan returns no matches, the persistence branch does not run. A stored row can also reflect an earlier scan, so seeing it on the screen does not prove a new search found it today. Why a keyword alert may miss a thread covers the search window and error cases.

Keep an agent's findings in your own log

Suppose an agent calls scan_reddit for a product problem and receives three candidate URLs. Those three URLs exist in that response; they have not been assigned to any dashboard monitor. This is an illustrative workflow, not observed customer or Reddit data. Record the returned URL, post ID, query, scan time, and the exact question you want to investigate before running the agent again. Reopen each thread to check its current content and community rules rather than treating a stored score as permission to reply.

If you compare later runs, compare post IDs and query settings as well as scores. The shared scanner searches recent posts sorted newest and scores each match using the query and the post's age and engagement. Results can therefore change without a dashboard history entry. This is separate from the question of whether an agent can post a Reddit reply, which this MCP endpoint cannot do.

The practical boundary is simple: use MCP for a returned search result, use a monitor scan for the dashboard's persisted snapshots, and keep your own notes if you need a record you can audit later. Neither route by itself measures signups, customer demand, or the success of a reply.