Globalping MCP Server

Created By
jsdelivra year ago
Remote MCP server that gives LLMs access to run network commands
Overview

What is Globalping MCP Server?

Globalping MCP Server is a remote server that enables AI models to access and run network commands through natural language, leveraging the Model Context Protocol (MCP). It connects AI models like OpenAI's GPT and Anthropic's Claude to a global network measurement platform.

How to use Globalping MCP Server?

To use the Globalping MCP Server, integrate it with any MCP-compatible AI tool by configuring the server endpoint https://mcp.globalping.dev/sse in the tool's settings. You can then issue commands in natural language to perform network tests.

Key features of Globalping MCP Server?

  • 🌐 Global Network Access: Run measurements from thousands of probes worldwide.
  • 🤖 AI-Friendly Interface: Easily parse data and run measurements using any LLM.
  • 📊 Comprehensive Measurements: Support for ping, traceroute, DNS, MTR, and HTTP tests.
  • 🔍 Smart Context Handling: Detailed parameter descriptions for intelligent measurement selection.
  • 🔄 Comparative Analysis: Compare network performance between different targets.
  • 🔑 oAuth Support: Higher rate limits with your Globalping account.

Use cases of Globalping MCP Server?

  1. Running network tests from various global locations.
  2. Comparing network performance across different regions.
  3. Debugging internet infrastructure issues using AI.

FAQ from Globalping MCP Server?

  • Can I use Globalping MCP Server with any AI model?

Yes! It is compatible with any MCP-compliant AI assistant.

  • Is there a cost to use Globalping MCP Server?

No, it is free to use for everyone.

  • What types of network tests can I perform?

You can perform ping, traceroute, DNS lookups, MTR tests, and HTTP requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jsdelivr
Star
4
Language
TypeScript
License
-

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