Borrowing it
Nothing to install: this file belongs to zizzfizzix/mcp-server-bwt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zizzfizzix/mcp-server-bwt/main/AGENTS.mdgit clone --depth 1 https://github.com/zizzfizzix/mcp-server-bwtWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/zizzfizzix/mcp-server-bwt/agents-md)<a href="https://agentmods.dev/instructions/zizzfizzix/mcp-server-bwt/agents-md"><img src="https://agentmods.dev/badge/instructions/zizzfizzix/mcp-server-bwt/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/zizzfizzix/mcp-server-bwt/agents-md"><img src="https://agentmods.dev/badge/instructions/zizzfizzix/mcp-server-bwt/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02717 | $0.02717 |
| Opus 5.5 | $0.01087 | $0.01087 |
| Sonnet 5.5 | $0.00543 | $0.00543 |
| Haiku 4.5 | $0.00272 | $0.00272 |
Grade A, and why
mcp-server-bwt AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project overview
mcp-server-bwt is a Python MCP (Model Context Protocol) server that connects AI assistants to the Bing Webmaster Tools API. It runs over stdio (MCPServer from mcp[cli] 2.x) and exposes the service methods of the bing-webmaster-tools client library as MCP tools. There are 62 today, covering site management, submission, traffic, crawling, keywords, links, content, blocking, regional settings and URL parameters. It is packaged with hatchling, managed with uv, and published to PyPI as mcp-server-bwt. Users launch its mcp-server-bwt console script through uvx mcp-server-bwt. It supports Python 3.13 and newer. Development and CI run on the 3.14 release pinned in .python-version.
Task routing
| When the task involves… | Read first | Key rules |
|---|---|---|
| Server startup, env config, entry point | mcp_server_bwt/main.py, pyproject.toml ([project.scripts]) |
BING_WEBMASTER_API_KEY is read at import time and a missing value raises ValueError. app() is the console-script target and must keep transport="stdio". Never log or echo the API key. |
| Adding, removing or renaming an MCP tool | mcp_server_bwt/tools/bing_webmaster.py, README.md (## Available Tools) |
Register tools only through wrap_service_method(mcp, service, "<service_attr>", "<method>") and assign the result to a variable named after the method with # noqa: F841. Keep tools grouped under the # <Area> Tools comments. Tool names, signatures and docstrings come from the upstream library method, so don't hand-write them. Update the README tool list in the same PR. Renaming or removing a tool is a breaking change (see BACKWARD_COMPATIBILITY.md). wrap_service_method adds offset/limit paging to every tool whose upstream method is annotated to return a list, and it raises if the upstream method already has either name. Default page size: BING_WEBMASTER_PAGE_SIZE, else 50 (max 500; 0 disables). Each list tool also caches its upstream list, keyed on the arguments minus offset/limit, in its own ResultCache for BING_WEBMASTER_CACHE_TTL seconds, else 300 (0 disables; errors are never cached). Every non-list tool whose name doesn't start with get_ counts as a write and clears all list caches of its service_attr area when it runs, even if it fails. sites writes clear every area (GLOBAL_WRITE_AREA). A new read tool must therefore be named get_…, or it will clear caches needlessly (test_write_tools_are_exactly_the_mutating_tools pins the set). Tests that share main.mcp must disable cache hits (see test_startup.py). Paged results come back as a CallToolResult, and mcp re-validates their dumped rows against the output model, so every model field must survive a JSON round trip. That's why the date parser in services/bing_webmaster.py accepts RFC 3339. |
| A new upstream service area | mcp_server_bwt/tools/bing_webmaster.py (SERVICE_CLASSES), mcp_server_bwt/services/bing_webmaster.py (__aenter__) |
Add the service class to SERVICE_CLASSES and instantiate it on the same attribute name in BingWebmasterService.__aenter__. The two maps must stay in sync. |
| API client settings (timeouts, retries, rate limits, base URL) | mcp_server_bwt/services/bing_webmaster.py |
Settings are built in BingWebmasterService.__init__. The key is wrapped in pydantic.SecretStr. Each tool call opens and closes the client through async with service. disable_destructive_operations=False is deliberate, so destructive tools (remove site, remove feed, …) are exposed. |
| Dependencies and packaging | pyproject.toml, mcp_server_bwt/version.py |
uv.lock is committed, so installs are reproducible. Change dependencies in pyproject.toml, then run uv lock and commit both files. mcp[cli] is pinned to >=2.2,<3. The server uses mcp.server.mcpserver.MCPServer, because mcp 2.x removed mcp.server.fastmcp (#8, #14). The next major needs the same schema diff as this one did. The version is sourced from mcp_server_bwt/version.py (__VERSION__) via [tool.hatch.version]. Add dev tools to [dependency-groups].dev (this includes lefthook, whose PyPI package ships the hook binary). requires-python is >=3.13, while .python-version pins 3.14 for development and CI, so CI never runs 3.13. [tool.mypy] python_version stays at the requires-python floor, and ruff infers its target from it, so both still check the code against 3.13. What gets published is set in pyproject.toml: the sdist include list (the package, README.md, LICENSE, CHANGELOG.md, pyproject.toml) and the wheel exclude of mcp_server_bwt/test_*.py. Keep repo process files out of both. The README is the PyPI project description, so use absolute URLs for links. PyPI versions are immutable: a bad release is yanked and fixed forward, never re-uploaded. |
| Tests | pyproject.toml ([tool.pytest.ini_options]), Makefile (test) |
Tests live next to the code as mcp_server_bwt/test_*.py (for example test_startup.py). pytest runs over mcp_server_bwt with --doctest-modules, and pythonpath = "mcp_server_bwt". mypy excludes files matching .+test_. Collection imports main.py, which reads the API key at import time, so run the tests with a dummy key: BING_WEBMASTER_API_KEY=dummy make test. The suite also runs in the validation gate, in CI, and in the lefthook pre-push hook, always with a fixed dummy key. |
| Tooling, lint, types, git hooks | Makefile, pyproject.toml ([tool.mypy]), lefthook.yml |
Code must pass mypy --strict and ruff (lint and format, default config). Every function carries full type annotations. Use # type: ignore only where the dynamic wrapping genuinely requires it. make install installs lefthook git hooks. pre-commit runs ruff check --fix and ruff format on staged *.py files and restages the fixes. pre-push runs, in parallel, mypy --strict, the gate's pytest command (with BING_WEBMASTER_API_KEY=dummy) when *.py files are pushed, and uv lock --check when pyproject.toml or uv.lock is pushed. Skip them with --no-verify or LEFTHOOK=0. The hooks don't replace the validation gate below. In a hook sub-job that fixes files, set stage_fixed: true on the sub-job itself, not on its group. |
| Releases | release-please-config.json, .release-please-manifest.json, .github/workflows/release-please.yml |
release-please owns the version: it keeps a chore(main): release X.Y.Z PR open, and merging that PR bumps mcp_server_bwt/version.py, updates CHANGELOG.md, tags vX.Y.Z, and publishes a GitHub release. Never hand-edit __VERSION__ (its line carries # x-release-please-version), CHANGELOG.md, or the manifest. The squash-merged PR title decides the bump: fix: → patch, feat: → minor, and a breaking change (feat!: or a BREAKING CHANGE: footer) → minor while pre-1.0. chore:/docs:/refactor: don't release. The same workflow publishes each new release to PyPI. The build job checks out the tag, runs uv build and fails unless the built version matches the tag. The publish job uploads through PyPI Trusted Publishing (OIDC) in the pypi environment, which only accepts deployments from main. Never add a PyPI token secret. The PyPI publisher is bound to the workflow filename release-please.yml and the environment name pypi, so renaming either breaks uploads until PyPI is updated. To backfill a tag or retry a failed upload, run gh workflow run release-please.yml -f tag=vX.Y.Z from main (the pypi environment rejects any other ref). |
| CI | .github/workflows/ci.yml, .github/workflows/release-please.yml |
ci.yml has one job, validate, which runs on every PR and on every push to main. It runs uv sync --locked, the validation-gate commands below as separate steps in the same order (the pytest step, Tests, sets the dummy key through env:), and an import smoke test (BING_WEBMASTER_API_KEY=dummy uv run python -c "import mcp_server_bwt.main"). validate is a required status check on the main ruleset (bound to the GitHub Actions app), so a PR can't merge until it passes. Never rename the job, because the required check matches it by name. Release-please PRs are the one exemption. A job-level if: skips validate when the PR's head is in this repository and its head branch starts with release-please--branches--. The skipped job still reports validate, which satisfies the required check. Those PRs only touch generated release files, and main re-validates after they merge. Fork PRs, other PRs, and pushes to main always run the full gate. The workflow steps mirror validation.commands in .ai/agentic.config.json, so change them together. There are no paths: filters, because a required check has to report on every PR. release-please.yml runs on push to main (plus a manual workflow_dispatch with a tag input for PyPI backfills). It opens release PRs with the RELEASE_PLEASE_TOKEN repo secret, and its build/publish jobs upload each release to PyPI (see Releases). Permissions are per job, and id-token: write is granted only to publish. That secret has to stay set: PRs opened with the default token don't trigger validate, and a release PR without it can't merge. |
| Docs | README.md |
The README documents client setup from PyPI via uvx mcp-server-bwt (Claude Desktop, Claude Code, Cursor, Zed), upgrades and pinning, a contributor-only local-checkout setup under Development, and the full tool list. Never document a git+https:// install. test_packaging.py enforces the uvx configs and the absence of git installs. Keep both accurate when behavior changes. |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +764 tokens per session 2eab726a13ef
- 1mo ago Changed · +2 lines · +588 tokens per session 253a494b16a1
- 1mo ago First seen · 38 lines · 1,365 tokens per session scan A cb9207144975
mcp-server-bwt AGENTS.md is an instructions file published in the GitHub repository zizzfizzix/mcp-server-bwt (7 stars, last pushed 1mo ago), licensed MIT. It adds 2,717 tokens to every session, about $0.0109 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-24.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.