INDIVIDUAL MCP TOOL
get_ports
For a monitor with port_scan on (Business plans): which of its host's addresses are verified and how to verify the rest (a file each address serves, or reverse DNS under the host with a TXT record), the ports the last weekly scan found open, flagged where the service usually should not be public, and the recent scans.
LIVE ENDPOINT
https://upheron.com/mcp
Connect to this endpoint to inspect the live schema for get_ports and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.upheron]
url = "https://upheron.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: upheron
Remote MCP URL: https://upheron.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"upheron": {
"url": "https://upheron.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"upheron": {
"type": "http",
"url": "https://upheron.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "upheron",
"transport": "streamable-http",
"url": "https://upheron.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
check_website— Checks whether a public website responds right now, from the monitoring service, without an account.get_account— Plan and its monitor slots (standard in plan_monitors, premium in premium_monitors with their kinds), and the workspace's time zone (workspace.list_locations— Location codes you can pass in a monitor's `locations`.list_monitors— Every monitor with its current status (pending, up, down, degraded), and interval.get_monitor— One monitor with uptime for 24 hours, 7 days and 30 days, its last 90 days, incident totals, its latest results with errors, recent incidents, and route traces from failing locations (Pro and Business: each hop's loss, round trips and jitter over every round).get_monitor_results— A monitor's most recent check results, newest first.get_uptime_history— A monitor's daily uptime, kept for as long as it exists: checks, successful, failed and average response time per UTC day, oldest first.get_sla_report— Business plans: availability against an SLA target for a range of days in the workspace's time zone (time_zone in get_account; by default this month), with the downtime budget used and left, incidents, MTTR, MTBF and the longest outage, per monitor (lowest availability first) and overall.