Tool Filter MCP

io.github.respawn-appPublished by GitHub account respawn-appv0.4.2Updated Oct 24, 2026

MCP proxy server that filters tools from upstream MCP servers via regex-based deny list

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.respawn-app/tool-filter-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account respawn-app for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.respawn-app%2Ftool-filter-mcp.svg)](https://sourceweft.com/mcp/io.github.respawn-app%2Ftool-filter-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP proxy that sits in front of upstream MCP servers and hides their tools using a regex-based deny list.

What you can do: Acts as a proxy between the assistant and upstream MCP servers, forwarding their tools through a single connection. Filters out tools from those upstream servers according to a regex-based deny list, so blocked tools are not exposed to the assistant. Runs as a local process over stdio.
When to use it: Useful when an upstream MCP server exposes more tools than you want an assistant to see, and you want to trim that set by name pattern without changing the upstream server itself.
Requirements: Runs as a local process on the user's machine, installed from the npm package @respawn-app/tool-filter-mcp over stdio. Desktop client only; no authentication, environment variables or headers are declared. Upstream MCP servers must be configured for it to proxy.

Before you install

It only hides tools by pattern; anything not matched by the deny list still reaches the assistant, so a loose regex leaves tools exposed. Review the deny patterns carefully, since filtering is the only control it provides.

Installation

In SourceWeft

Open Tool Filter MCP in the dashboard and add it to a workspace.
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.

Tools

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

Version history

v0.4.2LatestSep 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.