MCP Server

An MCP server is the far side of the Model Context Protocol: the program that offers an AI client a defined set of tools, resources and prompts.

The server holds the boundary. It declares what it offers via tools/list, validates every incoming argument against a JSON Schema, then runs the call against the real system behind it. The model never touches your API directly. Servers run locally over stdio or remotely over Streamable HTTP, where OAuth handles authorization and the API token scope decides what a client is allowed to see. The Uptimeify MCP server is remote: monitors, incidents and uptime summaries plus diagnostics for DNS, TLS, WHOIS and ports, always within the scope of the API token you connect with.

Related terms

Model Context Protocol (MCP)The Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data through one shared interface instead of one custom integration per system.Tool CallA tool call is a model's structured request to run exactly one named function with validated arguments. Execution happens outside the model.Streamable HTTPStreamable HTTP is the HTTP transport for remote MCP servers: a single endpoint that takes each JSON-RPC message as a POST and answers with either a JSON object or an SSE stream.API Token (Bearer Token)An API token is a secret credential that authenticates programmatic requests to an API, sent as a bearer token in the Authorization header.

Start monitoring in minutes

EU-hosted uptime monitoring with multi-location confirmation that kills false alarms, white-label for agencies.

Start Free Trial