test_notification_contact — UpHeron MCP Tool
test_notification_contact
(test notification contact) is one of 59 tools on the
UpHeron
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call test_notification_contact from your client
- Claude Code UpHeron test_notification_contact run in your project directory
- Claude Desktop UpHeron test_notification_contact ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor UpHeron test_notification_contact ~/.cursor/mcp.json
- VS Code UpHeron test_notification_contact .vscode/mcp.json
- Zed UpHeron test_notification_contact ~/.config/zed/settings.json
- Windsurf UpHeron test_notification_contact ~/.codeium/windsurf/mcp_config.json
- Cline UpHeron test_notification_contact ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI UpHeron test_notification_contact ~/.gemini/settings.json
- Grok UpHeron test_notification_contact .mcp.json (in your project root)
- ChatGPT UpHeron test_notification_contact Settings → Connectors → Advanced → Developer mode
- Claude.ai UpHeron test_notification_contact Settings → Connectors → Add custom connector
- LangChain UpHeron test_notification_contact pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http upheron https://upheron.com/mcp
Other tools on this server
- check_website
- get_account
- list_locations
- list_monitors
- get_monitor
- get_monitor_results
- get_uptime_history
- get_sla_report
- get_error_budgets
- list_incidents
- acknowledge_incident
- list_escalation_policies
- list_on_call_schedules
- get_incident
- post_incident_update
- comment_on_incident
- open_incident
- update_incident
- resolve_incident
- write_postmortem
- list_status_pages
- update_status_page_components
- create_on_call_schedule
- update_on_call_schedule
- delete_on_call_schedule
- add_on_call_override
- remove_on_call_override
- create_escalation_policy
- update_escalation_policy
- delete_escalation_policy
- list_maintenance_windows
- create_maintenance_window
- update_maintenance_window
- change_maintenance_occurrence
- delete_maintenance_window
- get_audit_log
- create_monitor
- preview_monitor_import
- import_monitors
- update_monitor
- pause_monitor
- resume_monitor
- delete_monitor
- add_notification_contact
- confirm_notification_contact
- list_notification_contacts
- get_vulnerabilities
- import_software
- add_software
- remove_software
- mark_vulnerability_fixed
- get_ports
- verify_host
- get_website_changes
- accept_page_change
- scan_ports
- get_domain_watch
- scan_website_software
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.