mcp -npm-goof

This MCP server exposes a single tool named getNpmPackageInfo. It runs as an HTTP MCP service and responds with structured information about a requested npm package. To use it, define the MCP server in your agent configuration so your MCP client can reach the HTTP endpoint where the server is listening (default port 3000, or a port you specify via PORT). The server is designed to work with IDE integrations and AI agents that understand MCP over HTTP, enabling you to fetch package metadata by name using the getNpmPackageInfo tool. Call the tool by providing the packageName parameter, and you will receive a packageInfo object with available details about the requested npm package.

Prerequisites:

• Node.js (LTS version) and npm installed

1. Clone or download the repository for the MCP server (npm-goof).
2. Install dependencies: npm install
3. Start the server: npm start By default the server will listen on port 3000. To run on a different port, set the PORT environment variable, e.g.: PORT=3500 npm start
4. Verify it's running by hitting the MCP endpoint (e.g., http://localhost:3000/mcp) or the configured port and using an MCP client to request getNpmPackageInfo for a package name.

Notes and tips:

• This server is labeled as educational and intentionally vulnerable to help with MCP security practice. Do not expose it to untrusted networks without proper hardening.
• The getNpmPackageInfo tool returns a packageInfo object containing information about the requested npm package when available. Ensure your MCP client supplies a valid packageName string.
• If you run into CORS or network issues, verify that the port configured by PORT is accessible from the client and that the MCP transport is HTTP as expected by your agent.
• You can customize the port using the PORT environment variable when starting the server, e.g., PORT=3500 npm start.
• In your MCP client configuration, reference the server name you defined (here npm-and-node-tools) to route requests to this MCP server.