PillScout
Know what everything you take is doing.
Connect your medications, supplements, OTC, and compounds to Claude once. When you ask a question that touches your cabinet, PillScout checks it against a verified safety engine: interactions, cumulative risk, condition context, pregnancy rules, and clear signals showing what's verified and what isn't.
Request a beta keyPillScout is in closed beta.
What's in the engine
PillScout runs as an MCP server that connects to Claude. When you ask about something you take, it checks your full cabinet instead of answering from memory.
Persistent cabinet. Connect once. Your full list travels across every Claude conversation. No re-listing what you take every time you ask.
Verified ingredient profiles. 151 profiles with citations covering the medications, supplements, and compounds people actually take.
Real-world safety checks. Interactions, cumulative risk, CYP pathways, bleeding risk, symptom matching, and timing rules, evaluated across your full cabinet.
Patient context. Age, conditions, pregnancy, and lactation status travel with your cabinet. Rules apply when they should, and don't when they shouldn't.
Symptom-to-cabinet mapping. Tell Claude what you're feeling. PillScout maps it back to what in your cabinet could plausibly be causing it, with confidence levels.
Three-tier safety architecture. Verified data first, class-level rules second, AI reasoning last. Every answer shows which layer it came from.
Coverage signals: what's verified, what isn't
Every safety engine has gaps. The question is whether it tells you where they are.
PillScout shows you what's database-verified, what's inferred from class rules, and what's AI-estimated. You see where the answer comes from, not just the answer itself.
Gaps aren't failures. They're transparency. A clean result with full coverage means something. A clean result with partial coverage means something different. You get to see which one you have.
How PillScout gets better
Every time someone uses it, the next gap becomes visible.
When an ingredient or combination isn't fully covered, that gap is recorded: just the missing piece and how often it comes up. Not your cabinet. Not your identity. Not your conversations. Only the structured inputs to the safety tools.
That means the database grows based on what people actually ask about. The most common gaps become the next verified profiles.
Part of a bigger picture
You can already track a lot.
Sleep with Oura Ring. Workouts with Strava. Nutrition with MyFitnessPal.
Each one tells your AI something real about your life.
PillScout is the one that knows what you take. And without that, the picture is incomplete.
If your AI sees your sleep but not your magnesium, your heart rate but not your medication, your nutrition but not your supplements, it's missing a key part of what's actually driving how you feel.
Once your cabinet is there, your AI can reason across everything:
"I slept poorly last night. I took magnesium. Did it help?"
"Is this supplement affecting my heart rate?"
Those become questions your assistant can actually answer.
I'm ScoutI don't guess what you takeI check it
How PillScout got here
I started PillScout because the tools I wanted didn't exist, or took too much work to be useful.
I'd see a supplement making big claims and wonder: can I take this with what I'm already on? A family member is on heart medication, would this help or hurt them? My mom takes prescriptions from different doctors and a bunch of supplements and always feels nauseous. Is one of them causing it? Could another one actually help?
Checking meant searching, piecing things together, and usually giving up.
AI can answer now, but only if it knows everything you take.
I asked my kids to build it. They said, "you build it." So I did.
I started with a web app because that's what was possible. Then MCP came along, and the version I actually wanted became possible: a cabinet your AI assistant uses automatically, wherever you're already talking to it.
That's what PillScout was always meant to be.
Request a beta key
PillScout is in closed beta. I'm handing keys out one at a time to clinicians, researchers, builders, students, caregivers, and anyone curious about health tech.
Email pillscout@pillscout.health with a line about who you are and what you'd try it on. I read every one.
If you'd also like to see the beta web app, mention it in your note.