Spoofy MCP server
social.spoofy/mcpspoofy.socialstreamable-httpv1.2.0Scanned
Quote and order followers, views, likes and members for any public link, with spend caps.
17 tools: 8 can delete or cancel things, 1 change things and 8 only read.
- Reads private data · 0
- Reads text others write · 8
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
8 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Spoofy MCP server can do
The Spoofy MCP server is published by spoofy.social, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (8 tools: place_order, place_orders, cancel_order, create_automation and 4 more) and create or change data (1 tool: pause_automation). 8 tools only read.
8 tools bring in text other people can write (place_order, place_orders, cancel_order and 5 more).
The fixed checks matched 1 finding (long-description). 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 8, 2026, version 1.2.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.
17 tools
Deletes or cancels 8Claude Code: deny
add_automation_linkFor an automation of kind per_link ("a new post each run"): the link of its next run — the new post, video or track the user wants it on.Reads text others writeNo findings
Why it is in this group
- The name "add_automation_link" says "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it For an automation of kind per_link ("a new post each run"): the link of its next run — the new post, video or track the user wants it on. The run goes out at once as an ordinary order at the price on sale (a move since moves the plan with it), charged from the balance (one run of the plan the user already agreed to; nothing else is charged). The link must be one the plan takes (its platform and kind: a post plan takes posts, never a profile or a token page), and each link takes one run only. Errors: not_per_link, wrong_platform / wrong_link_kind (the message says what the plan takes), link_already_used, no_runs_left, automation_ended, automation_paused. A short balance keeps the run waiting and pauses the plan until a top-up covers it; it then goes by itself.
Annotations the server declares
- title: Send a post to a plan (spends one run)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
cancel_automationStop an automation for good: every future run is cancelled.Reads text others writeNo findings
Why it is in this group
- The name "cancel_automation" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Stop an automation for good: every future run is cancelled. Orders already running finish, unless cancel_running: true asks those that allow it to cancel too (the undelivered part is refunded). Confirm with the user first.
Annotations the server declares
- title: Cancel an automation
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
cancel_orderAsk to cancel a pending or processing order (only when the order says cancelable: true).Reads text others writeNo findings
Why it is in this group
- The name "cancel_order" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Ask to cancel a pending or processing order (only when the order says cancelable: true). Whatever was not delivered is refunded to the balance in USD. Confirm with the user first.
Annotations the server declares
- title: Cancel an order
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
create_automationSet up an automation: Spoofy places ordinary orders for the user on a plan.Reads text others write1 finding
Why it is in this group
- The name "create_automation" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,874 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...tions, over_order_cap / platform_not_allowed / read_only_key (this key's limits)."
Description, as the server wrote it Set up an automation: Spoofy places ordinary orders for the user on a plan. Kinds: spread (a total over time, e.g. {"kind":"spread","service":12,"link":"…","quantity":10000,"over":"3d"}; pace "steady" or "front" for an S-curve growth plan, "launch" for about half straight away then each run smaller), scheduled (one order at start_at), recurring (every "1d"/"6h"/"1w", optional at "14:00" + timezone, with times, until or budget), split (past one order's max), campaign (steps [{service, link, quantity, offset_minutes, over_minutes}] or template: "token-launch" + links), keep_above (target + days + budget; public Telegram channels/groups and YouTube videos only), feed (a public Telegram channel, YouTube channel, CoinMarketCap Community profile, Pinterest profile or board, Bluesky account, Reddit user or subreddit, RSS feed, or an X account while X's API is on: every new post gets quantity of service — or quantity_min + quantity_max, a random whole number in that range for each post; spread_minutes (30–360) + parts (2–10) splits each post's order into parts at random times within the window, each at least the service's minimum (pace "launch": the first part about half); delay_min_minutes + delay_max_minutes start it a random number of minutes after the post; posts: the next N posts, then it completes — "likes on my next 30 posts" is posts 30, no days needed; max_per_day; budget, needed only without posts; change them later with update_automation), per_link (a new post each run: service, quantity each run, runs, optional every "daily" + at "14:00" and days; no link now — each run goes out when its post's link is sent with add_automation_link; runs not used are never charged). For new posts elsewhere (Instagram, TikTok …) order an "On new posts" service instead (find_services; fields username, min, max, posts, delay): the provider watches the account. Service ids come from find_services. THIS SPENDS THE USER'S REAL BALANCE: each run is charged when it goes, at the price on sale then — a price that moves while it runs moves the plan with it (a rise is emailed to the user and the automation keeps running; it never pauses for a price). Call first without confirm (or with dry_run: true): you get the plan — every run's time, size and cost at today's price, the total and the balance. Tell the user the total and timing, and this line: "Prices follow our costs and can change while it runs; we’ll email you if they go up, and you can stop it any time." — get their explicit OK, then call again with confirm: true and an idempotency_key. Errors: bad_automation / bad_schedule (the message says what to change), budget_required, count_not_readable (keep_above only reads those links), bad_feed (a feed Spoofy does not read; X only while its API is on), too_many_automations, over_order_cap / platform_not_allowed / read_only_key (this key's limits).
Annotations the server declares
- title: Set up an automation (spends balance as it runs)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
place_orderPlace an order.Reads text others writeNo findings
Why it is in this group
- The description says "cannot be undone".
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Place an order. THIS SPENDS THE USER'S REAL BALANCE (USD) and starts delivery to the link; it cannot be undone except by cancel_order where the service allows it. Before calling: get the price with get_quote and get the user's explicit agreement to that price. Then call with `confirm: true`. Without `confirm: true` nothing is charged and you get the price back so you can ask. `dry_run: true` validates everything (link fits the service, quantity range, key limits) and returns price, balance and whether it is enough — never charges. Pass a fresh `idempotency_key` per intended order so a retry never charges twice. Errors: insufficient_balance (details.shortfall = USD to top up — call get_top_up_info), over_order_cap / over_daily_cap / platform_not_allowed / read_only_key (this key's limits), wrong_platform, bad_quantity, link_busy (too many running on that link: details.available), chain_not_supported. Services with an `input` (find_services) take their fields in `inputs`: `comments` (custom comments, one per line or a list — their number is the quantity), `usernames` (accounts to mention), `hashtag`, `username`, `answer_number` (poll option, 1 = first), `runs` + `interval` (spread out; quantity is per run), or subscription terms (`min`, `max`, `posts`, `old_posts`, `delay`, `expiry`: auto-engagement on future posts, paid up front for at most max × posts). Text we post for the user is checked first: text_blocked = refused, nothing charged; a dry run says `text_review: true` when our team may check it before it starts. Errors also: bad_inputs, inputs_required. Done-for-you services (kind "manual": listings) need a form with images — those are ordered on the website.
Annotations the server declares
- title: Place an order (spends balance)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
place_ordersPlace up to 25 orders in one go — several services, one link or several — paid together from the balance.Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Place up to 25 orders in one go — several services, one link or several — paid together from the balance. THIS SPENDS THE USER'S REAL BALANCE (USD) and starts delivery. Use it when the user wants several things at once (e.g. followers + likes + views for one account); for one order use place_order. Every order is checked first at today's price: if any one cannot go (link does not fit, quantity out of range, too many running on one link, balance short…) NONE is placed and each item says why. Then they are placed one by one; should one fail at that very moment, the others stay placed and that one says why (nothing charged for it). Without `confirm: true` nothing is charged: you get each price and the total so you can ask the user. With `confirm: true` also pass `max_total` = the total the user agreed to; if prices moved above it nothing is placed (price_changed). Pass a fresh `idempotency_key` per intended batch: a retry with the same key never places an order twice. Each item takes what place_order takes: `service`, `link`, `quantity`, or `inputs` for services with an `input`. Errors: batch_invalid (details.items says which and why), insufficient_balance (details.shortfall = USD to top up — call get_top_up_info), order_rate_limited, over_daily_cap, price_changed, idempotency_conflict.
Annotations the server declares
- title: Place several orders at once (spends balance)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
resume_automationCarry on with a paused automation: the rest of the plan moves by the time it was paused.Reads text others writeNo 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).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Carry on with a paused automation: the rest of the plan moves by the time it was paused. Its runs are charged as they go, at the price on sale then — tell the user first.
Annotations the server declares
- title: Resume an automation
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
update_automationChange a new-post automation's settings (kind feed) while it runs, as PATCH /api/v1/automations/{id} takes them: each post's amount — quantity, or quantity_min + quantity_max (each…Reads text others writeNo findings
Why it is in this group
- The name "update_automation" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Change a new-post automation's settings (kind feed) while it runs, as PATCH /api/v1/automations/{id} takes them: each post's amount — quantity, or quantity_min + quantity_max (each post gets a random whole number in the range, within one delivery of the service) —, spread_minutes (30–360; 0 = all at once) + parts (2–10: each post's order in parts at random times within the window, each part at least the service's minimum, fewer parts for a small amount) and their pace (even, or "launch": the first part about half), delay_min_minutes + delay_max_minutes (the first part a random number of minutes after the post), posts (the next N posts), max_per_day and budget. Changes apply to posts found from now on; parts already planned keep their plan. Each part is charged the price on sale when it goes. Call first without confirm: you get the settings in words and what they can cost. Tell the user. When they can cost more than its limit (change.budget.raise), the user must agree to the higher limit: then call with confirm: true and settings.confirm_budget: true (or a budget the user chose). Errors: not_editable (another kind, or it has ended), bad_quantity (outside one delivery of the service), bad_automation / bad_schedule (the message says what to change), confirm_budget (the limit would rise without the user's yes).
Annotations the server declares
- title: Change a new-post automation (can raise what it spends)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
pause_automationStop placing new runs until it is resumed (orders already running keep delivering).No findings
Why it is in this group
- The description's first verb is "stop": a word for a change.
Description, as the server wrote it Stop placing new runs until it is resumed (orders already running keep delivering). Nothing is charged while paused.
Annotations the server declares
- title: Pause an automation
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 8Show 8 read-only tools
find_servicesFind what Spoofy can do for a link or a goal, with prices.No findings
Why it is in this group
- The name "find_services" says "find": a word for reading.
Description, as the server wrote it Find what Spoofy can do for a link or a goal, with prices. ALWAYS call this first: service ids come from here. Give `link` (any profile, post, video, channel, group, token page or website URL) and/or `goal` in plain words, e.g. "500 followers on my tiktok" or "cheap views for this YouTube video". With a link you only get services that fit that exact link (a profile link gets followers, a post link gets likes/views). Returns matching services: `service` (the id to quote/order), name, tier (basic/standard/premium), pricePer1k (USD per 1,000 units), min/max quantity, start time, speed, preset packages with USD prices, and — when the goal names a quantity — a `suggestion` with the exact total for that quantity. A service with an `input` needs those fields in place_order `inputs` (custom comments, accounts to mention, a hashtag, a poll option, runs, subscription terms); `input.quantity` says where the quantity comes from. `query` narrows to services whose words match, e.g. "usa", "brazil", "real", "story". Free; spends nothing. On every service, counts can drop after delivery and drops are not replaced — tell the user before they buy followers, members or likes.
Annotations the server declares
- title: Find services
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_automationOne automation with its timeline: every run, the order it placed and what that delivered, or why a run waits or was skipped (balance, budget, a daily limit).No findings
Why it is in this group
- The name "get_automation" says "get": a word for reading.
Description, as the server wrote it One automation with its timeline: every run, the order it placed and what that delivered, or why a run waits or was skipped (balance, budget, a daily limit).
Annotations the server declares
- title: Get an automation
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_balanceThe user's spendable balance in USD.No findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
Description, as the server wrote it The user's spendable balance in USD. Orders are paid from it.
Annotations the server declares
- title: Get balance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_orderStatus and progress of one order: status (pending, processing, completed, partial, refunded, cancelled, failed), start count, delivered, remains, charge and refunds in USD, and whe…No findings
Why it is in this group
- The name "get_order" says "get": a word for reading.
Description, as the server wrote it Status and progress of one order: status (pending, processing, completed, partial, refunded, cancelled, failed), start count, delivered, remains, charge and refunds in USD, and whether it can be cancelled now.
Annotations the server declares
- title: Get an order
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_quoteExact price in USD for a quantity of one service (from find_services).No findings
Why it is in this group
- The name "get_quote" says "get": a word for reading.
Description, as the server wrote it Exact price in USD for a quantity of one service (from find_services). Checks the quantity is within the service range. Free; spends nothing. Use it to tell the user the cost before place_order. For services with an `input`, pass the same `inputs` as for place_order; the quantity is then the units charged: the number of comments or usernames, per run × runs, or for subscriptions max × (posts + old_posts).
Annotations the server declares
- title: Get a quote
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_top_up_infoHow the user adds money to the balance: stablecoins (USDC, USDT or USDG, on the networks that are on), credited 1 coin = $1, and native coins (methods with native: true — SOL on So…No findings
Why it is in this group
- The name "get_top_up_info" says "get": a word for reading.
Description, as the server wrote it How the user adds money to the balance: stablecoins (USDC, USDT or USDG, on the networks that are on), credited 1 coin = $1, and native coins (methods with native: true — SOL on Solana, ETH on Ethereum, while they are on), credited at their US-dollar value when they arrive (the market price then; priceUsd is only an estimate). Each goes to the user's own deposit address — one address for every EVM network, another on Solana. Also gives the top-up page link. Use it when an order fails with insufficient_balance. Tell the user to send only the listed coin on the listed network. You cannot move money yourself — give the user the address or the link.
Annotations the server declares
- title: How to top up
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_automationsThe user's automations, newest first, with progress (runs placed, delivered), spend against budget and the next run.No findings
Why it is in this group
- The name "list_automations" says "list": a word for reading.
Description, as the server wrote it The user's automations, newest first, with progress (runs placed, delivered), spend against budget and the next run. Filter by status.
Annotations the server declares
- title: List automations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_ordersThe user's orders, newest first.No findings
Why it is in this group
- The name "list_orders" says "list": a word for reading.
Description, as the server wrote it The user's orders, newest first. Filter by status; page with `before` = the smallest order number already seen.
Annotations the server declares
- title: List orders
- 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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.
Looked at Nov 20, 2026, 19:19 UTC, unchanged since Oct 29, 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
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://spoofy.social/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://spoofy.social
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (8 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://spoofy.social/mcp: tools/list returned 17 tools to an anonymous client, including place_order (destructive), place_orders (destructive), cancel_order (destructive), create_automation (destructive), update_automation (destructive) and 4 more
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 7 to 9
Findings
Matches of fixed checks, with the text they matched.
The description is 2,874 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...tions, over_order_cap / platform_not_allowed / read_only_key (this key's limits)."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 added, 3 changed.+2 added~3 changedView diff
- Added:add_automation_linkDeletes or cancels
- Added:update_automationDeletes or cancels
- Changed:create_automationDeletes or cancelsdescription
- Changed:get_top_up_infoOnly readsdescription
- Changed:resume_automationDeletes or cancelsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 9.View diff
- Tools that change things, listed without credentials: 7 to 9
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http spoofy https://spoofy.social/mcpclaude mcp add --transport http spoofy https://spoofy.social/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__spoofy__find_services",
"mcp__spoofy__get_quote",
"mcp__spoofy__get_order",
"mcp__spoofy__list_orders",
"mcp__spoofy__get_balance",
"mcp__spoofy__get_top_up_info",
"mcp__spoofy__list_automations",
"mcp__spoofy__get_automation"
],
"ask": [
"mcp__spoofy__pause_automation"
],
"deny": [
"mcp__spoofy__place_order",
"mcp__spoofy__place_orders",
"mcp__spoofy__cancel_order",
"mcp__spoofy__create_automation",
"mcp__spoofy__update_automation",
"mcp__spoofy__resume_automation",
"mcp__spoofy__cancel_automation",
"mcp__spoofy__add_automation_link"
]
}
}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 spoofy. Review it before you use it.
Capability tags behind 8 rules
- mcp__spoofy__place_order untrusted-input
- mcp__spoofy__place_orders untrusted-input
- mcp__spoofy__cancel_order untrusted-input
- mcp__spoofy__create_automation untrusted-input
- mcp__spoofy__update_automation untrusted-input
- mcp__spoofy__resume_automation untrusted-input
- mcp__spoofy__cancel_automation untrusted-input
- mcp__spoofy__add_automation_link untrusted-input
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/social.spoofy/mcp/verify?hash=95daee470d40e10b35e35a9ec3bdd075f23cbd41db8074c9a726ba28d942c219" | jq -e '.changed == false'Pinned hash 95daee470d40, from Nov 8, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/social.spoofy/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/social.spoofy/mcp)Source: MCP Registry. Synced Oct 23, 2026, 04:18 UTC.
Spoofy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Spoofy MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 9 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Spoofy MCP server delete data?
- Yes. 8 tools can delete, cancel or revoke something: place_order, place_orders, cancel_order, create_automation, update_automation, resume_automation and 2 more.
Can the Spoofy MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Spoofy MCP server have?
- 17 tools: 8 destructive, 1 write, 8 read. place_order, place_orders, cancel_order, create_automation, update_automation, resume_automation, cancel_automation, add_automation_link and 9 more.
Does the Spoofy MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Spoofy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Spoofy MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.