Globalping

Created By
jsdelivra year ago
Gives any LLM the tools to run network commands like ping, traceroute, mtr, HTTP and DNS resolve from any location in the world.
Overview

Globalping MCP

The Globalping MCP server is the official server of the Globalping platform that gives users, developers and LLMs access to run network tools like ping and dns resolve from thousands of probes around the world.

How to use

The Globalping remote MCP server supports oAuth authentication with a simple and straight forward flow.

Simply add the config to your preferred MCP client and follow the steps in the browser.

Key features

🌐 Global Network Access: Run measurements from thousands of probes worldwide

🤖 AI-Friendly Interface: Any LLM will easily parse the data and run new measurements as needed

📊 Comprehensive Measurements: Support for ping, traceroute, DNS, MTR, and HTTP tests

🔍 Smart Context Handling: Provides detailed parameter descriptions for AI clients to intelligently select measurement types and options

🔄 Comparative Analysis: Allows to compare network performance between different targets

🔑 oAuth Support: Use your own Globalping account for higher rate limits

Server Config

{
  "mcpServers": {
    "globalping": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.globalping.dev/sse"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jsdelivr
Star
-
Language
-
License
-
Category

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