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

veska-mcp

v0.1.0

Published

Veska AI — MCP server (npx -y veska-mcp). Tools: search/install/compose/run.

Readme

@veska/mcp

MCP server do Veska AI. Expõe o catálogo do Veska como tools MCP para clientes como Claude Desktop, Claude Code e Cursor, via transporte stdio.

O MCP é parte da distribuição do produto: o assistente do usuário descobre, instala e executa skills do Veska direto pelas tools.

Tools

| Tool | Auth | Descrição | | ----------------- | ---- | ------------------------------------------------------------------------- | | veska_search | não | Busca skills por texto livre e categoria. Retorna slug/nome/descrição. | | veska_get_skill | não | Detalhe de uma skill + corpo (body) da versão latest. | | veska_install | sim | Registra instalação (claude-code/cursor/codex) e retorna o body da skill. | | veska_compose | sim | Executa um prompt no Composer (consome créditos). | | veska_run | sim | Executa uma skill via Runner com um input (consome créditos). | | veska_balance | sim | Saldo de créditos da conta. |

Tools autenticadas exigem VESKA_TOKEN. Sem ele, retornam erro claro orientando a configurar o token. Erros 401 (token inválido/ausente) e 402 (créditos insuficientes) são traduzidos em mensagens acionáveis no conteúdo da resposta.

Configuração por ambiente

| Variável | Default | Descrição | | --------------- | --------------------------- | --------------------------------- | | VESKA_API_URL | http://localhost:3001/api | Base da API do Veska. | | VESKA_TOKEN | — | Token Bearer (gerado no app/CLI). |

Uso com Claude Desktop / .mcp.json

Adicione ao .mcp.json (Claude Code) ou ao claude_desktop_config.json:

{
  "mcpServers": {
    "veska": {
      "command": "npx",
      "args": ["-y", "@veska/mcp"],
      "env": {
        "VESKA_TOKEN": "seu-token-aqui",
        "VESKA_API_URL": "https://api.veska.ai/api"
      }
    }
  }
}

O binário publicado é veska-mcp (bin). Em desenvolvimento local, após o build, é possível apontar command para node e args para ["/caminho/para/packages/mcp/dist/index.js"].

Desenvolvimento

pnpm --filter @veska/mcp build      # compila para dist/ (entrypoint executável)
pnpm --filter @veska/mcp typecheck  # checagem de tipos (strict)
pnpm --filter @veska/mcp lint       # eslint

Stack: TypeScript strict, ESM, @modelcontextprotocol/sdk (stdio), zod para validação de input. Cliente HTTP próprio com fetch nativo (Node 20+).