Skip to content

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

Open
JiwaniZakir wants to merge 1 commit intopathintegral-institute:mainfrom
JiwaniZakir:fix/318-add-toolpipe-mcp-server-145-developer-to
Open

Fix #318: Add ToolPipe MCP Server - 145+ Developer Tools for AI Agents#321
JiwaniZakir wants to merge 1 commit intopathintegral-institute:mainfrom
JiwaniZakir:fix/318-add-toolpipe-mcp-server-145-developer-to

Conversation

@JiwaniZakir
Copy link
Copy Markdown

@JiwaniZakir JiwaniZakir commented Apr 17, 2026

Closes #318

Adds mcp-registry/servers/toolpipe.json to register the ToolPipe MCP server in the registry.

Changes

  • mcp-registry/servers/toolpipe.json (new file, 35 lines): Registry entry defining the ToolPipe server with:
    • name: "toolpipe", display_name: "ToolPipe"
    • repository.url pointing to https://github.com/COSAI-Labs/make-money-30day-challenge
    • homepage set to the npm package page (@cosai-labs/toolpipe-mcp-server)
    • categories: ["Dev Tools"]
    • 8 tags: developer-tools, code-review, security, devops, data-generation, api-development, text-processing, conversion
    • installations.npm: npx -y @cosai-labs/toolpipe-mcp-server
    • is_official: false

Motivation

ToolPipe exposes 145+ developer utility tools (code review, JSON Schema validation, OpenAPI/API client generation, CSV analysis, JWT decode, SQL formatting, QR codes, UUID, DNS lookup, regex testing, SSL/WHOIS checking, Docker Compose and GitHub Actions generation, and more) through a single MCP connection. Adding it to the registry makes it discoverable to AI agent developers looking for a broad-coverage utility server without managing multiple MCP integrations.

Testing

  • JSON file validates against the registry schema (no required fields missing: name, display_name, description, repository, license, installations).
  • npx -y @cosai-labs/toolpipe-mcp-server resolves and launches the server against the published npm package.
  • MCP connection confirmed reachable at the npm-installed server endpoint; tool list returns 145+ entries matching the described categories.

This PR was created with AI assistance (Claude). The changes were reviewed by quality gates and a critic model before submission.

Summary by CodeRabbit

  • New Features
    • Added the "toolpipe" server to the registry, offering a comprehensive suite of developer utilities to enhance and streamline development workflows. This new server is now available for installation via npm, providing developers with additional tools for improved productivity.

Copilot AI review requested due to automatic review settings April 17, 2026 09:56
@qodo-code-review
Copy link
Copy Markdown
Contributor

Review Summary by Qodo

Register ToolPipe MCP server with 145+ developer tools

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Registers ToolPipe MCP server with 145+ developer utility tools
• Provides comprehensive toolset for code review, API generation, security checks
• Enables single MCP connection for multiple development utilities
• Installable via npm with straightforward command
Diagram
flowchart LR
  Registry["MCP Registry"]
  ToolPipe["ToolPipe Server<br/>145+ Dev Tools"]
  NPM["NPM Package<br/>@cosai-labs/toolpipe-mcp-server"]
  Registry -- "registers" --> ToolPipe
  ToolPipe -- "installs from" --> NPM
Loading

Grey Divider

File Changes

1. mcp-registry/servers/toolpipe.json ✨ Enhancement +35/-0

Add ToolPipe MCP server registry entry

• New registry entry for ToolPipe MCP server with complete metadata
• Defines 145+ developer utility tools across 8 semantic tags
• Specifies npm installation command and MIT license
• Links to GitHub repository and npm package homepage

mcp-registry/servers/toolpipe.json


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown
Contributor

qodo-code-review Bot commented Apr 17, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Action required

1. Wrong repository URL 🐞 Bug ≡ Correctness
Description
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.
Code

mcp-registry/servers/toolpipe.json[R5-9]

+  "repository": {
+    "type": "git",
+    "url": "https://github.com/COSAI-Labs/make-money-30day-challenge"
+  },
+  "homepage": "https://www.npmjs.com/package/@cosai-labs/toolpipe-mcp-server",
Evidence
The new manifest links to a GitHub repo whose name does not match the ToolPipe MCP server
package/homepage, and the registry build tooling explicitly consumes repository.url when it is a
GitHub URL. As a result, the generated registry metadata (and any UI built from it) will attribute
ToolPipe to the wrong GitHub repository.

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

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## 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


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 17, 2026

📝 Walkthrough

Walkthrough

A new manifest file for the "toolpipe" MCP server has been added to the registry, defining metadata including name, description, repository details, author information, installation via npm, and official status flag.

Changes

Cohort / File(s) Summary
Registry Manifest
mcp-registry/servers/toolpipe.json
Added new server manifest defining toolpipe with display name, description of developer utilities, repository/homepage URLs, MIT license, category/tags, npm installation command via npx -y @cosai-labs/toolpipe-mcp-server``, and is_official: false flag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related issues

Suggested labels

Review effort 2/5, Possible security concern

Suggested reviewers

  • calmini

Poem

🐰 A new tool hops into the registry today,
Toolpipe arrives in its JSON way,
With metadata complete from cosai's nest,
The server bundle joins all the rest! 🛠️✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly describes the main change: adding a ToolPipe MCP server registry entry with 145+ developer tools, which matches the PR's core objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds the ToolPipe MCP server to the registry to make it discoverable and installable by MCP clients/tools via the standard manifest format.

Changes:

  • Introduces a new server manifest for toolpipe with metadata (name, description, repository, homepage, tags/categories).
  • Defines an npm-based installation method using npx -y @cosai-labs/toolpipe-mcp-server.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +5 to +9
"repository": {
"type": "git",
"url": "https://github.com/COSAI-Labs/make-money-30day-challenge"
},
"homepage": "https://www.npmjs.com/package/@cosai-labs/toolpipe-mcp-server",
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

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@mcp-registry/servers/toolpipe.json`:
- Around line 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.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 443d1db0-e4d1-4a04-ac91-ca7a021e19e2

📥 Commits

Reviewing files that changed from the base of the PR and between bdd5ed9 and 4d9f4b6.

📒 Files selected for processing (1)
  • mcp-registry/servers/toolpipe.json

Comment on lines +5 to +8
"repository": {
"type": "git",
"url": "https://github.com/COSAI-Labs/make-money-30day-challenge"
},
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants