Pingdom Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.1Updated Oct 28, 2026

Measure site performance and catch broken links - no API key.

VerifiedSTDIODesktop onlyWeb Search & Scraping Developer Tools

Server details

Identifier: io.github.mrfentmen/pingdom-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 23, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mrfentmen for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mrfentmen%2Fpingdom-mcp.svg)](https://sourceweft.com/mcp/io.github.mrfentmen%2Fpingdom-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant measure website performance and detect broken links, reportedly without an API key.

What you can do: Measure site performance for a given web page or site.
Check pages for broken links.
The manifest lists no individual tools, so the exact commands and output format are not documented in the supplied material.
When to use it: Useful when you want an assistant to quickly check how fast a site loads or to sweep a page for dead links during development or content review, without setting up a monitoring account.
Requirements: Runs as a local process over stdio, installed from the npm package pingdom-mcp, so Node.js and npm are needed on the machine. Desktop-only; no web execution. No environment variables, headers or authentication are declared.

Before you install

The server contacts the target websites on your behalf, so the URLs you give it are sent to those third parties. Despite the Pingdom name, no credentials are declared, so it is unclear whether it uses a public endpoint or an unofficial route; verify behavior before relying on results. It is a local process with network access, so review the package before installing.

Installation

In SourceWeft

Open Pingdom Mcp in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.0.1LatestOct 17, 2026
v1.0.0Sep 23, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.