Checks a beekeeping varroa treatment rotation for resistance risk and withdrawal-period conflicts.
What you can do
Hive Ledger is a remote MCP server for beekeepers that evaluates a varroa mite treatment rotation. According to its registry description, it checks the rotation for resistance risk and for withdrawal-period conflicts. No tool list is published in the manifest, so the exact operations are not documented here.
When to use it
Worth considering if you plan varroa treatments across hives and want an assistant to flag resistance risk or withdrawal-period conflicts in a proposed rotation. It is less useful if you do not keep treatment records or do not need rotation checks.
Requirements
A remote streamable HTTP endpoint at hive-ledger.rowb.app; nothing runs locally. It requires an Authorization header carrying a Bearer API key. A free key is offered at the provider's signup page with a stated limit of 50 calls per month and no card required.
Before you install
The Authorization header is a secret API key; keep it out of shared logs and prompts. The free tier is limited to 50 calls per month, and the manifest declares no authentication beyond that key. Treatment and withdrawal-period guidance is advisory and should not replace label instructions or local regulations.
Connect Authorization token credentials. They are stored privately and never shown on public pages.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/app.rowb.hive-ledger%2Frotation/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Check a beekeeper's varroa treatment history against published resistance-rotation guidance. Deterministic rules only — no AI. Returns violations (same active group repeated, label withdrawal period breached), cautions, and the inputs it could not judge.
The active-group table this service rotates on: product, active ingredient, and IRAC mode-of-action group. Cite the group number when you record a treatment.
Takes no parameters.
get_thresholds
Published varroa damage thresholds with their exact source, plus the monitoring cadence the guidance asks for. Quoted study values — not a recommendation.
Takes no parameters.
Version history
1
v1.0.0LatestSep 28, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.