Hosted MCP server/Other Official

Official Visualping MCP server

Hosted at visualping.io·Streamable HTTP

Visualping monitors web pages for changes from an AI assistant. The official MCP server is at https://visualping.io/mcp. A Visualping account is required, and the first connection prompts for the account email and password. Available actions depend on the workspace role: Viewers can view monitors and changes but cannot create, edit, run, flag, or hide them, while Editors and Admins can. Personal accounts have full access to their own monitors. The provider currently lists Claude, ChatGPT, and Grok as supported clients; other Streamable HTTP clients may work but are not vendor-listed.

visualping.io Streamable HTTP OAuth Server not checked yet Reviewed 2026-11-16
About

Where it fits

Teams and individuals monitoring web page changes who have a Visualping account and a supported client.

  • Sign in with the Visualping account on first connect.
  • Monitor a web page for changes.
  • Check workspace role permissions before asking an agent to create monitors.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Visualping as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http visualping https://visualping.io/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://visualping.io/mcp
Host
visualping.io · /mcp
Transport
Streamable HTTP
Authentication
OAuth
Server name
visualping
Listing type
Official provider listing

The installer uses the server name visualping. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that visualping appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Sign in with the Visualping account on first connect. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Visualping documentationhttps://help.visualping.io/en/articles/11982593