mcp-bing-webmaster
Related Servers
Alternatives to mcp-bing-webmaster
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceEnables AI assistants to query Bing Webmaster Tools data such as site verification, traffic analytics, and search performance, with read-only defaults and configurable site access controls.34MIT
- AlicenseAqualityBmaintenanceBing Webmaster Tools and IndexNow for AI agents: traffic, indexing, crawl issues, inbound links, keywords. Direct writes are off by default; changes go through a plan a person applies.631MIT
- AlicenseBqualityCmaintenanceProvides AI agents full access to Bing Webmaster Tools API for site management, URL submission, sitemaps, traffic stats, keyword research, and URL blocking.248 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to manage sites, review traffic, and work with sitemaps through Microsoft's webmaster API.Apache 2.0
- AlicenseBqualityDmaintenanceProvides secure, read-only access to Bing Webmaster Tools analytics and non-destructive URL submission for indexing, without destructive site management capabilities.16MIT
- AlicenseCqualityCmaintenanceEnables AI assistants to manage Bing Webmaster Tools, including site verification, URL submissions, traffic analytics, crawl monitoring, and keyword analysis through natural language.62MIT
TDQS
Scored across 19 tools
Each tool targets a distinct resource and the descriptions explicitly route between similar ones (traffic_summary vs query_stats vs page_stats, query_pages vs page_queries). The inverse pair bing_webmaster_get_query_pages / bing_webmaster_get_page_queries is the one spot where a careless agent could swap them, but the docs distinguish them clearly.
All tools carry the bing_webmaster_ prefix with a predictable verb_noun form (get_*, list_*, plus a few object-named reads). Minor deviations like auth_status and the generic request tool don't break the pattern.
19 tools is on the heavy side but justified: read-only analytics, crawl, sitemap, link and keyword domains each need several endpoints. Almost every tool earns its place, with the generic request acting as a documented overflow valve rather than filler.
Read coverage is broad, but the surface has dead ends: get_url_submission_quota references bing_webmaster_submit_urls and get_fetched_url references bing_webmaster_fetch_url, neither of which exists as a tool, and writes are globally disabled. Agents can therefore see quota but never submit URLs, and cannot trigger a fetch despite being told how to read one.