An astronaut overseeing a futuristic data hub

Connect NPM Registry to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Pull real-time JavaScript dependency data directly into your workflow.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 4 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-04

4 capabilities in this set.

Part of 4 available through NPM Registry.

  1. 01

    Get package version

    Retrieves detailed metadata for a specific version of an NPM package.

  2. 02

    Search packages

    Searches the registry using qualifiers like author, maintainer, keywords, or stability status.

  3. 03

    Get package

    Fetches the general metadata for any NPM package by name.

  4. 04

    Get registry meta

    Provides status and scale information about the NPM registry instance itself.

Real work

What teams actually run

01

Dependency Debugging

Your agent identifies why a specific version of a library is required by inspecting package metadata.

02

Library Vetting

You ask your agent to find packages with specific keywords or maintainers to find reliable capabilities.

03

Pipeline Troubleshooting

The agent checks if a package version exists to resolve deployment failures.

04

Security Audits

You use the agent to check the metadata of a package to evaluate its maintenance status.

Automate a task

Put NPM Registry to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

NPM Registry works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put NPM Registry to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

975ms average. Fast in production.

NPM Registry is checked daily against the live service.

Daily averagePeak 1145ms
Oct 3Today
Fastest day
720ms
Slowest day
1145ms
14-day trend
Slowing+40%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 4 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of NPM Registry, so you can see the experience inside your AI.

It does not authenticate your account with NPM Registry. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

NPM Registry Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_otpZ68Nu8EhWCNWBS61r97Vlz9kXy1MwTNZ2GMP2/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — NPM Registry capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "npm-registry-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_otpZ68Nu8EhWCNWBS61r97Vlz9kXy1MwTNZ2GMP2/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up NPM Registry in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work NPM Registry owners hand off.

This MCP is built for developers who need instant access to package data without leaving their coding environment.

  • 01

    Software Engineers

    They use the agent to check dependencies and versions during active development.

  • 02

    DevOps Engineers

    They use it to verify package availability and history when debugging CI/CD pipelines.

  • 03

    Security Researchers

    They use it to inspect package metadata and maintenance scores for library health.

FAQ

Questions NPM Registry owners ask.

  • 01

    Do I need an NPM account to use this MCP?

    Public queries work without an account, but providing a Read-Only Token is recommended to prevent rate limiting.

  • 02

    Which AI clients can use this MCP?

    You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

  • 03

    Can I search for packages by author?

    Yes, the search capability supports qualifiers like author:name and maintainer:name.

  • 04

    How does Vinkius handle the connection?

    Vinkius hosts the MCP and manages the connection, so you only need to connect your client once.

  • 05

    Can I check specific versions of a library?

    Yes, the get_package_version capability allows you to retrieve metadata for any specific version.

  • 06

    Can I check the latest version of a package and its dependencies?

    Yes! Use the get_package_version capability with the version set to 'latest'. It will return the full metadata including dependencies, scripts, and engine requirements for that specific release.

  • 07

    How do I search for packages by a specific author or keyword?

    You can use the search_packages capability. It supports qualifiers in the text field like 'author:name' or 'keywords:word', and allows you to weight results by quality, popularity, or maintenance.

  • 08

    Is it possible to get a faster, smaller response for package metadata?

    Yes, when using the get_package capability, you can set the abbreviated parameter to true. This requests a 'packument' with less data, which is ideal for quick version checks or faster response times.

Connect NPM Registry to Claude, Cursor, ChatGPT & more