Bowerbird
Keep a folder of Markdown notes in order, and let an AI assistant, a script or
you search and check them. It is for anyone who keeps notes, runbooks or documentation
as Markdown in a folder or repository. It works on collections in Open Knowledge Format
(OKF) v0.2: one Markdown file per concept, each starting with a small header of
facts (its type, a description, where it came from, who checked it). A bundle is
a folder of concepts; a collection is a bundle, or a folder of bundles.
It is not tied to one format: one format: line in kbmcp.yaml points it at other
formats too (Formats).
It is an MCP server (MCP, the Model Context Protocol, is how AI assistants call tools) and a command line. It checks, maintains and imports concepts, and finds the passages that answer a question. It cares how a concept is written, never what it says. Local files only, no network (but see semantic search, which downloads a model once). Never writes to git. One contract, three users: an agent over MCP, CI, and a person at a terminal with no AI.
Try it (needs uv; its installer is curl -LsSf https://astral.sh/uv/install.sh | sh, which downloads and runs a script, so read it first
if you prefer). In an empty folder:
alias kb='uvx bowerbird-mcp'
kb init apply=true output=text
kb create deploy type=Playbook title="Deploy" description="How we deploy." \
body="Run the deploy script, then check the dashboard. To roll back, redeploy the previous tag." output=text
kb passages 'how do we roll back' output=text # the best passages, with file and line
kb lint output=text # ends: bowerbird-mcp lint: ok: ...
Personal project. Apache-2.0 (see LICENSE; NOTICE credits the spec), built under the ASF generative-tooling guidelines. Bugs and ideas: GitHub Issues; security reports: SECURITY.md.
Run
Requires uv. Install on the fly from PyPI, nothing to clone; this is
the form to use (pip install bowerbird-mcp works too):
uvx bowerbird-mcp help
In the examples below, uv run bowerbird_mcp.py ... means the same command run
from a checkout of this repository (or beside a saved copy of that one file).
To run the latest unreleased code instead of the PyPI release, give uv the repository:
uvx --from git+https://github.com/dfoulks1/bowerbird-mcp bowerbird-mcp help.
Settings: kbmcp.yaml
A kbmcp.yaml is the collection's configuration, and any folder that holds one is a collection: its
base, with its index, archive and bundles. Commit it. It sits at the root, not in a bundle. The tool finds the
nearest one from the current directory up, or you name it with --config, so a server needs no env block. A
folder inside a collection with its own kbmcp.yaml is another collection, and the outer one skips it.
init writes a mostly filled-in one (see below); config apply=true writes the all-commented example, and
neither overwrites a file. The old KB_ROOT variable is gone and is refused: the base is wherever kbmcp.yaml is.
about: Engineering runbooks. # shown to the agent; tells collections apart
user: your-id # your id in confirmation prompts: personal, prefer KB_USER in .env
ai_producers: [zed] # extra AI names for the provenance check (KB_AI_PRODUCERS)
passages: true # false removes the passages and reindex tools
format: okf # okf | adr | markdown | skos | asciidoc | seal-only: what the folder holds (see Formats)
hubs: true # concepts many others link to rank a little higher
semantic: false # also match by meaning (see Reading the collection)
semantic_model: BAAI/bge-small-en-v1.5
min_similarity: 0.6 # how close in meaning a passage must be
vector_index: scan # scan | sqlite-vec | hnsw: how semantic search finds neighbours
index: .kbmcp/index.db # one SQLite file: passages, BM25, links, vectors; "" = memory
build: auto # auto: passages keeps the index current; manual: only `reindex`
roles: [read, write, structure, lifecycle, seal] # roles the server may offer (see Register)
seal: {require: ["**"], exempt_status: [proposed, draft]} # who must have reviewed what (see Sealing)
Overrides: .env and the environment
kbmcp.yaml is shared, so what is yours alone does not go in it. env.example
lists every override as a KB_<KEY> variable (KB_USER, KB_ABOUT, KB_SEMANTIC, KB_VECTOR_INDEX, KB_BUILD,
and so on; lists are comma separated). Copy it to .env beside kbmcp.yaml and uncomment what you change: .env is
not committed (init and config list it in .gitignore). Precedence, last wins: kbmcp.yaml, then .env, then
real environment variables. format is the collection's own and no override touches it. KB_ROLE (singular)
is the same as --role.
init fills in what it can: format is guessed from the folder (thesaurus files mean skos, .adoc files mean
asciidoc, mostly numbered or adr/decisions Markdown means adr, other Markdown with no OKF types means markdown,
else okf), and it asks for what it cannot know: about, your user id (kept in .env)
and holds (the format, to confirm). Over MCP it asks the human with a prompt; at a terminal it asks on the
command line; or pass them (init about="Runbooks." holds=markdown user=you apply=true). Only an okf folder
gets a first bundle.
The index
With no kbmcp.yaml the defaults apply. The index is a cache derived from
the concepts: safe to delete, never committed (a new .kbmcp/ folder ignores
itself). To build it apart from the server, run reindex (incremental: only
changed files are read) and set build: manual, so passages only reads it:
uvx bowerbird-mcp reindex output=text # first semantic run embeds everything: minutes, once
# .pre-commit-config.yaml: refresh after you commit and after pulls
repos:
- repo: local
hooks:
- id: kbmcp-reindex
name: Bowerbird reindex
entry: uvx bowerbird-mcp reindex
language: system
pass_filenames: false
always_run: true
verbose: true
stages: [pre-commit, post-merge, post-checkout]
Where tools look
A collection is where its kbmcp.yaml is: the tool looks for one from the
current directory up (or takes --config path/to/kbmcp.yaml) and treats that
file's folder as the base. With none, it uses the current directory. In an okf collection it is one bundle at its root, or a set of sibling bundles (other formats are just the folder). A
directory whose index.md declares okf_version is a bundle root; bundles do
not nest. An index.md at the collection root lists its bundles (index apply=true there writes it), and tools find the root from inside a bundle
through it. bundles lists them, split makes a directory its own bundle,
rename moves or renames one, migrate moves a concept between bundles,
archive and unarchive retire and restore a concept or a whole bundle,
ingest keep_okf=true merges one in, and upgrade converts OKF v0.1.
Tools follow where you are: in a bundle, that bundle; at the collection
root, every bundle (lint, fix, baseline, status, list, search,
recheck_plan). Name files or directories to lint just those
(lint notes/a.md docs/). Files are named the OKF way: a bundle and the
path within it (bundle=eng file=runbooks/deploy.md), in every input and
output. On the command line, without bundle=, paths are relative to where
you are. Write tools act in the bundle the file belongs to. In a git work
tree, files git ignores are skipped.
Running a tool
wget https://raw.githubusercontent.com/dfoulks1/bowerbird-mcp/main/bowerbird_mcp.py
uv run bowerbird_mcp.py help # every tool, one line each
uv run bowerbird_mcp.py help move # one tool: what it does, its arguments
uv run bowerbird_mcp.py lint output=text
uv run bowerbird_mcp.py init apply=true # start a new bundle
Any tool runs as <name> name=value ... or <name> '<json object>'. Bare
arguments fill the required ones in order (move a.md b.md); on set, any
other key=value is frontmatter (set a.md status=deprecated tags=[x,y]).
Write tools that touch many files default to apply=false and show a diff.
--attest records you, as human:<KB_USER> (else your git user.email), on
create and provenance (generated), seal and recheck_apply
(verified). It exists
only on the command line: no MCP call can pass it.
Output is JSON; output=text prints one key per line and diffs as is.
Exit codes: 0 ok, 1 findings, 2 usage error.
Formats
Bowerbird is not tied to one format. format in kbmcp.yaml says what a folder holds, and the same
search, index and review tools work across them.
okf(the default): Open Knowledge Format bundles. Every tool is available.adr: ADR and MADR decision records. Every Markdown file is a record (exceptREADME.mdandindex.md), whatever its name or folder, and no frontmatter is needed. A hit gets typeadrand itsstatus, read from MADR frontmatter, a## Statussection (Nygard) or a* Status:line (MADR 2).markdown: any other folder of Markdown, no frontmatter needed;index.mdandlog.mdare ordinary files. A numbered file name (0007-use-queue.md) or a path throughadr,adrsordecisionsstill counts as an ADR.asciidoc: AsciiDoc (*.adoc,*.asciidoc), no frontmatter needed. One passage per section; the document header's:name: valueattributes (or YAML front matter) are the metadata, andxref:,link:and<<file.adoc#id>>links count.include::is not followed.skos: SKOS thesauri as Turtle, RDF/XML, JSON-LD, N-Triples or N3 (*.ttl,*.rdf,*.jsonld,*.nt,*.n3; needspip install rdflib). One passage per concept, headed by its broader chain, with its labels, notes and broader, narrower and related concepts in the text.seal-only: any text files you name (code, configuration), with nothing indexed or searched. List them inseal.require; the one tool isseal, andkb seal check=truefails when a listed file has no human review of its current version.
Outside okf a server offers only the tools that format uses: passages, reindex and seal for every format but
seal-only (just seal); markdown adds get, search, dirs, links, list, status, heatmap, init and
config; adr adds move; asciidoc adds heatmap. The command line always has every tool. A hit is unverified
until a human seals that exact file (see Sealing): reviews go in
.waxseals.yaml, not in the file. init guesses
the format from the folder, and the agent's instructions follow it.
OKF layout
OKF only, and not required. Everything in this section (bundles,
index.md,log.md, the archive) is how anokfcollection keeps its concepts in order. Amarkdown,adr,skos,asciidocorseal-onlyfolder needs only akbmcp.yamland its files, in any layout you like.
kb/ the collection (kbmcp.yaml sits here)
index.md lists the bundles; no frontmatter
.gitattributes log.md and index.md merge=union
eng/ a bundle
index.md okf_version, then the list of its concepts
log.md its history (§9)
runbooks/
index.md optional: this directory's concepts
deploy.md a concept
archive/ the archive: a collection of its own, set apart
index.md lists the archived bundles
eng/old-runbook.md archived from eng (archive/eng is a bundle)
OKF index.md
OKF §8: an index lists what is in its directory, for progressive disclosure. Every index has the same body shape, sections under headings with one entry per item:
# Engineering
Hand-written text is kept.
<!-- kb-index:start (generated by KnowledgeBaseMCP index; do not edit between the markers) -->
### runbooks
* [Deploy](./runbooks/deploy.md) - How we deploy.
<!-- kb-index:end -->
- The tool owns what is between the markers and rebuilds it from frontmatter
(title, else first heading, else file name;
description, else the first sentence). Write anything else around them. - Collection root: no frontmatter (it is not a bundle). The list has one
entry per bundle, titled by that bundle's first heading. Tools find the
collection by walking up from a bundle to the nearest
index.mdthat links to it. - Bundle root: frontmatter holds only
okf_version: "0.2", which is what makes the directory a bundle (§12). The list covers every concept, a section per top-level folder. - Any other directory: no frontmatter. The list covers that directory's
concepts and subdirectories (
index dirs=truewrites one everywhere). - Being listed counts as being linked, so a listed concept is not an orphan.
getsynthesizes a missing index from frontmatter (§8 allows this).
OKF log.md
OKF §9: date headings, newest first, one entry per line. Each tool write adds an
entry to the nearest log.md above the change, with a hidden unix-time stamp:
## 2026-10-27
* <!-- 1761588000 --> **Update**: Moved deploy.md to [ship.md](/runbooks/ship.md).
record "note" writes one by hand (link the concept it is about). log file=x.md
reads a concept's history: the entries linking to it in every log.md above it,
and the git commits that changed it. log alone shows the bundle's recent
entries.
For an okf bundle init adds log.md merge=union and index.md merge=union to the
collection's .gitattributes, so git keeps both sides when parallel
branches log or index. After such a merge, fix merges duplicate log date
sections, orders stamped entries by time, and rebuilds the generated index
lists. A section with a
hand-written, unstamped entry keeps its order.
The OKF archive
archive/ is a collection within the collection, and a special one. Its
index.md lists its bundles, like the collection root's. archive file=x.md bundle=eng moves a concept to archive/eng/x.md (starting archive/eng as a
bundle); archive bundle=eng moves the whole bundle to archive/eng/, still a
bundle. unarchive eng/x.md or unarchive eng puts them back. Links follow
both ways.
The live collection does not see the archive: lint, list, search, status
and web leave it out, nothing in it counts as nesting, and lint warns on links
into it (archived_link). Editing tools refuse archived concepts. That is the
only enforcement: the files are plain files, so an editor or a commit can still
change them. It works whether the collection root is a set of bundles or a
bundle itself.
Register with an MCP client
init writes a .mcp.json at the root of the collection: commit it, and whoever clones the repository has the
tools with nothing to register on their own machine (Claude Code asks once to approve a project's server). For
another client, or a folder without one, add this to the client's servers file: .mcp.json in the project for
Claude Code, claude_desktop_config.json for Claude Desktop, .cursor/mcp.json
for Cursor. VS Code's .vscode/mcp.json takes the same entry under "servers".
{
"mcpServers": {
"bowerbird": {
"command": "uvx",
"args": ["bowerbird-mcp"]
}
}
}
The server runs in the project folder, so it finds the kbmcp.yaml there (your
id is user: in it). To point at one elsewhere, add "--config", "/path/to/kb/kbmcp.yaml" to args. Or, in Claude Code:
claude mcp add bowerbird -- uvx bowerbird-mcp --config /path/to/kb/kbmcp.yaml
Several collections at once: one entry each, with its own --config. The
client prefixes tool names with the entry name, and each file's about: tells
the agent what that collection holds. Each keeps its own index.
The client loads the tool list at start. After editing the script, restart
the client or reconnect the server (/mcp in Claude Code).
Roles: a smaller tool list per agent
All 35 tools cost an agent about 7,250 tokens of schema (an estimate: each tool's name, description and argument
schema as the client receives them, in characters divided by four); the first four roles are each about a quarter of that, and seal is one tool. Register the same
script more than once, each with a role (--role, or KB_ROLE; several with
commas), and each server offers only that role's tools:
| Role | Tools | Schema |
|---|---|---|
read |
find and read, nothing written: dirs get heatmap links list log passages search status vocab |
10, ~1,750 tokens |
structure |
shape, repair and reorganization: archive bundles dirs ingest migrate move rename split unarchive web |
10, ~1,700 tokens |
write |
write a concept and check it: cite create fix lint record set |
6, ~1,600 tokens |
lifecycle |
keep it current: baseline config index init provenance recheck_apply recheck_plan reindex upgrade |
9, ~1,800 tokens |
seal |
a human's review of a file, and the check for it: seal |
1, ~500 tokens |
{
"mcpServers": {
"kb-read": { "command": "uvx", "args": ["bowerbird-mcp", "--role", "read"] },
"kb-write": { "command": "uvx", "args": ["bowerbird-mcp", "--role", "write"] }
}
}
The read server is read-only, so a client can approve it without asking; the others
change files (seal only writes a review: a ledger entry, or a concept's own verified key). A tool can belong to more than one role (dirs is in read and
structure), and a server with no --role offers them all. With no --role the server offers every role that roles: in
kbmcp.yaml leaves on; naming a role that is off refuses to start. Outside okf the format limits it further, to the tools
that format uses (see Formats). The CLI always has every tool.
Sealing: who reviewed what
seal is the one function for a human's review, in every format. It shows the human the exact file in a
prompt, asks for their id, and records who reviewed that version and when. Over MCP the human types their own id;
at a terminal --attest records you; an assistant can only seal as itself (by=process:<id>), never as a human.
verify (the OKF word), and ratify or accepted (the ADR words), are its command-line names too.
okf: averified: {by, at, sha256}entry in the concept's own frontmatter.markdown,adr,skos,asciidocandseal-only: one dense line per file in.waxseals.yamlat the collection root (commit it), holding only the latest review: file, sha256, who, when,bowerbird(the version that wrote it), anddecision=accepted|rejectedfor an ADR. The file itself is never edited, so Nygard ADRs, MADR and thesauri all work.
Like a wax seal, a review breaks when the file changes, and only a new review makes a new one (it replaces the old line; git has the history). The sha256 covers the file's exact bytes (line endings normalized; for okf, without the verified key). Edit the
file after sealing and the seal is broken: passages shows the hit unverified and stale. A ledger decision
becomes the hit's status.
seal check=true changes nothing and exits 1 on findings, for a pre-commit hook and for CI (since=origin/main
limits it to a pull request's files):
unsigned: a file the policy requires has no review by a human.stale_signature: reviewed, then edited.claims_accepted: its own status says accepted, but no human reviewed it.unreadable: a required file is not UTF-8 text, so it cannot be reviewed here.orphan_signature: a ledger entry for a file that is gone (a warning).
The policy is the seal key in the committed kbmcp.yaml (nothing local can loosen it); by default every file needs a
review, except those whose status is proposed or draft:
seal: {require: ["**"], exempt_status: [proposed, draft]}
A require glob that starts with ! takes files back out, for a generated page that needs no review:
require: ["/*.md", "!/tools.md"].
# .pre-commit-config.yaml
repos:
- repo: local
hooks:
- id: bowerbird-seal
name: Bowerbird seal check
entry: uvx bowerbird-mcp seal check=true output=text
language: system
pass_filenames: false
always_run: true
Limits: a hook can be skipped (--no-verify), so run the same command in CI. seal proves a ledger entry exists
for these bytes, not who typed it: protect .waxseals.yaml and kbmcp.yaml with CODEOWNERS or branch
protection so changes to them need a named reviewer. A SKOS file is sealed whole, not per concept.
Before you push
uv run bowerbird_mcp.py lint output=text # what's wrong, each with a fix
uv run bowerbird_mcp.py fix apply=true # mechanical repairs, then re-lint
uv run bowerbird_mcp.py lint output=text # what's left needs you
scope=okf limits the check to the spec; scope=house to hygiene (links,
anchors, orphans, islands, stubs, duplicate titles, reference links,
filenames, tags, generated indexes). only= and ignore= keep or drop finding
kinds: lint only=stub,island.
CI
Vendor bowerbird_mcp.py into the bundle's repo, then:
# .github/workflows/okf.yml
name: okf
on: [push, pull_request]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0 # provenance needs full history
- uses: astral-sh/setup-uv@v6
- run: uv run bowerbird_mcp.py lint scope=okf output=github
Findings show as annotations on the PR. output=sarif suits code scanning.
On PRs, since=origin/${{ github.base_ref }} limits findings to the files the PR
changed.
On a large existing collection, commit a baseline apply=true snapshot and
run lint baseline=.okf-baseline.json, so only new findings fail. The
snapshot sits at the collection root and matches from any directory. CI lints;
it does not push fixes (fork PRs get a read-only token anyway).
To skip files outright, list them in a kbmcp.nolint file. It works like
.gitignore: it may sit in any directory, patterns are relative to it, the
last match wins and ! re-includes. At the collection root it covers every
bundle. Skipped files are still read, so links to them resolve. One file can
skip itself with the line <!-- kbmcp-nolint -->.
# kbmcp.nolint: agent instructions are not concepts
AGENTS*
CLAUDE.md
.kiro/
pre-commit, lint only (a hook that edits files leaves the commit unstaged).
lint always ends with a verdict line, such as bowerbird-mcp lint: ok: 214 concept(s) in 3 bundle(s) checked, 0 finding(s), conformant: True, so you can
see it ran. pre-commit prints a passing hook's output only with verbose: true:
repos:
- repo: local
hooks:
- id: okf-lint
name: OKF lint
entry: uv run bowerbird_mcp.py lint output=text
language: system
pass_filenames: false
verbose: true
Reading the collection
-
Find things in three steps, each small:
dirsmaps the bundle (each directory and how many concepts it holds);searchranks concepts by where every word matches (title, then id, tags, type, description, body), withtype=,tag=anddir=filters;getreads only the top hit.vocablists the tags and types in use, the words those filters take.uv run bowerbird_mcp.py dirs output=text uv run bowerbird_mcp.py search deploy rollback dir=runbooks output=text uv run bowerbird_mcp.py get runbooks/deploy.md output=text
-
passagesanswers a question. It cuts concepts at headings (a long section is cut again at blank lines, each piece repeating the last short paragraph of the one before) and returns the best sections, each with file, line, heading, trust tier and staleness, so the answer can cite and qualify its sources. Ranking is BM25 (rarer words count more; any one word may match; no stemming), with title, tags, type and description counting too, and concepts many others link to a little higher (hubs). Withsemanticon, passages are also matched by meaning and the two rankings are fused.vector_indexpicks how:scan(exact, in Python; fine to a few thousand passages),sqlite-vec(exact, in C;pip install sqlite-vec) orhnsw(approximate, for 100K+;pip install hnswlib; it keeps the top 500 before the type, tag and dir filters). No hit returnsgap: true: say the collection has nothing, don't guess. Passages are indexed in one SQLite file (indexinkbmcp.yaml), updated from the files that changed.reindexbuilds it ahead of time, for a hook, and withbuild: manualpassagesonly reads it;reindex info=truereports what it holds and how far behind it is,drop=truedeletes it.passages: falseremoves both tools.uv run bowerbird_mcp.py reindex output=text uv run bowerbird_mcp.py passages 'how do we roll back a deploy' output=text
-
webmaps links and citations: bundles at the collection root, concepts in a bundle.output=textfor the terminal,output=mermaidfor anything that draws Mermaid (GitHub, GitLab). -
heatmap days=30ranks concepts by how many commits changed them (the ones most likely to collide across branches) and by how many people did; who changes the most; and concepts only one person has ever touched. In OKF index.md and log.md are left out; the other formats count their own files (.md, or.adocand.asciidoc). -
statuslists what needs a person next: longest since review, oldest drafts, concepts without sources, the longest concepts, and what goes stale withindue_days; the most linked-to concepts (hubs); and the pages links want that do not exist yet (wanted), most wanted first. Inmarkdownandadrit counts by type, status, state (a decision record is accepted once a person has sealed it, else proposed; superseded is final) and tier, and the records edited since a review (stale);list status=proposedis the unreviewed worklist. -
log file=x.mdis a concept's history.
Known limits
- A human
sealover MCP needs a client that supports elicitation (confirmation prompts); otherwise the human runs it from the CLI. move,migrate,split,rename,archiveandunarchiverewrite links (code blocks included; read the diff) and §6.2 path fields (resource,computation,executor/attester,sources[].resource). A value naming an existing file is a path; one naming nothing is a path only if it has a file extension or a leading/,./or../, else a scope description.- OKF makes
okf_versionoptional; here it is how a bundle is found. An undeclared bundle is any folder until you pass it asbundle=. ingestdoes not convert other formats or check licenses. Its plan says so.- With
format: skos, links between concepts are not counted, sohubsdoes nothing, and a file that does not parse is skipped without an error. Withformat: asciidoc,include::is not followed, andmoveis not offered. passageshas no stemming ("rolling" will not match "roll"), and withbuild: manualit does not notice files changed since the lastreindex. Semantic search downloads its model (~65 MB) once into~/.cache/bowerbird-mcp/models.fastembedand its dependencies (about 150 MB) come with the installed package (uvx bowerbird-mcp) but not with the bare script, which needsuv run --with fastembedforsemantic: true. The index lives in the fileindexnames and is safe to delete; nothing in the collection changes.
Self-check
uv run test_bowerbird_mcp.py
Spec
SPEC.md is OKF v0.2, copied unchanged from
GoogleCloudPlatform/knowledge-catalog at commit bad9bdb,
Apache-2.0.
Metadata
Release files for bowerbird-mcp 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bowerbird_mcp-2.0.0.tar.gz | 99.7 kB | Without provenance | Details for bowerbird_mcp-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bowerbird_mcp-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for bowerbird_mcp-2.0.0-py3-none-any.whl |
Total release size: 188.8 kB
Release files / bowerbird_mcp-2.0.0.tar.gz
| Download URL | bowerbird_mcp-2.0.0.tar.gz |
|---|---|
| Size | 99.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ebba48606158e498dea82e18c3718206a66f53080129fc89f558f865f93ce26
|
|
BLAKE2b-256 checksum How to use checksums |
687a5e414250a3eab69b08001d508d063bdc63b9cb187a0a9e134facf8d8a727
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / bowerbird_mcp-2.0.0-py3-none-any.whl
| Download URL | bowerbird_mcp-2.0.0-py3-none-any.whl |
|---|---|
| Size | 89.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f9565828ed6b5f3855d520865a3c6303dd677bfb9f20142b875f84ee9f367f3
|
|
BLAKE2b-256 checksum How to use checksums |
967243d03eb0c7bbd8214d75c451159a8cf3a62fadf699cb367c0ecac84df906
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.26 {"installer":{"name":"uv","version":"0.11.26","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for bowerbird-mcp 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.