Skip to content

Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server

com.forevenza.services/balconesapiaryservices.forevenza.comstreamable-httpv1.0.0Scanned

Request managed hive placement, ongoing care and Texas agricultural valuation documentation

18 tools: 1 can delete or cancel things, 4 do something that can't be undone, 9 change things and 4 only read.

Tools: 1 delete, 4 irreversible, 9 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 2
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 4 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server can do

The Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server is published by services.forevenza.com, a domain the MCP Registry verified. It has 18 tools. It can delete or cancel things (1 tool: decline_offer), do things that cannot be undone, such as sending, paying or publishing (submit_request, send_requirement, release_payment and submit_purchase_order) and create or change data (9 tools: interpret_requirement, edit_requirement, request_status, accept_offer and 5 more). 4 tools only read.

2 tools read private data (inspect_offer and report_vendor_status); 1 tool brings in text other people can write (inspect_offer); 2 tools can send data out of your system (submit_request and send_requirement). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 6 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

18 tools

Deletes or cancels 1Claude Code: deny
  • decline_offerDecline an issued offer on its inspected terms.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Decline an issued offer on its inspected terms.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
Can't be undone 4Claude Code: ask
  • release_paymentConfirm a payment condition only where the inspected order allows the customer to release it.No findings

    Why it is in this group

    • The name "release_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • send_requirementSend the requirement to Balcones Apiary Co.Can send data outNo findings

    Why it is in this group

    • The name "send_requirement" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_requirement" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send the requirement to Balcones Apiary Co. once the buyer says to: the first send records the request (its receipt token is the requirement's token, for request_status and offers); a later send of a changed requirement records a revision of the same request. Name the revision the buyer saw. This orders nothing: an offer comes later and is accepted separately on its exact terms.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • submit_purchase_orderSend the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms.No findings

    Why it is in this group

    • The name "submit_purchase_order" says "submit": a word for a change.
    • The name "submit_purchase_order" also says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Send the buyer's purchase order for an issued offer or a placed order: number, revision, lines, total, currency and payment terms. It is matched against the accepted terms; differences are recorded and shown in inspect_offer thread.purchasing as exceptions, never silently accepted. A changed purchase order is the same number with a higher revision. This does not accept the offer and pays nothing.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • submit_requestSend Balcones Apiary Co.Can send data outNo findings

    Why it is in this group

    • The name "submit_request" says "submit": a word for a change.
    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    • The input carries an amount (input.budget.amount) and a currency, so it moves money.
    • The input addresses people (input.geography.to): what it sends cannot be taken back.

    What it can reach

    • outboundThe input takes a destination (input.geography.to): what the tool writes goes there.
    Description, as the server wrote it
    Send Balcones Apiary Co. a requirement (Managed hive placement and agricultural valuation support). A successful submission is recorded with a reference number. When an address is left, Balcones Apiary Co. replies by email. Balcones evaluates district rules, eligible area, history and site needs, seeks placement options and prepares feasibility, a management and documentation scope and proposed written terms. Nothing is ordered or committed until the owner agrees terms. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time. It is answered with a receipt: keep its id and token to read its status (request_status), to add details later (continuation) and to act on an offer made in reply. A requirement is not an order and costs nothing.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 9Claude Code: ask
  • accept_offerPlace an order on terms you have inspected and the buyer has authorized you to accept.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • answer_remedyAccept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Accept or decline a remedy the business proposed on a placed order (inspect_offer thread.fulfilment.remedies with state PROPOSED). Recorded for the business, which applies it and shows the result there. Accepting a credit or refund here moves no money; the business records it when its payment processor does.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • counter_offerPropose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Propose a change to an issued offer on its inspected terms: other quantities (by item index in terms.items), another list of companies (where the items price companies), a delivery date, a total price for the whole, a payment plan, or a note. It is a proposal, not a change: the terms stand and can still be accepted as they are. The business answers it in inspect_offer thread.counteroffers, with a revised offer to inspect and accept, or a reason. A later proposal replaces an earlier one still awaiting an answer. Nothing here orders or pays.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • edit_requirementSet fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading.No findings

    Why it is in this group

    • The name "edit_requirement" says "edit": a word for a change.
    Description, as the server wrote it
    Set fields by name ({"op":"set","values":{...}}, an empty value clears) or change the list ({"op":"add"|"update"|"remove"|"replace", ...}), exactly as given: no reading. Use it to answer the open question when the answer is a value.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • inspect_deliveryRecord the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally…1 finding

    Why it is in this group

    • The name "inspect_delivery" says "inspect": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "inspect_delivery" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "inspect_delivery" says "inspect": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Record the buyer's inspection of a placed order: for each item (its index in terms.items) the quantity accepted and the quantity rejected, with a reason for a rejection, optionally for one portion of the order. Whether it was accepted is computed: only when nothing is rejected. Recorded for the business, which answers a rejection in inspect_offer thread.fulfilment, with a proposed remedy. Nothing here pays or refunds.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • interpret_requirementGive Balcones Apiary Co.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Give Balcones Apiary Co. the buyer's requirement, or a correction or addition to it, in their own words: it is read into a structured requirement (each value says which words it came from), conflicting or unclear facts come back as one question, and words not yet read are kept as written. Pass the requirement (id, token) from the first answer to continue it. Nothing is sent or ordered: send_requirement sends it when the buyer says so. When you already have the fields in structured form, use submit_request instead.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • report_vendor_statusReport the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requeste…Reads private data1 finding

    Why it is in this group

    • The name "report_vendor_status" says "status": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.

    Findings

    • Warn

      The server marks "report_vendor_status" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "report_vendor_status" says "status": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Report the seller's vendor standing with the buyer's organization (APPROVED, DOCUMENTS_REQUESTED or REJECTED) with the buyer's approval or case reference and any documents requested. Recorded as the buyer's own statement; the business answers it in inspect_offer thread.purchasing.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_statusResume a requirement using the receipt credentials.2 findings

    Why it is in this group

    • The name "request_status" says "request": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "Resume a requirement using the receipt credentials. Read the recorded requirement, any rep..."

      What this check looks for
    • Warn

      The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Resume a requirement using the receipt credentials. Read the recorded requirement, any replies the business has published on it (messages: where it answers a buyer with no email, it answers here) and any linked offers. Answer a reply by sending a continuation. Contact details are kept apart.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • state_purchasing_requirementsTell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Tell the business how the buyer's purchasing works for this offer: whether the seller must be an approved vendor, whether a purchase order is required, which documents are needed, the seller's vendor id with the buyer, where orders and invoices go, and the payment terms. Recorded as the buyer's statement; the business answers it in inspect_offer thread.purchasing. Nothing here orders or pays.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • describe_businessWhat Balcones Apiary Co.No findings

    Why it is in this group

    • The name "describe_business" says "describe": a word for reading.
    Description, as the server wrote it
    What Balcones Apiary Co. does (Managed hive placement and agricultural valuation support: Arrange a tract-specific beekeeping plan, ongoing colony care and district documentation. Start with known land facts and resolve the remaining questions through a proposal by email.), what happens to a request, what you receive, its price basis (a verified price, an estimate, a method or a scoped quotation; never an offer), when a reply is due, who the buyer contracts with and who invoices, its scope, and the request fields with examples.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_requirementA Balcones Apiary Co.No findings

    Why it is in this group

    • The name "get_requirement" says "get": a word for reading.
    Description, as the server wrote it
    A Balcones Apiary Co. requirement as it stands: each value with where it came from, what it replaced, the open question, words not yet read, whether it was sent and any offer on it.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • inspect_offerRead the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.count…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "inspect_offer" says "inspect": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "thread": it reads messages.
    • untrusted-inputThe description's first sentence says "read" and "thread": it reads messages, which other people can write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...(thread.fulfilment). Use the offer link credentials, or credentials of the request explicit..."

      What this check looks for
    Description, as the server wrote it
    Read the exact authorized terms, terms hash, order state and processor payment links, and the thread the business published on the offer: its answers to counteroffers (thread.counteroffers), the purchasing requirements, vendor status and purchase order matches it holds (thread.purchasing), and the portions, shortfall and remedies of delivery (thread.fulfilment). Use the offer link credentials, or credentials of the request explicitly linked to this offer.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • retrieve_deliverableRetrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall.1 finding

    Why it is in this group

    • The name "retrieve_deliverable" says "retrieve": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...e. Use the offer link or linked request credentials."

      What this check looks for
    Description, as the server wrote it
    Retrieve what a paid order delivers, where the business produces it itself (a report): the exact text, its SHA-256, version, sources and any shortfall. Before payment is confirmed it says it is not yet available. Use the offer link or linked request credentials.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__balconesapiary__inspect_offer"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 14, 2026, 12:20 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
