mcp-server-bwt

Created By
zizzfizzixa year ago
Model Context Protocol (MCP) server for Bing Webmaster Tools (BWT) allowing Claude.ai and other clients to interact with the BWT API
Overview

what is mcp-server-bwt?

MCP server-bwt is a server application designed for Bing Webmaster Tools, enabling users to manage and interact with their Bing web properties effectively.

how to use mcp-server-bwt?

To use mcp-server-bwt, you need to install the project dependencies and run the application using the provided make commands.

key features of mcp-server-bwt?

  • Easy installation and setup using make commands
  • Comprehensive testing suite to ensure code quality
  • Linting and formatting tools for maintaining code standards
  • MCP inspector for analyzing Bing Webmaster Tools data

use cases of mcp-server-bwt?

  1. Managing Bing Webmaster Tools properties for websites.
  2. Running tests to ensure the server application functions correctly.
  3. Analyzing web data through the MCP inspector.

FAQ from mcp-server-bwt?

  • What are the requirements to run mcp-server-bwt?

You need Python and Node.js installed on your system.

  • How do I install the project dependencies?

Run the command make install to install all necessary dependencies.

  • Can I run tests on the application?

Yes! You can run tests by executing the command make test.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zizzfizzix
Star
1
Language
Python
License
MIT license
Tags

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago