npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@kynver-app/mcp-analyst

v0.1.4

Published

Kynver Analyst MCP server — data collection, hypothesis tracking, analysis pipeline

Readme

@kynver-app/mcp-analyst

Kynver Analyst MCP server. Proxies 56 tools to /api/agents/analyst/* on your Kynver deployment — dashboards, memory, hypotheses, trackers, research (analyst_research uses Perplexity where configured), data collection, daily-intelligence scheduling (including analyst_schedule_weekly_pipeline), predictions, patterns, notifications, and the analyst_market_* trading-desk surface.

This is the external MCP surface for Claude Code, Cursor, OpenClaw, etc. The in-app Kynver agent uses separate synthetic dispatch; this package is for clients that talk HTTP to a live Kynver app.

Agentic OS (agent_os_*) lives in a sibling package: @kynver-app/mcp-agent-os. Mount both MCP servers if you need analyst + structured agent identity / goals / projects / Ghost memory.

Tools (overview)

| Family | Count | Notes | |--------|------:|--------| | analyst_* (general) | 40 | Memory, dashboards, collections, hypotheses, trackers, scheduling (daily + weekly pipeline), research, intent/setup, daily reports & schedules, addenda, insiders ingest, fear & greed, predictions, patterns, notification prefs | | analyst_market_* | 16 | Admin-only on Kynver — market data, backtests, paper accounts, proposals, orders, positions, bars, chains |

Full JSON schemas are kept in the Kynver repo at lib/mcp/tool-manifests/kynver-mcp-analyst.json (used as a static fallback where stdio spawn is unavailable).

Env

| Var | Purpose | |-----|---------| | KYNVER_API_URL | Kynver origin (e.g. https://kynver.com). In development, stdio may default to http://localhost:3000 if unset — production MCP hosts should set this explicitly. | | KYNVER_API_KEY | Bearer token sent as Authorization. Required for authenticated calls to user-scoped analyst routes. | | KYNVER_SERVICE_SECRET | Required when using SSE transport so the server can forward X-Kynver-User-Id + service secret after resolving the API key owner (see src/sse.ts). | | KYNVER_FETCH_TIMEOUT_MS | Optional HTTP timeout for upstream Kynver calls (default 120000). | | PORT | SSE listener port (default 3100 — differs from @kynver-app/mcp-agent-os, which defaults to 3101). |

Trading desk: analyst_market_* routes enforce requireAdminUser on the API. Your API key must belong to a Kynver admin (ADMIN_USER_IDS / ADMIN_EMAILS on the server).

Transports

  • Stdio (default): node dist/index.js or the kynver-mcp-analyst bin — set KYNVER_API_URL + KYNVER_API_KEY.
  • SSE: npm run start:sse / node dist/sse.js — exposes /sse and /messages; external clients authenticate with an API key; requires KYNVER_SERVICE_SECRET aligned with the web app for impersonation headers.

Cursor / OpenClaw config (published package)

{
  "mcpServers": {
    "kynver-analyst": {
      "command": "npx",
      "args": ["-y", "@kynver-app/mcp-analyst"],
      "env": {
        "KYNVER_API_URL": "https://kynver.com",
        "KYNVER_API_KEY": "${KYNVER_API_KEY}"
      }
    }
  }
}

Add a second block for kynver-agent-os using @kynver-app/mcp-agent-os when you need Agentic OS tools (see that package’s README).

Monorepo dev

From repo root:

npm install
cd packages/kynver-mcp-analyst
npm run build
node dist/index.js

Publish after build:

npm publish --access public