14
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 14 tools that change things (1 destructive, 4 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://balconesapiary.forevenza.com/mcp: tools/list returned 18 tools to an anonymous client, including decline_offer (destructive), submit_request (irreversible), send_requirement (irreversible), release_payment (irreversible), submit_purchase_order (irreversible) and 9 more

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • Tools that change things, listed without credentials: 5 to 14

Findings

Matches of fixed checks, with the text they matched.

3 warn3 info
  • The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.

    What this check looks for
  • The server marks "report_vendor_status" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "report_vendor_status" says "status": a word for reading.

    What this check looks for
  • The server marks "inspect_delivery" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "inspect_delivery" says "inspect": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "Resume a requirement using the receipt credentials. Read the recorded requirement, any rep..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...(thread.fulfilment). Use the offer link credentials, or credentials of the request explicit..."

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...e. Use the offer link or linked request credentials."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools16 added, 2 changed.+16 added~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 5 -> 14.View diff
    • Tools that change things, listed without credentials: 5 to 14

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http balconesapiary https://balconesapiary.forevenza.com/mcp
claude mcp add --transport http balconesapiary https://balconesapiary.forevenza.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__balconesapiary__describe_business",
      "mcp__balconesapiary__get_requirement",
      "mcp__balconesapiary__inspect_offer",
      "mcp__balconesapiary__retrieve_deliverable"
    ],
    "ask": [
      "mcp__balconesapiary__submit_request",
      "mcp__balconesapiary__interpret_requirement",
      "mcp__balconesapiary__edit_requirement",
      "mcp__balconesapiary__send_requirement",
      "mcp__balconesapiary__request_status",
      "mcp__balconesapiary__accept_offer",
      "mcp__balconesapiary__release_payment",
      "mcp__balconesapiary__counter_offer",
      "mcp__balconesapiary__submit_purchase_order",
      "mcp__balconesapiary__state_purchasing_requirements",
      "mcp__balconesapiary__report_vendor_status",
      "mcp__balconesapiary__inspect_delivery",
      "mcp__balconesapiary__answer_remedy"
    ],
    "deny": [
      "mcp__balconesapiary__decline_offer"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as balconesapiary. Review it before you use it.

Capability tags behind 4 rules
  • mcp__balconesapiary__submit_request outbound
  • mcp__balconesapiary__send_requirement outbound
  • mcp__balconesapiary__inspect_offer private-data, untrusted-input
  • mcp__balconesapiary__report_vendor_status private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.forevenza.services/balconesapiary/verify?hash=d8e333ea34152a22a554b8d032b723539ac29b69ccfff1a5c45a09da7fc5c851" | jq -e '.changed == false'

Pinned hash d8e333ea3415, from Nov 20, 2026, 20:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.forevenza.services/balconesapiary/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.forevenza.services/balconesapiary
[![Anlyon Radar](https://radar.anlyon.com/badge/com.forevenza.services/balconesapiary.svg)](https://radar.anlyon.com/servers/com.forevenza.services/balconesapiary)

Source: MCP Registry. Synced Nov 6, 2026, 18:17 UTC.

Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server safe?

No scan can promise that. What its definitions show: 18 tools, 14 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: decline_offer.

Can the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server do things that cannot be undone?

Yes. 4 tools can send, pay, publish or merge: submit_request, send_requirement, release_payment and submit_purchase_order.

What tools does the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server have?

18 tools: 1 destructive, 4 irreversible, 9 write, 4 read. decline_offer, submit_request, send_requirement, release_payment, submit_purchase_order, interpret_requirement, edit_requirement, request_status and 10 more.

Does the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_request and send_requirement.

Has the Balcones Apiary Co.: Managed hive placement and agricultural valuation support MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.