@4da/mcp-server 5.0.4 → 6.0.1

package/dist/schemas/ecosystem-pulse.json

@@ -1,17 +0,0 @@
-{
-  "name": "ecosystem_pulse",
-  "description": "Live ecosystem news relevant to your tech stack. Surfaces trending Hacker News discussions filtered by your detected technologies. Updated on server startup.\n\nPrivacy: No personal data sent. Only generic tech keywords used for filtering. Call when the user asks what is new, trending, or happening in their ecosystem or tech community.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "min_points": {
-        "type": "number",
-        "description": "Minimum HN points to include. Default: 0"
-      },
-      "limit": {
-        "type": "number",
-        "description": "Maximum headlines to return. Default: 15"
-      }
-    }
-  }
-}

package/dist/schemas/get-actionable-signals.json

@@ -1,29 +0,0 @@
-{
-  "name": "get_actionable_signals",
-  "description": "Classify content into actionable signal types (security_alert, breaking_change, tool_discovery, tech_trend, learning, competitive_intel) with priority levels. Cross-references against user's tech stack. Call when the user wants to know what is actionable or urgent, not just what is relevant.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "priority_filter": {
-        "type": "string",
-        "description": "Filter by priority level",
-        "enum": ["critical", "high", "medium", "low"]
-      },
-      "signal_type": {
-        "type": "string",
-        "description": "Filter by signal type",
-        "enum": ["security_alert", "breaking_change", "tool_discovery", "tech_trend", "learning", "competitive_intel"]
-      },
-      "limit": {
-        "type": "number",
-        "description": "Maximum signals to return (default: 20, max: 100)",
-        "default": 20
-      },
-      "since_hours": {
-        "type": "number",
-        "description": "Only include items from last N hours (default: 48)",
-        "default": 48
-      }
-    }
-  }
-}

package/dist/schemas/get-context.json

@@ -1,17 +0,0 @@
-{
-  "name": "get_context",
-  "description": "Get the user's context - what 4DA knows about them.\n\nReturns information about:\n- Static Identity: User-declared role, tech stack, domains, interests, and exclusions\n- ACE Context (optional): Auto-detected technologies and active topics from recent activity\n- Learned Preferences (optional): retained compatibility field; implicit preference learning no longer contributes to scoring\n\nCall FIRST when you need to understand what the user works on or cares about before answering or recommending.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "include_ace": {
-        "type": "boolean",
-        "description": "Include ACE-detected context (detected tech, active topics). Default: true"
-      },
-      "include_learned": {
-        "type": "boolean",
-        "description": "Include the retained learned-preferences compatibility field. Default: true"
-      }
-    }
-  }
-}

package/dist/schemas/get-relevant-content.json

@@ -1,26 +0,0 @@
-{
-  "name": "get_relevant_content",
-  "description": "Get filtered relevant content from 4DA's personalized feed.\n\nReturns content items that match the user's explicit interests, tech stack, and ACE-detected context.\nItems are scored based on:\n- Explicit interests declared by the user\n- Tech stack and domains\n- ACE-detected context (recent files, projects, git activity)\n\nIMPORTANT for autonomous use: each item carries an `evidence_class` describing how it is grounded. The relevance_score float is NOT comparable across classes — gate actions on evidence_class, not the number:\n- \"osv_verified\": a security advisory matching one of the user's INSTALLED dependencies — safe to act on\n- \"dependency_grounded\": matched one of the user's declared dependencies — trustworthy\n- \"semantic_only\": topical/embedding relevance with NO dependency edge — surface to the human, verify before acting\n- \"keyword_heuristic\": standalone-mode keyword score (no Rust pipeline) — weakest signal\n\nCall when the user asks what to read, what is relevant to them, or for content on a topic.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "min_score": {
-        "type": "number",
-        "description": "Minimum relevance score (0.0-1.0). Default: 0.35"
-      },
-      "source_type": {
-        "type": "string",
-        "description": "Filter by source type: \"hackernews\", \"arxiv\", or \"reddit\". Leave empty for all sources.",
-        "enum": ["hackernews", "arxiv", "reddit"]
-      },
-      "limit": {
-        "type": "number",
-        "description": "Maximum number of items to return. Default: 20, max: 100"
-      },
-      "since_hours": {
-        "type": "number",
-        "description": "Only include items discovered in the last N hours. Default: 24"
-      }
-    }
-  }
-}

package/dist/schemas/knowledge-gaps.json

@@ -1,14 +0,0 @@
-{
-  "name": "knowledge_gaps",
-  "description": "Detect knowledge gaps in your project dependencies.\n\nIdentifies dependencies you use but haven't been tracking content about — blind spots where a breaking change, security advisory, or major release could catch you off guard. Call when the user asks what they are missing, what they are not tracking, or where their blind spots are.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "min_severity": {
-        "type": "string",
-        "enum": ["critical", "high", "medium", "low"],
-        "description": "Minimum gap severity to include. Default: medium"
-      }
-    }
-  }
-}

