Update Hijack Demo

io.github.NOTTIBOY137Published by GitHub account NOTTIBOY137v1.0.1Updated Oct 24, 2026

Demo: Server update hijack PoC (clean copy for video)

The publisher's own server: demo.st

VerifiedSTDIODesktop onlySecurity & Monitoring

Overview

AI-generated overview

A local demo MCP server presented as a proof of concept for a server update hijack, with no documented tools or usage.

What you can do
The registry entry describes it only as a demo and proof of concept for a server update hijack, prepared as a clean copy for a video. No tools are listed, and there are no instructions or README, so what an assistant could actually do with it is undocumented. It runs as a local process over stdio.
When to use it
Only if you are studying or demonstrating update-hijack risks in MCP server distribution and want the author's demo package. It is not intended for general assistant use, since no capabilities are described.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package. Desktop only; no web execution. No authentication, environment variables or headers are declared.
Before you install
The name and description point to an update hijack proof of concept, so treat the package as untrusted demonstration code rather than a tool for real work. No tools, permissions or data handling are documented, so review the package contents before running it on a machine with anything sensitive.

Installation

In SourceWeft

  1. Open Update Hijack Demo 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.

Other Demo integrations