1. Conduid
  2. Developer Tools
  3. MasterMCP
MCP server · Developer Tools

MasterMCP

by · github.com/HC010602/MasterMCP

A demonstration toolkit revealing potential security vulnerabilities in MCP (Model Context Protocol) frameworks through data poisoning, JSON injection, function overriding, and cross-MCP call attacks, exposing AI security issues while providing defense recommendations. For educational and research purposes only.

Unclaimed last commit a year ago devtools
InstallView source
44Fair

Scored 14 days ago · breakdown

About MasterMCP

MasterMCP is an MCP server published by HC010602 in the Developer Tools category: a demonstration toolkit revealing potential security vulnerabilities in MCP (Model Context Protocol) frameworks through data poisoning, JSON injection, function overriding, and cross-MCP call attacks, exposing AI security issues while providing defense recommendations. For educational and research purposes only.

Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/HC010602/MasterMCP

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about MasterMCP

Powered by Claude · Grounded in docs

I know everything about MasterMCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About MasterMCP

How do I install MasterMCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is MasterMCP safe to use with an AI agent?

Its trust score is 44 out of 100 (fair). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is MasterMCP still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.