Mcpsentry

io.github.Roshan6335Published by GitHub account Roshan6335v0.1.4Updated Oct 24, 2026

Security scanner and runtime proxy for MCP servers.

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local security scanner and runtime proxy for MCP servers, run as a desktop-only process on the user's machine.

What you can do
The listing gives no tool list, so capabilities come from the one-line description only. It is described as a security scanner for MCP servers, suggesting it inspects server configurations or packages for risk. It is also described as a runtime proxy, suggesting it can sit between an assistant and other MCP servers and mediate their traffic. No further detail on scanning rules, proxied protocols or reporting is provided.
When to use it
Consider it if you want to vet MCP servers before or while using them, or route assistant-to-server traffic through a local intermediary for inspection. Because no tools or documentation are published, confirm its actual behavior before relying on it.
Requirements
Runs as a local process on the user's machine via the npm package @roshan6335/mcpsentry over stdio. Desktop only; not available as a web executable. No authentication, environment variables or headers are declared.
Before you install
As a runtime proxy it may see traffic between your assistant and other MCP servers, which can include sensitive data. No tools, README or instructions are published, so its scanning coverage and data handling cannot be verified from this listing; review the package before installing.

Installation

In SourceWeft

  1. Open Mcpsentry 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.

Tools

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

Version history

1
  1. v0.1.4LatestSep 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.