package/dist/schemas/record-feedback.json

@@ -1,24 +0,0 @@
-{
-  "name": "record_feedback",
-  "description": "Record explicit user interaction history for a content item.\n\nFeedback actions:\n- \"click\": User clicked/opened the item\n- \"save\": User saved/bookmarked the item\n- \"dismiss\": User dismissed the item\n- \"mark_irrelevant\": User marked item as not relevant\n\nThis records what happened; it does not train content preferences (interaction counts only graduate scoring's bootstrap gate). Call after the user reacts to a surfaced item (opens, saves, or dismisses it).",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "item_id": {
-        "type": "number",
-        "description": "The database ID of the item"
-      },
-      "source_type": {
-        "type": "string",
-        "description": "The source type: \"hackernews\", \"arxiv\", or \"reddit\"",
-        "enum": ["hackernews", "arxiv", "reddit"]
-      },
-      "action": {
-        "type": "string",
-        "description": "The feedback action: \"click\", \"save\", \"dismiss\", or \"mark_irrelevant\"",
-        "enum": ["click", "save", "dismiss", "mark_irrelevant"]
-      }
-    },
-    "required": ["item_id", "source_type", "action"]
-  }
-}

package/dist/schemas/upgrade-planner.json

@@ -1,22 +0,0 @@
-{
-  "name": "upgrade_planner",
-  "description": "Ranked standalone upgrade recommendations for project dependencies — call before upgrading, adding, or auditing any dependency to pick the safest order. Combines vulnerability severity, deprecation status, and version distance into a prioritized plan.\n\nSplits recommendations three ways: quick wins (safe patch/minor upgrades), breaking changes (major version bumps), and transitive CVEs marked waiting_on_upstream (not declared in your manifest — the fix arrives via a parent package update or a lockfile refresh). Call dependency_health first for registry context and vulnerability_scan first for a CVE-aware plan; without a scan the output says it is CVE-blind.\n\nProvenance: standalone heuristic — a point-in-time plan from local lockfiles plus live registry/OSV lookups, not the 4DA desktop app's cross-project, version-confirmed plan.\n\nPrivacy: live mode may query public registries and OSV with package names and versions. It never sends source code.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "include_dev": {
-        "type": "boolean",
-        "description": "Include devDependencies. Default: false."
-      },
-      "max_recommendations": {
-        "type": "number",
-        "description": "Maximum recommendations to return. Default: 20."
-      },
-      "risk_threshold": {
-        "type": "string",
-        "enum": ["all", "low", "medium", "high", "critical"],
-        "description": "Only show upgrades at or above this risk level. Default: all."
-      }
-    }
-  }
-}

package/dist/schemas/vulnerability-scan.json

@@ -1,26 +0,0 @@
-{
-  "name": "vulnerability_scan",
-  "description": "Scan project dependencies for known vulnerabilities (CVEs) using OSV.dev.\n\nReturns severity levels, fix versions, direct/transitive scope, and upgrade recommendations for npm, Rust, Python, and Go dependencies. Zero configuration — scans the complete resolvable lockfile package set.\n\nPrivacy: only sends package names and versions (public manifest data). No code, paths, or personal data transmitted. Call when the user asks about security, vulnerabilities, or CVEs, or before you recommend adding a dependency.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "project_path": {
-        "type": "string",
-        "description": "Project directory to scan. Default: current working directory."
-      },
-      "severity_filter": {
-        "type": "string",
-        "enum": ["critical", "high", "medium", "low"],
-        "description": "Only show vulnerabilities at or above this severity level."
-      },
-      "include_dev": {
-        "type": "boolean",
-        "description": "Include known direct devDependencies. Transitive dev/runtime scope may be unknown. Default: false."
-      },
-      "force_refresh": {
-        "type": "boolean",
-        "description": "Ignore cache and fetch fresh data from OSV.dev. Default: false."
-      }
-    }
-  }
-}

package/dist/schemas/what-should-i-know.json

@@ -1,19 +0,0 @@
-{
-  "name": "what_should_i_know",
-  "description": "Pre-task intelligence briefing. Given a task description and optional file paths, returns filtered advisories (security alerts, breaking changes), active decision windows, signal chains, relevant past decisions/memories, and a delegation assessment. Call this before starting any non-trivial task to get caught up on what matters. If the task involves upgrading, adding, or auditing dependencies, follow with upgrade_planner for the ranked plan.",
-  "inputSchema": {
-    "type": "object",
-    "properties": {
-      "task": {
-        "type": "string",
-        "description": "Description of what you are about to work on"
-      },
-      "files": {
-        "type": "array",
-        "items": { "type": "string" },
-        "description": "File paths involved in the task (optional). Improves relevance filtering."
-      }
-    },
-    "required": ["task"]
-  }
-}