Custom Mcp Server

io.github.yuv24793Published by GitHub account yuv24793v1.0.1Updated Oct 25, 2026

An MCP server that provides custom functionality.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A locally run MCP server, distributed as an npm package, that its author describes only as providing custom functionality.

What you can do
The registry entry gives no tool list, instructions or README, so the specific capabilities cannot be determined from the available information. The only stated purpose is that it provides custom functionality to an assistant. It runs as a local process over stdio on the user's machine. To learn what it actually does, inspect the package source before relying on it.
When to use it
Only worth considering if you already know the author and want to evaluate a small custom local MCP server. It is not a good choice when you need documented, predictable tools, since nothing about its behavior is published.
Requirements
Node.js and an npm-based MCP client that can launch a local stdio process. The manifest declares no authentication, environment variables or headers, so no credentials are requested. Desktop client only; it is not offered as a web-executable server.
Before you install
The purpose, tools and behavior are undocumented, so you cannot tell what data it reads, sends or changes before installing. Review the package source and its dependencies first, and treat any local process with the same care as other third-party code you run on your machine.

Installation

In SourceWeft

  1. Open Custom Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.