Skip to content

Fix #318: Add ToolPipe MCP Server - 145+ Developer Tools for AI Agents #321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
JiwaniZakir wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix #318: Add ToolPipe MCP Server - 145+ Developer Tools for AI Agents #321

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
35 changes: 35 additions & 0 deletions mcp-registry/servers/toolpipe.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
{
"name": "toolpipe",
"display_name": "ToolPipe",
"description": "145+ developer utility tools for AI agents via a single MCP connection, including code review, fake data generation, JSON Schema validation, security headers checking, API client generation, OpenAPI spec generation, CSV analysis, code minification, code formatting, QR codes, hashing, UUID, DNS lookup, regex testing, JWT decode, SQL formatting, XML/YAML conversion, text summarization, and more.",
"repository": {
"type": "git",
"url": "https://github.com/COSAI-Labs/make-money-30day-challenge"
},
Comment on lines +5 to +8

@coderabbitai coderabbitai Bot Apr 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify npm package exists and check its repository field

echo "=== Checking npm package metadata ==="
npm view `@cosai-labs/toolpipe-mcp-server` repository.url repository.type homepage version

echo -e "\n=== Checking if package exists and is installable ==="
npm view `@cosai-labs/toolpipe-mcp-server` name

Repository: pathintegral-institute/mcpm.sh

Length of output: 1081

🌐 Web query:

@cosai-labs/toolpipe-mcp-server npm package repository GitHub

💡 Result:

The GitHub repository for the @cosai-labs/toolpipe-mcp-server npm package is https://github.com/COSAI-Labs/toolpipe-mcp-server. It is an MCP (Model Context Protocol) server providing 35+ developer utility APIs (e.g., JSON formatting, QR code generation, hashing, UUID, DNS lookup, etc.) accessible to AI agents like Claude, Cursor, VS Code, and Windsurf. The package is installed via npx @toolpipe/mcp-server (note: the npm scoped name in docs is @toolpipe/mcp-server, while the query and GitHub suggest @cosai-labs/toolpipe-mcp-server; likely related or aliased). Created April 3, 2026. Requires Node.js 18+. Free tier: 100 API calls/day; Pro: 10k/day for $9.99/mo via https://toolpipe.dev.

Citations:

Update repository URL to point to the toolpipe-mcp-server repository.

The URL currently points to "make-money-30day-challenge" but should reference the actual toolpipe-mcp-server source code at https://github.com/COSAI-Labs/toolpipe-mcp-server.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@mcp-registry/servers/toolpipe.json` around lines 5 - 8, Update the repository
URL value inside the "repository" JSON object: locate the "repository" block
(the "type" and "url" fields) and replace the current
"https://github.com/COSAI-Labs/make-money-30day-challenge" string with
"https://github.com/COSAI-Labs/toolpipe-mcp-server" so the "url" field points to
the correct toolpipe-mcp-server repository.

"homepage": "https://www.npmjs.com/package/@cosai-labs/toolpipe-mcp-server",
Comment on lines +5 to +9

@qodo-code-review qodo-code-review Bot Apr 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Wrong repository url 🐞 Bug ≡ Correctness

The ToolPipe manifest’s repository.url points to COSAI-Labs/make-money-30day-challenge, which is
inconsistent with the ToolPipe npm package homepage and will cause the registry to show and fetch
GitHub metadata (e.g., stars/link) for the wrong project.
Agent Prompt 
## Issue description
`mcp-registry/servers/toolpipe.json` sets `repository.url` to `https://github.com/COSAI-Labs/make-money-30day-challenge`, while the manifest otherwise identifies the server as the npm package `@cosai-labs/toolpipe-mcp-server`. This inconsistency will cause registry consumers to display and fetch GitHub metadata (e.g., stars/link) for the wrong project.

## Issue Context
The registry build script extracts GitHub repository URLs from `manifest.repository.url` and uses them to fetch GitHub metadata.

## Fix Focus Areas
- mcp-registry/servers/toolpipe.json[5-9]
- scripts/prepare.py[79-100]
- scripts/prepare.py[119-127]

## Expected fix
Update `repository.url` to the actual GitHub repository for the ToolPipe MCP server (the repo that corresponds to `@cosai-labs/toolpipe-mcp-server`). If the code truly lives in a monorepo, ensure the URL points to the correct repo/path that represents this server (and ideally align `homepage` accordingly).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

"author": {
"name": "COSAI-Labs"
},
"license": "MIT",
"categories": [
"Dev Tools"
],
"tags": [
"developer-tools",
"code-review",
"security",
"devops",
"data-generation",
"api-development",
"text-processing",
"conversion"
],
"installations": {
"npm": {
"type": "npm",
"command": "npx",
"args": ["-y", "@cosai-labs/toolpipe-mcp-server"]
}
},
"is_official": false
}
Loading