Visualping
Visualping monitors web pages for visual, text, and content changes and sends alerts when detected changes match configured criteria.
Integration
- Vendor
- Visualping
- Category
- productivity
- Auth
- API_KEY
- Tools
- 9
- Composio slug
visualping
Tools
- Bulk Create Monitors
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.
- Create Monitor
Create a monitor in a workspace. Visualping immediately performs an initial check, which uses monitoring capacity or credits.
- Delete Monitordestructive
Permanently delete one monitor from its Visualping workspace.
- Describe Account and Workspaces
Return the connected Visualping account, organization, workspaces, plan limits, balances, and monitor counts. Use this first to resolve a workspace ID for write operations.
- Get Monitor
Get a monitor's configuration, check history, and detected changes in one response.
- Launch Monitor Checks
Immediately launch checks for one or more active monitors, consuming or reserving monitoring credits. Use Preflight Monitor Checks first to confirm credit requirements.
- List Monitors
List and filter monitors visible to the connected workspace, returning one page and a continuation cursor.
- Preflight Monitor Checks
Estimate the credits required to check one or more active monitors without launching a check or changing their schedules.
- Update Monitor
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 rather than the updated monitor representat
Setup
- Create or open a Switchy Project.
- Open Integrations and connect Visualping.
- Authorise through api_key. Switchy stores the connection against your org.
- Everyone in the Project can now @-mention the Visualping tools in chat.
What teammates see: by default, memories from Visualping are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.