Probe MCP

Created By
abcClover10 months ago
A diagnostic MCP server for probing and validating client connections.
Overview

A diagnostic MCP server for probing and validating client connections.

Probe is a public utility designed for developers and security researchers working within the MCP ecosystem. Its purpose is to help you inspect your AI assistant's communication stack, identify connection proxies like mcp-remote, and verify that your configuration is transparent and secure.

When your client connects, Probe passively analyzes the handshake and provides an interactive tool to actively query your connection's properties.

Core Function

The server offers a single, powerful tool: get_proxy_info. When called, this tool performs a security check on your connection and returns a detailed report, including the version of any detected mcp-remote proxy.

How to Use

To use Probe, add it as an MCP server in your AI assistant's configuration file (e.g., ~/.cursor/mcp.json).

Server Config

{
  "mcpServers": {
    "Probe": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://tencent.yumeeu.com:5000/sse",
        "--allow-http"
      ]
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
abcClover
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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