# Visualping — MCP server on mcp.ai
> Connect your Visualping account and use 9 tools for productivity straight from your AI agent. Connect with your own API key. Visualping monitors web pages for visual, text, and content changes and sends alerts when detected changes match configured criteria.

By: mcp.ai · official
Page: https://mcp.ai/visualping

## Connect (MCP protocol)
Remote MCP endpoint (HTTP, streamable): https://api.mcp.ai/p_visualping?ms=1787293740000
Add it as a custom/remote MCP connector, then authenticate when prompted.

## REST API (no MCP client required)
Every tool is also a REST endpoint, authed with a workspace API key.
Discover: GET https://api.mcp.ai/api/visualping/_endpoints   # public; lists every endpoint
Call:     POST https://api.mcp.ai/api/visualping/<endpoint>
  Authorization: Bearer sk_live_…   # create one at https://mcp.ai/settings/api-keys
  Content-Type: application/json
  Body: { …args }   →   { "ok": true, "tool": "<id>", "result": { … } }

## Developer docs
How to use (MCP or REST), markdown: https://mcp.ai/visualping/skill.md
Postman collection (v2.1): https://mcp.ai/visualping/postman.json

## Tools
- visualping_bulk_create_monitors(mode?: string, interval: string, monitors: object[], workspace_id: integer, initialize_without_baseline?: boolean) — Create two or more active monitors with shared detection settings. Each monitor starts checking immediately and may consume monitoring credits; use only when workspace bulk import is enabled.
- visualping_create_monitor(url: string, crop?: object, mode?: string, active?: boolean, interval: string, keywords?: string, selector?: string, description?: string, notification?: object, workspace_id: integer) — Create a monitor in a workspace. Visualping immediately performs an initial check, which uses monitoring capacity or credits.
- visualping_delete_monitor(job_id: integer, workspace_id: integer) — Permanently delete one monitor from its Visualping workspace.
- visualping_describe_account() — Return the connected Visualping account, organization, workspaces, plan limits, balances, and monitor counts. Use this first to resolve a workspace ID for write operations.
- visualping_get_monitor(job_id: integer, workspace_id?: integer) — Get a monitor's configuration, check history, and detected changes in one response.
- visualping_launch_monitor_checks(job_ids: integer[], workspace_id: integer, restart_schedule?: boolean) — Immediately launch checks for one or more active monitors, consuming or reserving monitoring credits. Use Preflight Monitor Checks first to confirm credit requirements.
- visualping_list_monitors(event?: string, active?: boolean, search?: string, sort_by?: string[], page_size?: integer, date_range?: string, next_cursor?: string, workspace_id?: integer, date_range_start?: string, monitoring_modes?: string[]) — List and filter monitors visible to the connected workspace, returning one page and a continuation cursor.
- visualping_preflight_monitor_checks(job_ids: integer[], workspace_id: integer) — Estimate the credits required to check one or more active monitors without launching a check or changing their schedules.
- visualping_update_monitor(url?: string, crop?: object, mode?: string, active?: boolean, job_id: integer, interval?: string, keywords?: string, selector?: string, description?: string, notification?: object, workspace_id: integer) — Partially update a monitor's core URL, schedule, detection, state, or notification settings. Only explicitly supplied mutable fields are sent. The response reports impact and estimated consumption rat

## Example prompts
- "What can I do in Visualping?"
- "Show me a summary of my Visualping account"

## Links
Docs: https://mcp.ai/docs/mcps/visualping
Website: https://mcp.ai/mcps/visualping