Uptimeify

Your agent calls check_ssl, you open the SSL Certificate Checker. Same probe, same endpoint, two front doors, so a result from the chat is one you can reproduce in the browser and put in front of a client. TLS & domains DNS & mail HTTP & network Browse all free tools

This is how it is wired. Learn more about API tokens Static token The authenticated tools accept a long-lived API token on the MCP request. Authorization: Bearer wsm_your_token_here OAuth Or your client logs in over OAuth 2.0 with PKCE and never holds a stored secret. It finds the flow through the server card, registers itself at the registration endpoint and runs the authorization-code grant. A bearer the server cannot resolve comes back as a 401 carrying a WWW-Authenticate header that points at the protected-resource metadata, so the client restarts the login on its own. GET](https://uptimeify.io/.well-known/mcp/server-card.json)[https://uptimeify.io/.well-known/oauth-protected-resourceScope organization customer an API token is scoped when you create it, customer field empty for the whole organization, or one customer to bind it there. OAuth scope An OAuth session is forced read-only and carries what that user may see in Uptimeify right now. The binding is re-resolved when the session mints its short-lived inner token, not frozen at login, so access you revoke in the dashboard stops working instead of living on in a stale grant. Creation You create tokens under Settings, API tokens. The token is shown exactly once, at creation. Arguments check_history takes monitor_id plus optional from and to as ISO dates. list_incidents takes an optional limit, 100 by default and 500 at most. Unauthenticated No header at all stays fully anonymous. The anonymous tools answer as usual and an authenticated tool returns an error naming the header it needs, rather than an empty result. There is no forced 401 on every request. Portfolio Layer

Anyone can check a domain. Send an API token and your agent stops looking only at the public internet and starts reading your own monitoring. Or let the client log in over OAuth and skip the token entirely. List monitors, pull the status of a single monitor, fetch recent incidents, read check history for a date range, summarize uptime and average response time for day, month and year. The client report starts in the chat, not in the spreadsheet.

- list_monitorsandmonitor_status, so one sentence tells you what is up and what is not.
- list_incidentsandcheck_history, so you can reconstruct an incident without clicking through views.
- uptime_summary, so availability and response time are ready when the client asks.

Service Level Agreement templates to define professional boundaries with your clients.

Find the sweet spot for your care plans. Calculate margins based on check frequency and support hours.

Powerpoint Templates that explain 24/7 monitoring to non-technical clients. Close more retainers.

Use automated reports to proactively communicate value, so clients never ask what they're paying for. Claim your Success Kit and start scaling today. Claim your Success Kit & Start Monitoring Ready to turn monitoring into a profit center? Every Uptimeify subscription includes access to our Success Kit, a collection of battle-tested resources to turn your monitoring into a profit center.