com.insightfulpipe/bing-webmaster
Bing Webmaster Tools MCP by InsightfulPipe
Is the Bing Webmaster Tools MCP by InsightfulPipe MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Hosted Bing Webmaster Tools MCP server, with each action switched on or off per account.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error": "invalid_token", "error_description": "Authentication failed. The provided bearer token is invalid, - Endpoint
- https://bing-webmaster.insightfulmcp.com/ (streamable-http)
- Host
- bing-webmaster.insightfulmcp.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://bing-webmaster.insightfulmcp.com/ registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server bing-webmaster.insightfulmcp.com, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp_connection.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/Insightful-Pipe/bing-webmaster-mcp-server
- Website
- https://insightfulpipe.com/mcp-servers/bing-webmaster
- Registry
- active, updated 2026-10-21 · registry entry
Compare this server with others.
More servers
Servers that mention webmaster.
- GSC Wizard com.gscwizard/gsc-wizard · needs auth
- Murkuz SEO com.murkuz/murkuz · needs auth
- IndexPulse in.puzaricloud/indexpulse · needs auth
- SEO Tools: Yandex.Webmaster io.github.antohins/seo-tools-mcp-ywm · alive
- Bing Webmaster AI CLI MCP io.github.stufently/bing-webmaster-ai-cli-mcp · alive
- Yandex Webmaster MCP io.github.askads/mcp-yandex-webmaster · alive
- io.github.BoxLab-Ltd/yandex-webmaster-mcp · alive
- Yandex Webmaster MCP io.github.stufently/yandex-webmaster-mcp · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.