Phare (BYOK)

Phare (BYOK) — connector documentation

• MCP endpoint: https://byok-phare.connectorbay.com/mcp
• REST API: POST https://byok-phare.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-phare.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Phare project-scoped API key with read access (organization-scoped keys also need a project header, which this connector does not send), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-phare.connectorbay.com/health · Tool schemas: https://byok-phare.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-phare · agent@connectorbay.com

What Phare (BYOK) is for

Phare (BYOK) lets an AI assistant read your own Phare data through the Phare API with a key you supply (project-scoped API key with read access (organization-scoped keys also need a project header, which this connector does not send)). Read-only: 10 tools (list_monitors, get_monitor, get_monitor_report, get_project_report, list_incidents, list_incident_updates, list_maintenance_windows, list_status_pages, get_status_page_current_status, list_alert_rules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.phare.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Phare. Phare and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which of my Phare monitors are offline right now?"
• "Show the settings of Phare monitor 12"
• "What was the uptime of Phare monitor 12 over the last 30 days?"
• "What was my overall availability across all Phare monitors this month?"
• "Which incidents did my Phare monitors have recently?"
• "What updates were posted on Phare incident 5?"

What it does

• list_monitors: List the uptime monitors of the project with status, protocol, check interval, timeout, regions, tags and last check time.
• get_monitor: Get one monitor's full configuration and current status, including request settings and success assertions.
• get_monitor_report: Uptime statistics for one monitor over a time window: availability, downtime, MTTR, MTBF and the incidents in that window.
• get_project_report: Aggregated uptime statistics for all monitors of the project over a time window, with a per-monitor breakdown.
• list_incidents: List incidents (automatic and manual) with impact, state, status, start and recovery time, optionally for one monitor or tag.
• list_incident_updates: List the published updates of one incident (state, text and publish time), oldest first as returned by the API.
• list_maintenance_windows: List maintenance windows with state, monitoring mode, schedule and the monitors and status pages they cover.
• list_status_pages: List the project's status pages with name, subdomain, custom domain, privacy flag, timeframe and tags.
• get_status_page_current_status: Current status of one status page: overall impact, availability, component states and active incidents.
• list_alert_rules: List alert rules: which event triggers which integration, with rate limit settings.

BYOK key

You bring your own Phare project-scoped API key with read access (organization-scoped keys also need a project header, which this connector does not send) (https://app.phare.io). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.phare.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.phare.io/api-reference/introduction (the API this connector calls, with a BYOK key)

Live from the Phare API (api.phare.io) with a BYOK key; documentation: https://docs.phare.io/api-reference/introduction. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Phare. Phare and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Phare account.

Built for: Worldwide. Languages: English.

Phare (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Phare (BYOK) is. Phare (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Phare data: Read your Phare uptime monitors, incidents, maintenance windows, status pages and uptime reports with your own project API key. You bring your own Phare project-scoped API key with read access (organization-scoped keys also need a project header, which this connector does not send); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Phare call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.phare.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Phare rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Phare receives. The request we make on your behalf, including the key and the arguments, under Phare's own terms and privacy policy. Phare acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Phare gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Phare data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Phare (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Phare at any time to end all access.

Children. Phare (BYOK) is a general-audience service operated by the adult using the assistant, under Phare's own age rules.

Changes. We will post changes here with a new effective date.

Phare (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Phare (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Phare (BYOK) provides: Read your Phare uptime monitors, incidents, maintenance windows, status pages and uptime reports with your own project API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Phare credentials and only access data you are allowed to access. Phare's terms apply to your use of Phare; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Phare. Phare and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Phare returns, lightly trimmed; it may be incomplete, delayed or changed by Phare. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Phare account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Phare's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Phare may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Phare key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Phare takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-phare

Phare (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-phare.connectorbay.com/mcp
• REST API: https://byok-phare.connectorbay.com/openapi.json
• Live status: https://byok-phare.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Phare (BYOK) never asks for them.