Probecast

io.probecastPublished by probecast.iov0.2.0Updated Oct 30, 2026

Your coding agent adds Probecast uptime monitors and reads incidents for projects you ship.

VerifiedSTDIODesktop onlyDeveloper Tools Security & Monitoring

Server details

Identifier: io.probecast/mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Oct 29, 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 that this server's namespace belongs to probecast.io. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

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.probecast%2Fmcp.svg)](https://sourceweft.com/mcp/io.probecast%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Probecast lets a coding agent check live status of public remote MCP servers and, with an API key, manage uptime monitors and incidents for shipped projects.

What you can do: Check whether a public remote MCP server (GitHub, Stripe, Sentry, Linear, Context7 and others) is down, for one server by name or slug or for all of them
See live status gathered with a real MCP handshake from four regions
Add uptime monitors and read incidents for projects you ship, once an API key is configured
Diagnose whether a failing MCP server is down or the local setup is at fault
When to use it: Useful when another MCP server stops responding and you need to tell an outage from a local configuration problem, or when you want your agent to set up uptime monitoring and review incidents for projects you run.
Requirements: Runs as a local stdio process installed from the npm package, so Node.js is needed. The PROBECAST_API_KEY environment variable is optional: without it only the public status check is available; with it, monitor and incident features are enabled. A Probecast account is needed to create a key.

Before you install

The PROBECAST_API_KEY is a secret that grants access to your Probecast account; keep it out of logs and shared configs. With a key configured, the server can add monitors and read incident data, which changes state in your Probecast account. Status checks query third-party public MCP servers.

Installation

In SourceWeft

Open Probecast 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.

Tools

check_mcp_status

Is a public MCP server down, or is it the local setup? Returns Probecast's live status for public remote MCP servers (GitHub, Stripe, Sentry, Linear, Context7…), checked with a real MCP handshake from 4 regions. Pass server (name or slug, e.g. "github") to check one; omit it to list all. Works without an API key.

Parametersserver

Version history

v0.2.0LatestOct 29, 2026

Score

65% 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
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 listedRequired15 pts
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.