Server definition
- Hash
- sha256:5831a52125f4a5005383758191c390689aec76841034112505f8da91efd58dbe
- What it is
- What a remote MCP server returned when asked what it offers: 25 tools
The blob, as servednamed by its sha256
{
"instructions": null,
"tools": [
{
"description": "Marks an open incident as acknowledged and attaches an AI diagnostic note. Use this tool when you have reviewed an active incident and want to let the team know it is being investigated.\n\nNote: This tool does not resolve the incident, it only acknowledges it.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the incident to acknowledge.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"incident_id": {
"description": "Alternative alias for id.",
"type": "integer"
},
"note": {
"description": "Purpose: Optional note or investigation summary.\n\nExample values:\nInvestigating 502 Bad Gateway error on origin server\nChecking database CPU metrics",
"type": "string"
}
},
"type": "object"
},
"name": "acknowledge_incident",
"outputSchema": null
},
{
"description": "Creates a new monitor inside Monitor Hub.\n\nSupports:\n• HTTP\n• HTTPS\n• API\n• Ping\n• TCP Port\n• Keyword Monitoring\n\nUse this tool whenever a user wants to monitor a website, API, server, endpoint, IP address or service.\n\nReturns the newly created monitor and its initial monitoring status.",
"inputSchema": {
"properties": {
"body": {
"description": "Optional HTTP request body payload for POST/PUT checks.",
"type": "string"
},
"category": {
"default": "uptime",
"description": "Purpose: Category grouping.\n\nSupported values:\nuptime\napi",
"enum": [
"uptime",
"api"
],
"type": "string"
},
"headers": {
"description": "Optional custom HTTP headers to include with checks.",
"type": "object"
},
"interval_seconds": {
"default": 300,
"description": "Purpose: Monitoring interval in seconds (Free: 300s, Starter: 60s, Pro/Business: 30s).\n\nSupported values:\n30\n60\n300\n600\n1800\n3600",
"type": "integer"
},
"keyword": {
"description": "Expected keyword string for keyword monitors.",
"type": "string"
},
"method": {
"default": "GET",
"description": "HTTP method (e.g. GET, POST, HEAD).",
"type": "string"
},
"name": {
"description": "Purpose: Descriptive name for the new monitor.\n\nExample values:\nProduction Checkout API\nFrontend Website\n\nValidation rules: Must be a non-empty string.",
"type": "string"
},
"target": {
"description": "Purpose: Target URL or hostname to monitor.\n\nAccepted values: URL or IP address.\n\nExample values:\nhttps://monitorhubs.com\nhttps://api.example.com/health",
"type": "string"
},
"type": {
"default": "http",
"description": "Purpose: Monitoring type.\n\nSupported values:\nhttp\nhttps\ntcp\nport\nping\nkeyword",
"enum": [
"http",
"https",
"tcp",
"port",
"ping",
"keyword"
],
"type": "string"
},
"url": {
"description": "Alias for target.",
"type": "string"
}
},
"required": [
"name"
],
"type": "object"
},
"name": "create_monitor",
"outputSchema": null
},
{
"description": "Permanently removes monitoring and deletes its historical metrics.\n\nUse only when the user explicitly requests the deletion of a monitor, as this action is irreversible and deletes all associated monitoring history and data.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the monitor to delete.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"monitor_id": {
"description": "Alternative alias for id.",
"type": "integer"
}
},
"type": "object"
},
"name": "delete_monitor",
"outputSchema": null
},
{
"description": "Returns incident timeline, outage duration, recovery time, failure reason, affected monitor, and timestamps.\n\nUseful when Claude needs to investigate the root cause of an outage or read historical logs for a specific downtime event.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the incident to inspect.\n\nAccepted values: Integer ID.",
"type": "integer"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "get_incident_details",
"outputSchema": null
},
{
"description": "Retrieves full diagnostic configuration, headers, assertion settings, and last check time for a specific monitor.",
"inputSchema": {
"properties": {
"monitor_id": {
"description": "The unique ID of the monitor to retrieve.",
"type": "number"
}
},
"required": [
"monitor_id"
],
"type": "object"
},
"name": "get_monitor_details",
"outputSchema": null
},
{
"description": "Returns historical uptime events, incidents, and outages for a specific monitor ID.\n\nUseful for checking the long-term reliability of a specific website or server over time.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the monitor.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"limit": {
"default": 50,
"description": "Purpose: Maximum number of historical records to return.\n\nAccepted values: Integer between 1 and 100.",
"type": "integer"
}
},
"required": [
"id"
],
"type": "object"
},
"name": "get_monitor_history",
"outputSchema": null
},
{
"description": "Fetches historical CPU %, RAM %, Disk %, and Network telemetry metrics for a server agent over a specified time window.",
"inputSchema": {
"properties": {
"agent_id": {
"description": "The unique ID of the server agent.",
"type": "number"
},
"hours": {
"description": "Time window in hours (default: 24, min: 1, max: 168).",
"type": "number"
}
},
"required": [
"agent_id"
],
"type": "object"
},
"name": "get_server_metrics",
"outputSchema": null
},
{
"description": "Lists all HTTP, TCP, Ping, and Keyword monitors for the user along with current status and uptime stats.",
"inputSchema": {
"properties": {
"category": {
"description": "Filter by category (uptime or api).",
"enum": [
"uptime",
"api"
],
"type": "string"
},
"status": {
"description": "Filter monitors by status (up, down, warning, paused, pending).",
"enum": [
"up",
"down",
"warning",
"paused",
"pending"
],
"type": "string"
}
},
"type": "object"
},
"name": "list_monitors",
"outputSchema": null
},
{
"description": "Lists configured alert webhooks (Slack, Discord, Telegram, Email) and alert trigger settings with sensitive tokens redacted.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "list_notification_channels",
"outputSchema": null
},
{
"description": "Summarizes downtime events over a specified number of days along with outage duration in minutes and root cause explanations.",
"inputSchema": {
"properties": {
"days": {
"description": "Time window in days (default: 7, min: 1, max: 30).",
"type": "number"
}
},
"type": "object"
},
"name": "list_recent_outages",
"outputSchema": null
},
{
"description": "Lists user public status page configurations and public URLs.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "list_status_pages",
"outputSchema": null
},
{
"description": "Pauses uptime checking for a specified monitor ID.\n\nUse this tool when a user explicitly requests to stop monitoring a website temporarily (e.g. during maintenance).",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the monitor to pause.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"monitor_id": {
"description": "Alternative alias for id.",
"type": "integer"
}
},
"type": "object"
},
"name": "pause_monitor",
"outputSchema": null
},
{
"description": "Fetches recent alert log entries and delivery notifications across email, Slack, Discord, and Telegram channels.",
"inputSchema": {
"properties": {
"limit": {
"description": "Maximum number of alert logs to return (default: 50, min: 1, max: 100).",
"type": "number"
}
},
"type": "object"
},
"name": "read_alerts",
"outputSchema": null
},
{
"description": "Retrieves active and recent outage incidents including start time, resolution time, and AI-generated root cause analysis.",
"inputSchema": {
"properties": {
"limit": {
"description": "Maximum number of incidents to return (default: 50, min: 1, max: 100).",
"type": "number"
}
},
"type": "object"
},
"name": "read_incidents",
"outputSchema": null
},
{
"description": "Provides a high-level health overview (total count, up count, down count, warning count, overall uptime percentage, average response time).",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "read_monitor_status",
"outputSchema": null
},
{
"description": "Lists connected physical/virtual server agents, hostnames, OS types, public/private IPs, and dynamic heartbeat status (up, down, pending).",
"inputSchema": {
"properties": {
"status": {
"description": "Filter servers by status (up, down, pending).",
"enum": [
"up",
"down",
"pending"
],
"type": "string"
}
},
"type": "object"
},
"name": "read_server_status",
"outputSchema": null
},
{
"description": "Calculates 24-hour uptime SLA percentages and average latency statistics across all monitors.",
"inputSchema": {
"properties": {},
"type": "object"
},
"name": "read_uptime_statistics",
"outputSchema": null
},
{
"description": "Marks an ongoing incident as resolved and updates root cause analysis details.\n\nUse this tool when you have diagnosed an incident and want to close it, specifying what steps were taken to fix the issue.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the incident to resolve.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"incident_id": {
"description": "Alternative alias for id.",
"type": "integer"
},
"root_cause": {
"description": "Purpose: Explanation of root cause and resolution steps taken.\n\nExample values:\nRestarted nginx upstream service; 200 OK restored\nRolled back faulty deployment",
"type": "string"
}
},
"type": "object"
},
"name": "resolve_incident",
"outputSchema": null
},
{
"description": "Resolves an active warning sign on a monitored server agent.\n\nCloses open warning incidents for the server, restores the agent status to \"up\" (operational), and clears firing threshold alarms.\n\nUse this tool when you have diagnosed high CPU, RAM, or disk warnings and resolved the underlying server load.",
"inputSchema": {
"properties": {
"agent_id": {
"description": "Alternative alias for id.",
"type": "integer"
},
"id": {
"description": "The unique ID of the server agent.",
"type": "integer"
},
"server_id": {
"description": "Alternative alias for id.",
"type": "integer"
}
},
"type": "object"
},
"name": "resolve_server_warning",
"outputSchema": null
},
{
"description": "Resumes active uptime monitoring for a paused monitor ID.\n\nUse this tool when a user explicitly requests to resume monitoring a website or API.",
"inputSchema": {
"properties": {
"id": {
"description": "Purpose: The unique ID of the monitor to resume.\n\nAccepted values: Integer ID.",
"type": "integer"
},
"monitor_id": {
"description": "Alternative alias for id.",
"type": "integer"
}
},
"type": "object"
},
"name": "resume_monitor",
"outputSchema": null
},
{
"description": "Searches monitors by target URL, keyword, or name.",
"inputSchema": {
"properties": {
"query": {
"description": "The search query matching target URL or monitor name (max 200 characters).",
"type": "string"
}
},
"required": [
"query"
],
"type": "object"
},
"name": "search_monitors",
"outputSchema": null
},
{
"description": "Runs an instant live HTTP/ping probe test against any website or API URL.\n\nMeasures exact response time (latency), HTTP status code, response headers, and response snippet without creating a monitor.\n\nUse this tool to verify endpoint reachability, test latency, check SSL/TLS responses, or diagnose an ongoing outage.",
"inputSchema": {
"properties": {
"body": {
"description": "Optional request body payload for POST/PUT/PATCH.",
"type": "string"
},
"headers": {
"description": "Optional custom request headers.",
"type": "object"
},
"method": {
"default": "GET",
"description": "HTTP method (GET, POST, HEAD, PUT, OPTIONS).",
"type": "string"
},
"target": {
"description": "Target URL or IP address to test (e.g. https://api.example.com/health).",
"type": "string"
},
"url": {
"description": "Alternative alias for target.",
"type": "string"
}
},
"type": "object"
},
"name": "test_endpoint",
"outputSchema": null
},
{
"description": "Triggers a synthetic test alert to verify notification channels (email, webhooks, Slack, Discord).\n\nUse this tool when a user wants to test if their alerting setup is working correctly.",
"inputSchema": {
"properties": {
"message": {
"description": "Purpose: Custom message for test alert verification.\n\nExample values:\nTest alert from Monitor Hub AI\nPlease ignore this alert",
"type": "string"
},
"monitor_id": {
"description": "Purpose: Optional monitor ID to associate with the test alert.\n\nAccepted values: Integer ID.",
"type": "integer"
}
},
"type": "object"
},
"name": "trigger_test_alert",
"outputSchema": null
},
{
"description": "Updates configuration for an existing monitor (name, target URL, interval, HTTP method, headers, expected status code).\n\nUse this tool when a user wants to edit or reconfigure a monitor.",
"inputSchema": {
"properties": {
"body": {
"description": "Request payload body for POST/PUT checks.",
"type": "string"
},
"expected_status": {
"description": "Expected HTTP status code range (e.g. \"200-399\").",
"type": "string"
},
"headers": {
"description": "Custom HTTP headers object.",
"type": "object"
},
"id": {
"description": "The unique ID of the monitor to update.",
"type": "integer"
},
"interval_seconds": {
"description": "New checking interval in seconds (30, 60, 300, 600, 1800, 3600).",
"type": "integer"
},
"keyword": {
"description": "Keyword string expected in response body.",
"type": "string"
},
"method": {
"description": "HTTP method (GET, POST, HEAD, PUT).",
"type": "string"
},
"monitor_id": {
"description": "Alternative alias for id.",
"type": "integer"
},
"name": {
"description": "New descriptive name for the monitor.",
"type": "string"
},
"target": {
"description": "New target URL or IP address.",
"type": "string"
},
"url": {
"description": "Alias for target.",
"type": "string"
}
},
"type": "object"
},
"name": "update_monitor",
"outputSchema": null
},
{
"description": "Updates public status page configuration and slug for the user workspace.\n\nUse this tool when a user wants to rename or update their public status page URL.",
"inputSchema": {
"properties": {
"slug": {
"description": "Purpose: New unique URL slug for the status page.\n\nExample values:\nmy-company-status\nstartup-uptime\n\nValidation rules: Must be URL-safe (no spaces or special characters).",
"type": "string"
}
},
"required": [
"slug"
],
"type": "object"
},
"name": "update_status_page",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:5831a52125f4a5005383758191c390689aec76841034112505f8da91efd58dbe | sha256sum