Phare

io.pharePublished by phare.ioOfficial publisherv1.1.0Updated Nov 7, 2026

Manage the uptime monitoring, incidents and status pages of your Phare organization.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server that lets an assistant manage the uptime monitoring, incidents and status pages of a Phare organization.

What you can do
  • Manage uptime monitoring for a Phare organization.
  • Work with incidents recorded by the monitoring service.
  • Manage status pages that report service health.
  • No tool list is published, so the exact actions available are not documented here.
When to use it
Useful when you already run uptime checks and status pages in Phare and want an assistant to help manage monitors, incidents or status pages from a conversation instead of the Phare interface.
Requirements
A remote endpoint at mcp.phare.io using streamable HTTP. Authentication is OAuth and required, so you need a Phare account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
The server can change monitoring configuration, incidents and status pages in your organization, so review actions before they are applied. Access is granted through OAuth to your Phare account, so connect only with an account whose permissions you are comfortable delegating. No tool list is published, so the exact scope of write access is unclear.

Installation

In SourceWeft

  1. Open Phare in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.phare%2Fphare/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "phare": {
      "type": "http",
      "url": "https://mcp.phare.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestNov 7, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.