Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

bot.ranch/mcp-server

NPM · @RANCHBOT/MCP-SERVER

Read and write cattle and sheep records with farm-scoped, revocable access.

0 this week 87 Trust /100

Last scanned (13 hours ago)

Scores higher than 81% of npm servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 33 of 114 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to RanchBot/mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 32 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 8707 tokens (~106/item across 82 items; 82 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 83 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 −3
    • Stability: fail → 0.80 functional
  • 30 Oct 26 0
    • Package version: 0.1.6 → 0.2.0 functional
  • 25 Oct 26 0
    • Package version: 0.1.6 → 0.2.0 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/@ranchbot/mcp-server@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo RanchBot/mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/RanchBot/mcp-server/.github/workflows/release.yml@refs/tags/v0.2.0
Rekor log index 3331334028
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1022fdc61b4d3c8c37a78e67257807c8355957e99cf8af87938822d129842b73a64fc266435d7cd14853f1ddc3b33929209a8fd75ebd43da33479479d

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 114 packages
Packages resolved 114
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 82 exposed · ~7,996 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
list_memories ~57

List what the assistant currently remembers about this farm (the current value per key). Use before saving a memory to avoid duplicate or conflicting keys.

NameTypeReqDescription
farm_idstring–The ID of the farm (optional if a default is set).

No output schema declared.

No examples provided.

list_my_farms ~20

List all farms that the user has access to

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_pending_imports ~48

List concierge import requests across all farms (admin only). Defaults to PENDING status.

NameTypeReqDescription
skipinteger––
statusstring––
takeinteger––

No output schema declared.

No examples provided.

list_protocol_versions ~45

List immutable farm protocol definitions with bounded pagination. Never invent missing steps.

NameTypeReqDescription
farm_idstring––
skipinteger––
takeinteger––

No output schema declared.

No examples provided.

list_rations ~64

List feed rations on the farm: named recipes in per-head-per-day amounts, with their ingredients and group assignments.

NameTypeReqDescription
farm_idstring––
include_inactiveboolean––
skipinteger––
takeinteger––

No output schema declared.

No examples provided.

list_records ~174

List records (events applied to animals or groups, e.g. feed/health/movement) on the farm. Without a target or time bound this is the ordinary farm-wide list. With an animal_id, group_id and/or applied_from/applied_before it becomes a bounded history read (default 50, max 200). Scoped credentials: an animal_id filter also needs read:animals, a group_id filter also needs read:groups, and include_group_context needs both.

NameTypeReqDescription
animal_idstring––
applied_beforestring––
applied_fromstring––
farm_idstring––
group_idstring––
include_group_contextboolean––
skipinteger––
takeinteger––
typestring––

No output schema declared.

No examples provided.

list_traceability_events ~74

List typed traceability events on the farm. Voided events are excluded unless include_void is true.

NameTypeReqDescription
farm_idstring––
include_voidboolean––
kindstring––
movementboolean––
skipinteger––
takeinteger––

No output schema declared.

No examples provided.

list_workflow_templates ~66

List farm-owned workflow templates with their current published version. Sheep farms receive Detailed and Minimal lambing starters on first use. Read-only.

NameTypeReqDescription
farm_idstring––
skipinteger––
takeinteger––
workflowstring––

No output schema declared.

No examples provided.

lookup_animal_by_eid ~80

Read-only exact EID lookup on one farm across inventory statuses. Never creates or changes animals. Missing matches return not found; multiple animals return an ambiguity error. Requires Reader access.

NameTypeReqDescription
eidstringyesThe EID to search for
farm_idstring–The ID of the farm (optional if default is set)

No output schema declared.

No examples provided.

preview_birth_event ~197

Validate and preview one atomic birth event without saving farm data. Supports observation-only, existing-offspring, new-offspring and mixed bundles. Show the producer every bundle field and all resolved dam, group, protocol, and evidence details. Obtain explicit approval of this exact preview before calling confirm_birth_event. Before confirmation only, any change to the proposal or its referenced evidence requires another preview and renewed approval. For a saved birth, use preview_workflow with operation amend_birth, record_id, expected_revision and reason, then review and commit_workflow; amendment_operation entered_in_error invalidates it. Use this route only when exposed by the connected release; otherwise stop and contact https://ranch.bot/support. Do not re-record one or use generic edits as a workaround.

NameTypeReqDescription
bundleobjectyes–
farm_idstring––
request_idstringyesStable request UUID. Preserve it across preview, confirmation, and retries.

No output schema declared.

No examples provided.

preview_workflow ~338

Resolve one workflow run into a non-committable preview without creating livestock records. Use operation record_birth with template_id and inputs, or operation amend_birth with record_id, expected_revision, reason and changes (amendment_operation amend or entered_in_error) to preview a birth correction or invalidation. Resolves literal and today defaults once and returns structured field/domain issues. Show the producer the complete review before seeking approval for commit_workflow. Never guess a missing required answer.

NameTypeReqDescription
amendment_operationstring–amend_birth: correct facts (amend) or invalidate the event (entered_in_error).
bundleobject–Untemplated record_birth only: a complete birth bundle (observation-only, existing animal links, or inline new profiles). Mutually exclusive with template_id/inputs.
changesobject––
expected_revisioninteger–amend_birth: the record revision the producer reviewed.
farm_idstring–Farm UUID; defaults to the active farm.
inputsobject––
operationstring–Defaults to record_birth. Use amend_birth to correct or mark entered in error an existing BIRTH record.
reasonstring––
record_idstring–amend_birth: the canonical BIRTH record being corrected.
replaces_preview_idstring––
request_idstringyesStable request UUID. Retrying the identical payload returns the same snapshot.
template_idstring––
template_versioninteger––
timezonestring–IANA timezone used once to resolve the "today" date default; never guessed.

No output schema declared.

No examples provided.

publish_workflow_template_version ~95

Publish an immutable new template version. Requires the OWNER role and the exact expected_current_version; a stale value returns a conflict. Definitions cannot weaken handler invariants, hide indispensable controls, change core types, or invent units.

NameTypeReqDescription
definitionobjectyes–
expected_current_versionintegeryes–
farm_idstring–Farm UUID; defaults to the active farm.
template_idstringyes–

No output schema declared.

No examples provided.

recent_transport_suggestions ~58

Read-only recent transporter and vehicle details derived from current nonvoid events on the farm. Suggestions require explicit confirmation for a new trip; they are not a contacts directory.

NameTypeReqDescription
farm_idstring––
takeinteger––

No output schema declared.

No examples provided.

remove_identifier ~62

Remove an identifier from an animal

NameTypeReqDescription
animal_idstringyesThe ID of the animal
farm_idstring–The ID of the farm (optional if default is set)
identifier_idstringyesThe ID of the identifier to remove

No output schema declared.

No examples provided.

restore_group ~55

Restore a previously archived group back to the active list.

NameTypeReqDescription
farm_idstring–The ID of the farm (optional if a default is set).
group_idstringyesThe UUID of the archived group to restore.

No output schema declared.

No examples provided.

restore_location ~58

Restore an archived location. A sublocation can only be restored beneath an active parent; restoring a premises restores its sublocations too.

NameTypeReqDescription
expected_versioninteger––
farm_idstring––
location_idstringyes–

No output schema declared.

No examples provided.

set_birth_history_settings ~57

Replace explicit producer-approved birth-history settings. Never invent biological interval defaults; an empty birth_windows array means no planned windows.

NameTypeReqDescription
farm_idstring–Farm UUID; defaults to the active farm.
settingsobjectyes–

No output schema declared.

No examples provided.

set_default_farm ~70

Change the saved default farm for later calls on this session. This changes context, not farm data; it is unnecessary when every scoped call passes farm_id explicitly, and it should be used only when the user asks.

NameTypeReqDescription
farm_idstringyesThe ID of the farm to set as default

No output schema declared.

No examples provided.

set_default_workflow_template ~64

Select the farm default template for its workflow. Requires the OWNER role and the exact expected_metadata_revision.

NameTypeReqDescription
expected_metadata_revisionintegeryes–
farm_idstring–Farm UUID; defaults to the active farm.
template_idstringyes–

No output schema declared.

No examples provided.

set_home_location ~54

Set the farm default home premises. Pass location_id null to clear it. This never changes move events and is never assumed as an origin.

NameTypeReqDescription
farm_idstring––
location_idstring|null––

No output schema declared.

No examples provided.

traceability_report ~148

Farm-record completeness report over typed events: movement gap checks, identification basis, sent/received discrepancies, and a separate legacy-unstructured section. Not an official submission; independent of the ENABLE_REPORTS gate.

NameTypeReqDescription
animal_idstring––
date_basisstring––
farm_idstring––
fromstring––
identifierstring––
include_legacyboolean––
include_voidboolean––
kindstring––
location_idstring––
movementboolean––
skipinteger––
takeinteger––
tostring––

No output schema declared.

No examples provided.

update_animal ~385

Update an existing animal's details. Pass the fields to change as the named profile fields (name, kind, sex, breed, color, birth_date, notes); they merge into the existing metadata rather than replacing it, so changing one field keeps the rest.

NameTypeReqDescription
animal_idstringyesThe UUID of the animal to update.
birth_datestring–Exact date of birth as an ISO date (YYYY-MM-DD). Supply it only when the user states the date itself. If the user gives an approximate age instead, omit this field and keep that age wording in notes;…
breedstring–Breed or cross, e.g. "Suffolk X", "Angus".
colorstring–Color or markings, e.g. "white", "black white-face".
farm_idstring–The ID of the farm (optional if a default is set).
inventory_statusstring–Inventory status: CURRENT (default on create), UNKNOWN when current presence is unconfirmed, SOLD, DECEASED, or NOT_MANAGED when care ended without sale or death. Historical profiles remain readable.
kindstring–Classification word: cow, heifer, bull, steer, ram, ewe, ewe lamb, lamb, kid, etc.
metadataobject–Optional raw metadata keys to set; merges into the existing metadata over the named fields.
namestring–The animal's name or call name.
notesstring–Any other standing detail (e.g. "bottle-fed", "polled"). Goes into metadata.notes.
sexstring–Sex/gender, e.g. female, male, castrated male (steer/wether).

No output schema declared.

No examples provided.

update_chute_session ~160

Revise a PROPOSED chute session before the user starts it: rename it or replace its widget grid (full replacement list, same widget types and arrangement rules as create_chute_session). Sessions that have been started at the chute cannot be changed from here — only the operator can edit those in the app.

NameTypeReqDescription
farm_idstring–The ID of the farm (optional if a default is set).
group_namestring–Group the processed animals join; created if it does not exist.
namestring–New session name.
record_typestring––
session_idstringyesThe PROPOSED chute session UUID.
widgetsarray–Full replacement widget list, in display order.

No output schema declared.

No examples provided.

update_farm_task ~66

After producer approval, update task status and optionally its due date. An explicit null clears the date; omission preserves it.

NameTypeReqDescription
due_datestring|null––
farm_idstring––
statusstringyes–
task_idstringyes–

No output schema declared.

No examples provided.

update_group ~187

Update an existing group, and optionally add animals to it. Membership is additive: animal_ids adds those animals and never removes existing members. Omit animal_ids (or pass an empty array) to leave membership unchanged. Every requested animal must be an active animal on the same farm; any unknown, archived or other-farm animal fails the whole update. A group update that adds animals cannot be undone.

NameTypeReqDescription
animal_idsarray–Animal UUIDs to ADD to the group (additive; existing members are preserved). Omit or pass [] to leave membership unchanged. Cannot be undone.
descriptionstring–The new description of the group.
farm_idstring–The ID of the farm (optional if a default is set).
group_idstringyesThe UUID of the group to update.
namestring–The new name of the group.

No output schema declared.

No examples provided.

update_group_membership ~128

Add and remove group members. Pass the membership_fingerprint from a fresh group read; a stale one is a 409 conflict. add/remove ids must not overlap, targets must be same-farm, and additions must be active. Returns the ids actually changed. Removal changes no record and cannot be undone.

NameTypeReqDescription
add_animal_idsarray––
farm_idstring–The ID of the farm (optional if a default is set).
group_idstringyes–
membership_fingerprintstringyes–
remove_animal_idsarray––

No output schema declared.

No examples provided.

update_import_request_status ~79

Mark an import request PROCESSING, COMPLETED, or FAILED, with an optional summary of what was loaded (admin only).

NameTypeReqDescription
import_request_idstringyesThe ID of the import request
statusstringyesThe new status
summarystring–What was loaded or why it failed (shown to the customer)

No output schema declared.

No examples provided.

update_location ~133

Update a location directory entry. Pass expected_version to reject a stale edit. Reparenting an existing sublocation is an explicit directory edit and never changes prior event snapshots.

NameTypeReqDescription
addressstring|null––
categorystring|null––
contextstring|null––
countrystring|null––
expected_versioninteger––
farm_idstring––
legal_land_descriptionstring|null––
location_idstringyes–
namestring––
parent_idstring|null––
province_statestring|null––

No output schema declared.

No examples provided.

update_premises_identifier ~153

Update a premises identifier on a root premises. Omitted fields keep the stored value; pass null to clear nullable metadata. Values are stored as strings with leading zeros preserved; no registry verification is claimed. Scheme OTHER needs a scheme_label.

NameTypeReqDescription
confirmedboolean––
expected_versioninteger––
farm_idstring––
identifier_idstringyes–
is_preferredboolean––
issuerstring|null––
jurisdictionstring|null––
location_idstringyes–
schemestring––
scheme_labelstring|null––
sourcestring|null––
valuestring––

No output schema declared.

No examples provided.

update_record ~85

Update an existing record.

NameTypeReqDescription
applied_atstring–When the event occurred (ISO date/time).
descriptionstring––
farm_idstring–The ID of the farm (optional if a default is set).
namestring––
record_idstringyesThe UUID of the record to update.
typestring––

No output schema declared.

No examples provided.

update_workflow_template_state ~95

Archive or reactivate a template. Requires the OWNER role and the exact expected_metadata_revision. Archiving the default template requires an active replacement_template_id in the same transaction.

NameTypeReqDescription
expected_metadata_revisionintegeryes–
farm_idstring–Farm UUID; defaults to the active farm.
is_activebooleanyes–
replacement_template_idstring––
template_idstringyes–

No output schema declared.

No examples provided.

void_traceability_event ~73

Void a typed event with a reason. History keeps every revision; the event leaves ordinary totals without erasing the record.

NameTypeReqDescription
event_idstringyes–
expected_revisionintegeryes–
farm_idstring––
reasonstringyes–
request_keystringyes–

No output schema declared.

No examples provided.

Install

How do I install the bot.ranch/mcp-server server?

bot.ranch/mcp-server runs locally as an npm package, launched with npx -y @ranchbot/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @ranchbot/mcp-server

# add to Claude Code
claude mcp add bot-ranch-mcp-server -- npx -y @ranchbot/mcp-server
Common questions

What is the bot.ranch/mcp-server server?

bot.ranch/mcp-server is listed in the public MCP registry as bot.ranch/mcp-server. Read and write cattle and sheep records with farm-scoped, revocable access. This page covers its npm package (@ranchbot/mcp-server).

Is the bot.ranch/mcp-server server safe to use?

bot.ranch/mcp-server scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the bot.ranch/mcp-server server expose?

bot.ranch/mcp-server exposes 82 tools: farm_archive, list_my_farms, get_farm, set_default_farm, get_current_context, and 77 more. Their descriptions and schemas cost roughly 7,996 tokens of context every time the server is loaded.

Is the bot.ranch/mcp-server server still maintained?

bot.ranch/mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the bot.ranch/mcp-server server under?

bot.ranch/mcp-server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the bot.ranch/mcp-server server?

VerifyMCP ran 16 checks on bot.ranch/mcp-server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.