evipedia-mcp-dev 0.1.26 → 0.1.28

package/dist/index.js

@@ -18,6 +18,8 @@ var pkg = (() => {
 var BASE_URL = (process.env.EVIPEDIA_BASE_URL ?? "https://evipedia.ai").replace(/\/$/, "");
 var SUGGEST_ENDPOINT = process.env.EVIPEDIA_SUGGEST_ENDPOINT ?? "https://formspree.io/f/myknrvdg";
 var CACHE_TTL = 5 * 60 * 1e3;
+var DEFAULT_UPDATE_DAYS = 7;
+var DEFAULT_UPDATE_MAX = 100;
 var cache = /* @__PURE__ */ new Map();
 async function fetchCached(url) {
   const now = Date.now();
@@ -39,8 +41,9 @@ Use this server whenever a user asks whether an intervention works, how strong t
 
 Typical workflow:
 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.
-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.
-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.
+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?"). With no arguments it covers the last 7 days (max 100 entries); pass 'days' for a wider window.
+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.
+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.
 
 '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.`;
 var lunrCache = null;
@@ -122,6 +125,34 @@ function createServer() {
       return { content: [{ type: "text", text: JSON.stringify(list) }] };
     }
   );
+  server2.tool(
+    "list_updates",
+    "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. Called with no arguments it returns the last 7 days (at most 100 entries); pass `days` for a different window, e.g. days: 30. 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.",
+    {
+      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 to use the default 7-day window. The catalogue turns over quickly \u2014 a large window returns hundreds of entries.")
+    },
+    async ({ days }) => {
+      const updates = await fetchCached(`${BASE_URL}/updates.json`);
+      const windowDays = days ?? DEFAULT_UPDATE_DAYS;
+      const cutoff = new Date(Date.now() - windowDays * 864e5).toISOString().slice(0, 10);
+      const matched = updates.filter((u) => u.date >= cutoff).sort((a, b) => b.date.localeCompare(a.date));
+      const rows = days === void 0 ? matched.slice(0, DEFAULT_UPDATE_MAX) : matched;
+      const list = rows.map((u) => ({
+        title: u.title,
+        slug: toSlug(u.permalink),
+        status: u.status,
+        date: u.date
+      }));
+      const window = windowDays === 1 ? "day" : `${windowDays} days`;
+      if (list.length === 0) {
+        return { content: [{ type: "text", text: `Nothing has been published or updated on evipedia in the last ${window}.` }] };
+      }
+      const note = days === void 0 ? `
+
+Default window: the last ${window}${matched.length > list.length ? `, capped at the ${list.length} most recent of ${matched.length} entries` : ""}. Pass \`days\` for a wider window.` : "";
+      return { content: [{ type: "text", text: JSON.stringify(list) + note }] };
+    }
+  );
   server2.tool(
     "get_conclusion",
     "Get just the plain-text conclusion of an evidence review.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "evipedia-mcp-dev",
-  "version": "0.1.26",
+  "version": "0.1.28",
   "description": "Internal development build of evipedia-mcp. Not for public use.",
   "type": "module",
   "bin": {