Uptimeify

MCP Server Monitoring: Checks in Your AI Agent | Uptimeify

Point your AI agent at the Uptimeify MCP server: 20 free checks with no token, your own monitors with an API token. Start your free trial today.

Source: https://uptimeify.io/mcp-server

Point any MCP client at https://uptimeify.io/mcp and your AI agent runs SSL, DNS, mail and reachability checks itself. 20 tools anonymously, no token, no setup. Add an API token and it reads your own monitors too. Start Free Trial Explore Success Kit

MCP Server for Monitoring. Your Agent Runs the Check.

For the technical stakeholder

Endpoint & transport

This is how it is wired. Read the MCP docs https://docs.uptimeify.io/api/mcp Endpoint Streamable HTTP, stateless. No session, no handshake state for you to maintain. POST https://uptimeify.io/mcp Discovery The server card describes the server in machine-readable form. GET https://uptimeify.io/.well-known/mcp/server-card.json Verify One tools/list call over JSON-RPC against the endpoint, with the header Accept: application/json, text/event-stream. If the server returns the tool list, the connection is live. Transport Layer

Your agent asks directly.

No more copy and paste. The usual routine costs you three context switches: open a tab, type the domain, paste the result back into the chat. The MCP server removes the detour. Your agent calls the tool itself, gets structured data back and keeps working, while you stay on the actual question.

• 20 checks as tools, so you settle certificates, DNS, mail auth and reachability inside the conversation instead of across five tabs.
• Anonymous, no token required, so you are connected in a minute with nothing to set up.
• Structured answers, not screenshots, so your agent processes the values instead of just reading them out.

For the technical stakeholder

Tool signatures

This is how it is wired. Browse the public check tools Hosts check_ssl takes host and an optional port. port_check takes host plus port, ping_test takes host and an optional port. Domains The DNS and mail tools take domain, with dkim_check also taking selector. IPs & URLs dnsbl_check and reverse_dns take ip. http_headers, redirect_check, website_status and response_time take a full url. ip_geolocation and asn_lookup take query, meaning an IP or a domain. Scope read-only every anonymous tool queries, none of them change anything. Tool Layer

The whole check bench.

One endpoint. The tools mirror our public tools one to one. Certificate expiry, DNS propagation, SPF, DKIM, DMARC, blacklist status, HTTP headers, redirect chains, ports, response times, geolocation. All read-only, none of it touching your systems.

• TLS and domains, so you can query check_ssl, whois and domain_expiry before a certificate or a domain quietly lapses.
• DNS and mail auth, so you can walk check_dns, dns_propagation, mx_lookup, spf_check, dkim_check, dmarc_check and dnsbl_check in one pass when mail suddenly stops arriving.
• HTTP and network, so you can use http_headers, hsts_check, redirect_check, port_check, ping_test, website_status, response_time, ip_geolocation, asn_lookup and reverse_dns straight from the agent.

For the technical stakeholder

Token, OAuth & scope

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/oauth-protected-resource Scope 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

With a token it becomes your portfolio.

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_monitors and monitor_status, so one sentence tells you what is up and what is not.
• list_incidents and check_history, so you can reconstruct an incident without clicking through views.
• uptime_summary, so availability and response time are ready when the client asks.

SLA & Contract Templates

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

Pricing Calculator

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

White-Label Pitch Decks

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

Churn-Proof Reporting Guide

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.

We don't just monitor. We help you sell.

→ For the technical stakeholder

Discovery & failure modes: how it's wired

The server card at GET https://uptimeify.io/.well-known/mcp/server-card.json describes the server in machine-readable form. If you just want to see what is there, ask for the tool list: bash curl -X POST https://uptimeify.io/mcp \ -H 'Content-Type: application/json' \ -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' The most common stumble is a missing Accept header with text/event-stream. The second most common: calling an authenticated tool without a token. In that case the tool does not return an empty result, it returns an error asking for the Authorization: Bearer header. An OAuth bearer the server cannot resolve behaves differently on purpose. It comes back as a 401 with WWW-Authenticate: Bearer resource_metadata="https://uptimeify.io/.well-known/oauth-protected-resource" — the pointer your client follows to run the login again. A request with no Authorization header at all never gets that challenge: it stays anonymous, which is what keeps the token-free tools usable. Do you need an account to use the MCP server? No. The anonymous check tools work with the URL https://uptimeify.io/mcp alone, no token and no signup. You only need an account once your agent should read your own monitors, because that is what the API token is for. So you can try whether the tools help in daily work first and decide afterwards. How do you connect your MCP client? You add the endpoint to your client configuration, with an Authorization header if you need one. Clients that speak remote HTTP servers point at the URL directly. Clients that only speak stdio bridge to it with mcp-remote, which forwards the call to the HTTP endpoint. If you only need the anonymous tools, leave the header out entirely. json { "mcpServers": { "uptimeify": { "url": "https://uptimeify.io/mcp", "headers": { "Authorization": "Bearer wsm_your_token_here" } } } } Through the stdio bridge: json { "mcpServers": { "uptimeify": { "command": "npx", "args": ["-y", "mcp-remote", "https://uptimeify.io/mcp", "--header", "Authorization: Bearer wsm_your_token_here"] } } } Do you have to keep a token in a config file? No. Your client can log in over OAuth instead: it sends you to the browser, you approve with the account you already have, and from then on it holds a session rather than a secret you pasted. That keeps a long-lived key out of a file that gets synced, shared or committed by accident. An OAuth session is always read-only and shows exactly what that user may see in Uptimeify, checked fresh rather than frozen at login. Static API tokens still work where you want one, for a script or a shared runner. Can your agent change anything through the MCP server? No. Every tool is read-only, both the anonymous checks and the authenticated queries against your monitoring data. Your agent can read and interpret state, but it cannot create, edit or delete monitors and cannot acknowledge incidents. That takes the edge off internal approval: a badly worded prompt cannot reconfigure your monitoring. What does a customer-scoped token see? Only that one customer's monitors. An organization token, by contrast, sees every customer in your organization. So you can hand a client project or a single team member access that shows exactly the right slice instead of opening up your whole portfolio. Can you use the MCP server on your client domains? Yes. The anonymous tools check any publicly reachable domain, including deinkunde.com, with nothing to install on that side. They read what is already answered publicly: certificate, DNS records, mail records, HTTP response. Availability history and incidents are different: those need a configured monitor and a token. Are there rate limits? Yes, and they are worth knowing before you build against them. The endpoint accepts 120 requests per minute per IP, and each individual check tool has its own cap on top: 15 to 30 calls per minute for the anonymous ones depending on how expensive the check is, 60 for the authenticated ones. So a spread of different checks is fine, hammering one tool is not. Over the limit you get HTTP 429 with a retryAfter value telling you when the window resets. Counting is per IP, not per token, so a token does not buy you more. If you have a case that genuinely needs a higher ceiling, talk to us. FAQ

Frequently Asked Questions

Add the endpoint, connect, run a check. The anonymous tools cost you nothing and no token. Your own monitors join in as soon as you have them. Start Free Trial Read the MCP docs

Ready to put your checks inside your agent?