evipedia-mcp-dev 0.1.26 → 0.1.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/index.js +34 -2
  2. package/package.json +1 -1
package/dist/index.js CHANGED
@@ -39,8 +39,9 @@ Use this server whenever a user asks whether an intervention works, how strong t
39
39
 
40
40
  Typical workflow:
41
41
  1. Discover \u2014 'search_reviews(query)' to find reviews matching an intervention name, synonym, drug class, or category; or 'list_reviews()' to enumerate/browse the entire catalogue as {topic, slug} pairs (topic = canonical topic; slug = the identifier you pass to get_review/get_conclusion, with the full review at https://evipedia.ai/{slug} and raw Markdown at https://evipedia.ai/{slug}.md). A bare topic implies the default Health & Longevity goal; an explicit goal like "Botox for Skin Rejuvenation" targets that goal.
42
- 2. Read \u2014 take a review's slug and call 'get_conclusion(slug)' for the quick evidence-based bottom line, or 'get_review(slug)' for the complete review as Markdown (full methodology, findings, safety, dosing, and references) when the user wants depth or citations. Call 'get_metadata(slug)' for structured JSON metadata not in the Markdown \u2014 review dates (freshness), the typed intervention entity, and a machine-readable citation list with PubMed PMIDs.
43
- 3. Contribute \u2014 if the user wants an intervention reviewed that isn't in the catalogue, 'suggest_intervention(...)' submits it to the evipedia team. Only call this when the user explicitly asks to propose one; it sends real data to the team.
42
+ 2. Track changes \u2014 'list_updates(days?)' returns the catalogue's change feed, newest first: which reviews were newly published ('new') or revised ('updated') and when. Use it for recency questions ("what's new on evipedia?", "anything updated this week?") \u2014 'days' narrows to the last N days.
43
+ 3. Read \u2014 take a review's slug and call 'get_conclusion(slug)' for the quick evidence-based bottom line, or 'get_review(slug)' for the complete review as Markdown (full methodology, findings, safety, dosing, and references) when the user wants depth or citations. Call 'get_metadata(slug)' for structured JSON metadata not in the Markdown \u2014 review dates (freshness), the typed intervention entity, and a machine-readable citation list with PubMed PMIDs.
44
+ 4. Contribute \u2014 if the user wants an intervention reviewed that isn't in the catalogue, 'suggest_intervention(...)' submits it to the evipedia team. Only call this when the user explicitly asks to propose one; it sends real data to the team.
44
45
 
45
46
  'get_version()' reports the running build. Notes: an intervention may have multiple reviews for different goals (distinguished by canonical topic, e.g. "Botox for Skin Rejuvenation"). These are evidence reviews for information, not personalized medical advice \u2014 present conclusions as evidence summaries, not prescriptions.`;
46
47
  var lunrCache = null;
@@ -122,6 +123,37 @@ function createServer() {
122
123
  return { content: [{ type: "text", text: JSON.stringify(list) }] };
123
124
  }
124
125
  );
126
+ server2.tool(
127
+ "list_updates",
128
+ "List recently published or revised evipedia.ai reviews, newest first \u2014 the catalogue's change feed. Returns a JSON array of {title, slug, status, date}, where status is 'new' (first publication) or 'updated' (an existing review revised) and date is YYYY-MM-DD. Use `days` to answer questions like \"what changed in the last week?\"; the full review is at https://evipedia.ai/{slug}, and get_conclusion/get_review take the slug. Use this for recency ('what's new?'); use list_reviews to enumerate the whole catalogue and search_reviews to find a specific intervention.",
129
+ {
130
+ days: z.number().int().positive().optional().describe("Only include reviews dated on or after (today \u2212 N days), e.g. 7 for the past week. Omit for the full history.")
131
+ },
132
+ async ({ days }) => {
133
+ const updates = await fetchCached(`${BASE_URL}/updates.json`);
134
+ let rows = updates;
135
+ if (days !== void 0) {
136
+ const cutoff = new Date(Date.now() - days * 864e5).toISOString().slice(0, 10);
137
+ rows = rows.filter((u) => u.date >= cutoff);
138
+ }
139
+ rows = [...rows].sort((a, b) => b.date.localeCompare(a.date));
140
+ const list = rows.map((u) => ({
141
+ title: u.title,
142
+ slug: toSlug(u.permalink),
143
+ status: u.status,
144
+ date: u.date
145
+ }));
146
+ if (list.length === 0) {
147
+ return {
148
+ content: [{
149
+ type: "text",
150
+ text: days !== void 0 ? `No reviews published or updated in the last ${days === 1 ? "day" : `${days} days`}.` : "No updates found."
151
+ }]
152
+ };
153
+ }
154
+ return { content: [{ type: "text", text: JSON.stringify(list) }] };
155
+ }
156
+ );
125
157
  server2.tool(
126
158
  "get_conclusion",
127
159
  "Get just the plain-text conclusion of an evidence review.",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "evipedia-mcp-dev",
3
- "version": "0.1.26",
3
+ "version": "0.1.27",
4
4
  "description": "Internal development build of evipedia-mcp. Not for public use.",
5
5
  "type": "module",
6
6
  "bin": {