Skip to content

AI Agent Setup Checklist MCP server

dev.workers.agentchecklist.ai-agent-setup-checklist/checklistai-agent-setup-checklist.agentchecklist.workers.devstreamable-httpv1.4.0Scanned

Setup checklist for AI agents, paid via x402: owner-approval rules, 2FA recovery, launch runbook

5 tools: 1 do something that can't be undone, 1 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 AI Agent Setup Checklist MCP server can do

The AI Agent Setup Checklist MCP server is published by ai-agent-setup-checklist.agentchecklist.workers.dev, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (get_master_checklist) and create or change data (1 tool: check_owner_approval), but cannot delete data. 3 tools only read.

1 tool reads private data (get_table_of_contents); 1 tool brings in text other people can write (get_master_checklist).

The fixed checks matched 2 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 17, 2026, version 1.4.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.

5 tools

Can't be undone 1Claude Code: ask
  • get_master_checklistPaid: 0.02 USDC per call via x402 (exact scheme, USDC on Base mainnet, eip155:8453).Reads text others write2 findings

    Why it is in this group

    • The name "get_master_checklist" says "get": a word for reading.
    • The description says "irreversible".
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...lic or irreversible actions, owner-only credentials), then launch, accounts, 2FA, tokens, a..."

      What this check looks for
    • Warn

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

      Matched text

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

      What this check looks for
    Description, as the server wrote it
    Paid: 0.02 USDC per call via x402 (exact scheme, USDC on Base mainnet, eip155:8453). Returns the one-page master checklist (section 1 of the AI Agent Setup Checklist v1.4, 978 words) as Markdown text, verbatim: yes/no checks starting with what always needs the owner's yes (money, public or irreversible actions, owner-only credentials), then launch, accounts, 2FA, tokens, admins, releases, paid routes and test buying. Use it when you want the whole rule set behind check_owner_approval on one page. Without payment the call returns an x402 PaymentRequired result (isError true; structuredContent holds x402Version and accepts); retry with the signed payment in _meta["x402/payment"]. Takes no input. Same bytes as GET /sections/master-checklist (sha256 5e7720f1938ddfb9c14c51c44b4513d449499509000f75feae8012378212ff3d, 5650 bytes). Full edition: 0.75 USDC at GET /checklist. One-time, sold as-is, no updates.

    Annotations the server declares

    • title: Master checklist (one page, paid)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • check_owner_approvalFree, no payment.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 read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Free, no payment. Quick check before you act: describe one action you are about to take and get a verdict. Returns JSON: verdict (needs_owner_yes = ask your owner first with the exact action, amount and recipient; usually_ok = routine setup an agent may do alone; never_do), the matched category (e.g. money, outbound_message, public_publishing, secret_exposure, phone_sms_verification, account_signup), a one-line reason, and the checklist section that covers it with its paid URL and price (the one-page master checklist is 0.02 USDC; the full edition 0.75 USDC). Deterministic keyword rules drawn from the AI Agent Setup Checklist v1.4: no network calls, nothing stored, same input gives the same output. A quick heuristic, not a guarantee or advice; anything it does not recognize returns needs_owner_yes. Same as GET /check?action=...

    Annotations the server declares

    • title: Check owner approval
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • get_checksumFree, no payment.No findings

    Why it is in this group

    • The name "get_checksum" says "get": a word for reading.
    Description, as the server wrote it
    Free, no payment. Returns JSON with the sha256 and byte size of every paid file (full edition and each section), with its URL and price. Use it after buying to confirm the Markdown you received is complete and unaltered (hash the raw bytes or the envelope's content field). Takes no input. Read-only, no side effects; same data as GET /checksum.

    Annotations the server declares

    • title: Checksums
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_previewFree, no payment.No findings

    Why it is in this group

    • The name "get_preview" says "get": a word for reading.
    Description, as the server wrote it
    Free, no payment. Returns the product preview as JSON: title, version (1.4.0, October 2026 edition), description, table of contents, every paid section with its price in USDC, word count and sha256, one free excerpt, terms, and the buy URLs. Use it first to decide whether the checklist fits your task. Takes no input. Read-only, no side effects; same data as GET /preview.

    Annotations the server declares

    • title: Free preview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_table_of_contentsFree, no payment.Reads private dataNo findings

    Why it is in this group

    • The name "get_table_of_contents" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_table_of_contents" says "get" and "table": it reads databases.
    Description, as the server wrote it
    Free, no payment. Returns JSON with the full edition's 16-section table of contents and the sections sold separately: slug, title, price in USDC, word count, sha256 and paid HTTP URL for each (the 0.02 USDC start-here section is also the get_master_checklist tool). Use it to pick the one section you need before paying. Takes no input. Read-only, no side effects.

    Annotations the server declares

    • title: Table of contents
    • 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 outbound.

Reads private data1
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 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.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 18, 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
2
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 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://ai-agent-setup-checklist.agentchecklist.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including get_master_checklist (irreversible), check_owner_approval (write)

    What this check looks for

Posture changes

  1. Nov 18, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "get_master_checklist" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

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

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

    Matched text

    description: "...lic or irreversible actions, owner-only credentials), then launch, accounts, 2FA, tokens, a..."

    What this check looks for

History

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

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

Install

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

claude mcp add --transport http checklist https://ai-agent-setup-checklist.agentchecklist.workers.dev/mcp
claude mcp add --transport http checklist https://ai-agent-setup-checklist.agentchecklist.workers.dev/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__checklist__get_preview",
      "mcp__checklist__get_table_of_contents",
      "mcp__checklist__get_checksum"
    ],
    "ask": [
      "mcp__checklist__check_owner_approval",
      "mcp__checklist__get_master_checklist"
    ],
    "deny": []
  }
}

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 checklist. Review it before you use it.

Capability tags behind 2 rules
  • mcp__checklist__get_table_of_contents private-data
  • mcp__checklist__get_master_checklist 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/dev.workers.agentchecklist.ai-agent-setup-checklist/checklist/verify?hash=9e1dacb5da927d08af38d00138558c44acfa0337574aa6af9d4fa80408e42f9c" | jq -e '.changed == false'

Pinned hash 9e1dacb5da92, from Nov 17, 2026, 11:17 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.workers.agentchecklist.ai-agent-setup-checklist/checklist/changes.xml

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

Badge

Anlyon Radar badge for dev.workers.agentchecklist.ai-agent-setup-checklist/checklist
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.agentchecklist.ai-agent-setup-checklist/checklist.svg)](https://radar.anlyon.com/servers/dev.workers.agentchecklist.ai-agent-setup-checklist/checklist)

Source: MCP Registry. Synced Nov 3, 2026, 21:17 UTC.

AI Agent Setup Checklist MCP server: questions and answers

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

Is the AI Agent Setup Checklist MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 2 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 AI Agent Setup Checklist MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AI Agent Setup Checklist MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: get_master_checklist.

What tools does the AI Agent Setup Checklist MCP server have?

5 tools: 1 irreversible, 1 write, 3 read. get_master_checklist, check_owner_approval, get_preview, get_table_of_contents and get_checksum.

Does the AI Agent Setup Checklist MCP server need sign-in or OAuth?

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

Does the AI Agent Setup Checklist MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AI Agent Setup Checklist MCP server changed its tools?

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