Afterglow Checklists MCP server
com.soxoa/afterglow-checklistssoxoa.comstreamable-httpv1.0.2Scanned
Read linked separation checklists and save confirmed item progress. OAuth; practical guidance only.
3 tools: 1 can delete or cancel things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- 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 Afterglow Checklists MCP server can do
The Afterglow Checklists MCP server is published by soxoa.com, a domain the MCP Registry verified. It has 3 tools. It can delete or cancel things (1 tool: set_checklist_status). 2 tools only read.
1 tool reads private data (get_connected_profile); 1 tool brings in text other people can write (get_connected_profile).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.2.
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.
3 tools
Deletes or cancels 1Claude Code: deny
set_checklist_statusSave done, to do or not applicable for the exact item ID the user selected from an Afterglow checklist.No findings
Why it is in this group
- The name "set_checklist_status" says "set": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Save done, to do or not applicable for the exact item ID the user selected from an Afterglow checklist. Obtain confirmation of the item and status before calling. Overwrites that item's existing progress in the connected account. Repeating the same item and status preserves the completed timestamp and returns the saved state.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
get_checklistShow available items and saved progress in one of your Afterglow checklists.No findings
Why it is in this group
- The name "get_checklist" says "get": a word for reading.
Description, as the server wrote it Show available items and saved progress in one of your Afterglow checklists. Use when you ask for unfinished legal, money, home or coparenting checklist tasks. Your account's current onboarding and plan limits apply. Keep the returned disclaimer intact.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_connected_profileIdentify the Afterglow account connected for this conversation.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_connected_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "conversation": it reads messages.
- untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
Description, as the server wrote it Identify the Afterglow account connected for this conversation. Returns the account email and its actual verification state. Does not read your story or coaching history.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- 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.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 6, 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
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.withafterglow.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.withafterglow.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 destructive). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.withafterglow.com/mcp: tools/list returned 3 tools to an anonymous client, including set_checklist_status (destructive)
Posture changes
- Nov 6, 2026
- RFC 9728 protected resource metadata: https://afterglow-lime.vercel.app/.well-known/oauth-protected-resource/mcp to https://api.withafterglow.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: https://afterglow-lime.vercel.app to https://api.withafterglow.com
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: https://afterglow-lime.vercel.app/.well-known/oauth-protected-resource/mcp -> https://api.withafterglow.com/.well-known/oauth-protected-resource/mcp; Authorization servers: https…View diff
- RFC 9728 protected resource metadata: https://afterglow-lime.vercel.app/.well-known/oauth-protected-resource/mcp to https://api.withafterglow.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: https://afterglow-lime.vercel.app to https://api.withafterglow.com
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http afterglow-checklists https://api.withafterglow.com/mcpclaude mcp add --transport http afterglow-checklists https://api.withafterglow.com/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__afterglow-checklists__get_connected_profile",
"mcp__afterglow-checklists__get_checklist"
],
"ask": [],
"deny": [
"mcp__afterglow-checklists__set_checklist_status"
]
}
}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 afterglow-checklists. Review it before you use it.
Capability tags behind 1 rule
- mcp__afterglow-checklists__get_connected_profile private-data, 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/com.soxoa/afterglow-checklists/verify?hash=91a09a5f357f7bc36dcfea1754801b80d4d414242e70bdccb25049075d16fa9c" | jq -e '.changed == false'Pinned hash 91a09a5f357f, from Nov 16, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.soxoa/afterglow-checklists/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.soxoa/afterglow-checklists)Source: MCP Registry. Synced Nov 2, 2026, 22:17 UTC.
Afterglow Checklists MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Afterglow Checklists MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 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 Afterglow Checklists MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: set_checklist_status.
Can the Afterglow Checklists 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 Afterglow Checklists MCP server have?
- 3 tools: 1 destructive, 2 read. set_checklist_status, get_connected_profile and get_checklist.
Does the Afterglow Checklists MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Afterglow Checklists MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Afterglow Checklists MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.