truthstack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VAULT_API_KEY | Yes | Your TruthStack API key. Obtain one by contacting chris@truthstack.co or visiting truthstack.co | |
| VAULT_API_URL | Yes | The URL for the TruthStack API | https://api.truthstack.co |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_interactionsA | Check if supplements are safe with medications. Returns risk level, FDA adverse event data, CYP450 conflicts. Use when user mentions supplements + meds. |
| search_compoundsB | Fuzzy search for supplement compounds. 584 aliases across 95 compounds. Resolves misspellings, brands, abbreviations. |
| get_compound_infoB | Get detailed compound profile with interactions, research findings, and aliases. |
| explain_interactionA | Human-readable explanation of WHY an interaction is risky. Returns mechanism, severity, evidence summary. |
| get_evidenceC | Raw evidence bundle: FAERS counts, CYP data, research grades, label warnings. For citing sources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose with no overlap: checking interactions, explaining them, getting compound info, retrieving evidence, and searching compounds. The descriptions specify unique use cases, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (e.g., check_interactions, explain_interaction, get_compound_info, get_evidence, search_compounds). This uniformity enhances readability and predictability for agents.
With 5 tools, the server is well-scoped for its supplement-medication interaction domain. Each tool serves a specific, necessary function, avoiding bloat while covering key operations like search, retrieval, and analysis.
The toolset covers core workflows: searching compounds, retrieving info, checking interactions, explaining them, and citing evidence. A minor gap might be the lack of a tool for managing or updating data, but the surface is largely complete for the stated purpose.