NPMJS Model Context Protocol (MCP) Server

Created By
yiannis-spyridakisa year ago
Overview

What is NPMJS Model Context Protocol (MCP) Server?

The NPMJS MCP Server is a lightweight, TypeScript-based server designed to provide structured information about npmjs packages in a standardized JSON format, making it easier for AI-driven development tools to access npm package metadata.

How to use NPMJS MCP Server?

To use the MCP Server, clone the repository, install dependencies, and run the server in either development or production mode using npm commands. You can then call various tools provided by the server to retrieve package information.

Key features of NPMJS MCP Server?

  • Provides essential npm package details such as version, download statistics, and licenses.
  • Simplifies access to npm package metadata by abstracting multiple API endpoints.
  • Supports various tools for fetching package summaries, versions, downloads, and detailed information.

Use cases of NPMJS MCP Server?

  1. Accessing metadata for npm packages in AI applications.
  2. Integrating npm package information into development tools.
  3. Analyzing package download statistics for performance insights.

FAQ from NPMJS MCP Server?

  • What is the purpose of the MCP Server?

The MCP Server aims to provide a simplified interface for accessing npm package metadata.

  • How do I run the server?

You can run the server by following the setup instructions provided in the documentation, using npm commands.

  • What tools are available in the MCP Server?

The server includes tools for getting package summaries, versions, downloads, and detailed information.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yiannis-spyridakis
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 days ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Payai X402 Tools

16 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago