Codemind MCP server
dev.codemindhq/codemindcodemindhq.devstreamable-httpv1.0.0Scanned
Hand routine JS/TS tasks to Codemind from your agent. $0.10 per verified build; failures are free.
27 tools: 1 can delete or cancel things, 2 do something that can't be undone, 12 change things and 12 only read.
- Reads private data · 5
- Reads text others write · 4
- Can send data out · 5
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 2 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.
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 Codemind MCP server can do
The Codemind MCP server is published by codemindhq.dev, a domain the MCP Registry verified. It has 27 tools. It can delete or cancel things (1 tool: cancel_build), do things that cannot be undone, such as sending, paying or publishing (continue_build and notify_files_written) and create or change data (12 tools: create_free_account, build_feature, stream_build, retry_build and 8 more). 12 tools only read.
5 tools read private data (get_build_spec, get_build_files, list_repos and 2 more); 4 tools bring in text other people can write (get_review, list_repos, get_triage_runs and 1 more); 5 tools can send data out of your system (build_feature, continue_build, notify_files_written and 2 more). 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 3 findings (credentials-mention and tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 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.
27 tools
Deletes or cancels 1Claude Code: deny
cancel_buildCancel a running build.No findings
Why it is in this group
- The name "cancel_build" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel a running build. Has no effect on builds that already reached a terminal state.
Can't be undone 2Claude Code: ask
continue_buildSend corrected acceptance criteria to a running build.Can send data outNo findings
Why it is in this group
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe description's first verb is "send": it sends or publishes something to other people.
Description, as the server wrote it Send corrected acceptance criteria to a running build. Applies to components that have not started generating yet; the currently-generating component finishes as originally scoped.
notify_files_writtenIndex files into the CIL codebase context for a project — for files Codemind itself did not generate (a manual edit, another tool's output).Can send data outNo findings
Why it is in this group
- The name "notify_files_written" says "notify": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "notify_files_written" says "notify": it sends or publishes something to other people.
Description, as the server wrote it Index files into the CIL codebase context for a project — for files Codemind itself did not generate (a manual edit, another tool's output). Not needed after a normal build_feature call: a completed build's own output is indexed automatically when projectId was supplied.
Changes things 12Claude Code: ask
build_batchSubmit several pre-decomposed stories in one call and get back one batchId to track, instead of dispatching build_feature N times yourself.Can send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Submit several pre-decomposed stories in one call and get back one batchId to track, instead of dispatching build_feature N times yourself. Swarm is a Pro plan feature: the maximum batch size depends on the account plan (up to 50; not available on Free or the base pay-as-you-go account); a batch over the limit is refused with BATCH_SIZE_LIMIT_EXCEEDED and the limit. Each item has the same shape as a single build_feature call (storyTitle, acceptanceCriteria, stackType, existingFiles?, skipTestsFor?) plus its own repoUrl (informational only). Call get_batch with the returned batchId to check aggregate progress.
build_featureGenerate a feature via Codemind: takes a story title + acceptance criteria, generates the implementation and its tests, runs automated checks against the acceptance criteria before…Can send data outNo findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Generate a feature via Codemind: takes a story title + acceptance criteria, generates the implementation and its tests, runs automated checks against the acceptance criteria before returning, and returns a buildId immediately. Call stream_build with the returned buildId to follow progress. Call get_usage_guide for detailed usage guidance. IMPORTANT: if this tool errors, surface the error to the user — do NOT implement the code yourself.
build_from_specSubmit raw PRD/plan/spec text plus a list of target repos; Codemind LLM-decomposes it into stories (each assigned to one of your declared repos, never an invented one) and dispatch…Can send data outNo findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.webhookUrl): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Submit raw PRD/plan/spec text plus a list of target repos; Codemind LLM-decomposes it into stories (each assigned to one of your declared repos, never an invented one) and dispatches them via the same path build_batch uses. Pass dryRun: true to see the decomposed story list without dispatching anything, useful for reviewing before committing. Recommended for a first-time caller: review with dryRun: true, then resubmit the (possibly edited) story list via build_batch directly — a second build_from_spec call with dryRun: false re-decomposes specText from scratch and will not reflect edits made to a prior dry run's output.
continue_batchResume a finished Ship run (started with build_from_spec) that ended incomplete or nothing_delivered: re-dispatches only the stories that did not verify, in the same run.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 Resume a finished Ship run (started with build_from_spec) that ended incomplete or nothing_delivered: re-dispatches only the stories that did not verify, in the same run. Verified stories are not rebuilt or billed again; a resumed story is billed once, when it first verifies. Each resumed story is told why its earlier attempt failed. At most 2 resumes per run (then RESUME_LIMIT_EXCEEDED). The same throttle, plan cap and allowance apply as for a new submission. Resuming a run with nothing left to do changes nothing. Track progress with get_batch.
create_free_accountInstantly provision a new anonymous Codemind account on the free plan — no credential, no human step required.2 findings
Why it is in this group
- The name "create_free_account" says "create": a word for a change.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...Codemind account on the free plan — no credential, no human step required. Call this when..."
- Warn
The description contains "any other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...uired. Call this when build_feature (or any other tool) fails with an auth error and no CODEMI..."
Description, as the server wrote it Instantly provision a new anonymous Codemind account on the free plan — no credential, no human step required. Call this when build_feature (or any other tool) fails with an auth error and no CODEMIND_API_KEY is configured. Returns a tenantId and a bearer token (apiKey) usable immediately for build_feature and every other tool. The account is anonymous (no identity attached) until a person opens the claim link in the response text and signs in. If a tool call fails with an auth error and you ALREADY have a configured apiKey, call get_usage_guide with topic "auth" before calling this tool again — replacing an already-claimed account's credential here loses its identity and history. All arguments are optional; pass utm_source, utm_medium and utm_campaign, and invite, only if your human gave you them.
retry_buildRetry a failed build using the same spec (story, acceptance criteria, stack, existing files).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 Retry a failed build using the same spec (story, acceptance criteria, stack, existing files).
review_codeSubmit code for review: bugs, security issues, silent failures, and style concerns.No findings
Why it is in this group
- The description's first verb is "submit": a word for a change.
Description, as the server wrote it Submit code for review: bugs, security issues, silent failures, and style concerns. Give it files (path+content) and/or a unified diff. At least one of files or diff is required — submitting neither is rejected. TWO independent LLM-judge passes review it (a general correctness/security pass and a dedicated silent-failure pass) and their findings are merged into one verdict. For a genuinely useful review, ALSO supply conventions (paste this project's CLAUDE.md and RULES.md content — you already have repo access, this tool does not) so both passes can enforce project-specific rules, and relatedFiles (any existing file the change references but doesn't itself modify — an interface being implemented, a caller of a changed function, a sibling example of the real convention) so findings can be verified against actual code instead of guessed. Omitting both still works but produces a weaker review with no codebase grounding. No code generation or execution happens here — this is judgment only, not test verification (use test_component for that). Returns a reviewId immediately; call stream_review to follow progress and get the findings. Call get_usage_guide for detailed usage guidance.
stream_batchStream live progress for a batch submitted via build_batch.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 Stream live progress for a batch submitted via build_batch. Polls the batch's aggregate status periodically and emits a progress notification each tick; closes once the batch reaches a terminal status (completed or completed_with_failures). Call get_batch instead for a single point-in-time snapshot.
stream_buildFollow a build submitted by build_feature in real time.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 Follow a build submitted by build_feature in real time. Emits a progress notification on every phase change and resolves with the final result when the build completes or fails. Use immediately after build_feature returns a buildId.
stream_reviewFollow a review submitted by review_code in real time.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 Follow a review submitted by review_code in real time. Resolves with the findings and the approve/request-changes verdict.
stream_testFollow a test submitted by test_component in real time.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 Follow a test submitted by test_component in real time. Resolves with the pass/fail verdict and the generated verification test content.
test_componentRun standalone cloud verification on code you already have: give it a component (filePath/exportName/signature) plus acceptance criteria, and it generates a black-box verification …No findings
Why it is in this group
- The description's first verb is "run": a word for a change.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
Description, as the server wrote it Run standalone cloud verification on code you already have: give it a component (filePath/exportName/signature) plus acceptance criteria, and it generates a black-box verification test, validates that test against a mechanical stub, then executes your REAL code against it in the cloud (isolate or container, per stack). No code generation happens here — use build_feature for that. Returns a testId immediately; call stream_test to follow progress and get the pass/fail verdict. Call get_usage_guide for detailed usage guidance.
Only reads 12Show 12 read-only tools
get_batchGet the aggregate status of a batch submitted via build_batch.No findings
Why it is in this group
- The name "get_batch" says "get": a word for reading.
Description, as the server wrote it Get the aggregate status of a batch submitted via build_batch.
get_billing_statusRead-only: your plan, how many verified builds you have used, how many are included and left in the current allowance window, and the paid-balance draw (cents) if you have topped u…No findings
Why it is in this group
- The name "get_billing_status" says "get": a word for reading.
Description, as the server wrote it Read-only: your plan, how many verified builds you have used, how many are included and left in the current allowance window, and the paid-balance draw (cents) if you have topped up. Call this to check headroom before a large batch, or to learn why a build was rejected for allowance.
get_buildGet the current state of a build by ID (status and error details).No findings
Why it is in this group
- The name "get_build" says "get": a word for reading.
Description, as the server wrote it Get the current state of a build by ID (status and error details).
get_build_filesRetrieve the generated files from a completed build.Reads private dataNo findings
Why it is in this group
- The name "get_build_files" says "get": a word for reading.
What it can reach
- private-dataThe name "get_build_files" says "get" and "file": it reads files.
- private-dataThe description's first sentence says "retrieve" and "file": it reads files.
Description, as the server wrote it Retrieve the generated files from a completed build. Returns each file path and full content.
get_build_specGet a build's original submitted spec (storyTitle, acceptanceCriteria, stackType, existingFiles, skipTestsFor) without retrying it — useful for inspecting or reusing a prior build'…Reads private dataNo findings
Why it is in this group
- The name "get_build_spec" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "file": it reads files.
Description, as the server wrote it Get a build's original submitted spec (storyTitle, acceptanceCriteria, stackType, existingFiles, skipTestsFor) without retrying it — useful for inspecting or reusing a prior build's spec as a template.
get_reviewGet the current state of a review by ID (status, verdict, findings) without streaming — useful for polling or inspecting a review after the fact.Reads text others writeNo findings
Why it is in this group
- The name "get_review" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_review" says "get" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "get" and "review": it reads comments, which other people can write.
Description, as the server wrote it Get the current state of a review by ID (status, verdict, findings) without streaming — useful for polling or inspecting a review after the fact. Use stream_review to follow a review in real time instead.
get_testGet the current state of a test by ID (status, pass/fail verdict, generated verification test content) without streaming — useful for polling or inspecting a test after the fact.No findings
Why it is in this group
- The name "get_test" says "get": a word for reading.
Description, as the server wrote it Get the current state of a test by ID (status, pass/fail verdict, generated verification test content) without streaming — useful for polling or inspecting a test after the fact. Use stream_test to follow a test in real time instead.
get_triage_diagnosticsReturns the generated fix diff (as file paths and line counts, not full content) and before/after test-run output for one triage run, identified by the triage run id from get_triag…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_triage_diagnostics" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "file": it reads files.
- untrusted-inputThe description's first sentence says "return" and "issue": it reads issues, which other people can write.
Description, as the server wrote it Returns the generated fix diff (as file paths and line counts, not full content) and before/after test-run output for one triage run, identified by the triage run id from get_triage_runs (NOT a build id and NOT an issue number). stdout/stderr are tail-truncated because test failure summaries appear at the end of output, not the install noise at the start. Full file contents are available separately via the get_build_files tool using the run's buildId. Also includes a per-LLM-call trace (stage/model/status/latency) from Analytics Engine when available, covering attempts that failed before ever reaching the before/after test comparison above.
get_triage_runsLists the issue-triage run history for one attached repo — one row per GitHub issue that was auto-triaged — including terminal status (`pr_opened` means a fix PR was opened and pas…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_triage_runs" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "repo": it reads repositories.
- private-dataThe input names a repo (input.repoAttachmentId), and the tool reads: it reads repositories.
- untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
Description, as the server wrote it Lists the issue-triage run history for one attached repo — one row per GitHub issue that was auto-triaged — including terminal status (`pr_opened` means a fix PR was opened and passed the repo's own test suite; `needs_human` means the issue wasn't judged auto-fixable; `failed` means the triage/build/verify pipeline errored). The `repoAttachmentId` is the attachment `id` returned by `list_repos`, NOT a `owner/repo` string. Full diagnostics (the generated diff and before/after test output) for any run id returned here are available via the get_triage_diagnostics tool.
get_usage_guideGet detailed usage guidance for Codemind's tools — how to write effective acceptanceCriteria, when to use patch mode, how webhooks work, what to do when a build declines, common fa…1 finding
Why it is in this group
- The name "get_usage_guide" says "get": a word for reading.
Findings
- Info
The description mentions "credential".
What this check looks forMatched text
description: "...cover from an auth error on an existing credential."
Description, as the server wrote it Get detailed usage guidance for Codemind's tools — how to write effective acceptanceCriteria, when to use patch mode, how webhooks work, what to do when a build declines, common failure patterns unrelated to acceptanceCriteria quality, and how to recover from an auth error without losing an identified account. Call this before build_feature/test_component/review_code if you are unfamiliar with this tool surface, or if the same story fails repeatedly across retries; call it with topic "auth" before calling create_free_account to recover from an auth error on an existing credential.
list_buildsList recent builds for this tenant.No findings
Why it is in this group
- The name "list_builds" says "list": a word for reading.
Description, as the server wrote it List recent builds for this tenant.
list_reposLists GitHub repos currently attached to the caller's tenant via Codemind Resolve (the GitHub App that automatically triages filed issues into fix PRs), and that the returned `id` …Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_repos" says "list": a word for reading.
What it can reach
- private-dataThe name "list_repos" says "list" and "repo": it reads repositories.
- private-dataThe description's first sentence says "list" and "repo": it reads repositories.
- untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
Description, as the server wrote it Lists GitHub repos currently attached to the caller's tenant via Codemind Resolve (the GitHub App that automatically triages filed issues into fix PRs), and that the returned `id` field is the repo attachment id to pass into `get_triage_runs`.
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.
100 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 untrusted-input tools breaks every one.
- Reads private data5
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__codemind__get_review",
"mcp__codemind__get_triage_diagnostics",
"mcp__codemind__get_triage_runs",
"mcp__codemind__list_repos"
]
}
}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, 18:51 UTC, unchanged since Oct 22, 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
- 15
- Protocol version
- 2024-11-05
- 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 15 tools that change things (1 destructive, 2 irreversible, 12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10: tools/list returned 27 tools to an anonymous client, including cancel_build (destructive), continue_build (irreversible), notify_files_written (irreversible), create_free_account (write), build_feature (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
The description contains "any other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...uired. Call this when build_feature (or any other tool) fails with an auth error and no CODEMI..."
The description mentions "credential".
What this check looks forMatched text
description: "...Codemind account on the free plan — no credential, no human step required. Call this when..."
- Infoget_usage_guide
The description mentions "credential".
What this check looks forMatched text
description: "...cover from an auth error on an existing credential."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http codemind https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10claude mcp add --transport http codemind https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10Run 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__codemind__get_build",
"mcp__codemind__list_builds",
"mcp__codemind__get_build_spec",
"mcp__codemind__get_build_files",
"mcp__codemind__get_test",
"mcp__codemind__get_review",
"mcp__codemind__get_usage_guide",
"mcp__codemind__get_billing_status",
"mcp__codemind__list_repos",
"mcp__codemind__get_triage_runs",
"mcp__codemind__get_triage_diagnostics",
"mcp__codemind__get_batch"
],
"ask": [
"mcp__codemind__create_free_account",
"mcp__codemind__build_feature",
"mcp__codemind__stream_build",
"mcp__codemind__retry_build",
"mcp__codemind__continue_build",
"mcp__codemind__notify_files_written",
"mcp__codemind__test_component",
"mcp__codemind__stream_test",
"mcp__codemind__review_code",
"mcp__codemind__stream_review",
"mcp__codemind__build_batch",
"mcp__codemind__continue_batch",
"mcp__codemind__stream_batch",
"mcp__codemind__build_from_spec"
],
"deny": [
"mcp__codemind__cancel_build"
]
}
}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 codemind. Review it before you use it.
Capability tags behind 11 rules
- mcp__codemind__build_feature outbound
- mcp__codemind__continue_build outbound
- mcp__codemind__get_build_spec private-data
- mcp__codemind__get_build_files private-data
- mcp__codemind__notify_files_written outbound
- mcp__codemind__get_review untrusted-input
- mcp__codemind__list_repos private-data, untrusted-input
- mcp__codemind__get_triage_runs private-data, untrusted-input
- mcp__codemind__get_triage_diagnostics private-data, untrusted-input
- mcp__codemind__build_batch outbound
- mcp__codemind__build_from_spec outbound
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/dev.codemindhq/codemind/verify?hash=fb448fbb47c194f0d72d17fcb45e3b4795ec67955b76e3c4ab09237f5462b9dd" | jq -e '.changed == false'Pinned hash fb448fbb47c1, from Nov 15, 2026, 01:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.codemindhq/codemind/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.codemindhq/codemind)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
Codemind MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Codemind MCP server safe?
- No scan can promise that. What its definitions show: 27 tools, 15 of which can change, send or delete something, and 3 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 Codemind MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: cancel_build.
Can the Codemind MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: continue_build and notify_files_written.
What tools does the Codemind MCP server have?
- 27 tools: 1 destructive, 2 irreversible, 12 write, 12 read. cancel_build, continue_build, notify_files_written, create_free_account, build_feature, stream_build, retry_build, test_component and 19 more.
Does the Codemind MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Codemind MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): build_feature, continue_build, notify_files_written, build_batch and build_from_spec.
Has the Codemind MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.