mcp-security-sandbox

Created By
SirAppSeca year ago
MCP Security Playground - Hack with MCP Servers, MCP Clients. Try out different vulnerabilities and abuse LLMs and agents in a UI friendly experimentation lab
Overview

what is mcp-security-sandbox?

The mcp-security-sandbox is an experimental environment designed for exploring mcp hosts, clients, and servers. It allows users to perform attacks against mcp servers and experiment with large language models (LLMs).

how to use mcp-security-sandbox?

To use the mcp-security-sandbox, set up a virtual environment, install the necessary dependencies, and run the MCP server and frontend applications using the provided commands.

key features of mcp-security-sandbox?

  • Experimental sandbox for mcp hosts and clients
  • Ability to perform attacks against mcp servers
  • Integration with local LLMs for enhanced functionality

use cases of mcp-security-sandbox?

  1. Testing the security of mcp servers through simulated attacks.
  2. Exploring the capabilities of LLMs in a controlled environment.
  3. Developing and testing new features for mcp applications.

FAQ from mcp-security-sandbox?

  • What is the purpose of the mcp-security-sandbox?

It serves as a lab for security researchers to explore and test mcp technologies and LLMs.

  • Is there a specific setup required?

Yes, users need to install dependencies and set up the environment as per the instructions provided in the documentation.

  • Can I use this sandbox for production purposes?

No, this is an experimental sandbox and should not be used in production environments.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
SirAppSec
Star
1
Language
Python
License
MIT license
Category
security

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago