Classification Receipt & Appeal Layer
com.textforagents/classification-receipt-appeal-layertextforagents.comstreamable-httpv1.0.0Scanned
Signed verdict receipts recovering a fleet's gatekeeper category, plus appeal packets.
8 tools: 5 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Anlyon alternative
5 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →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.
8 tools
Changes things 5Claude Code: ask
alert_checkOne change-driven alerting check (subscription required)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 One change-driven alerting check (subscription required)
appeal_packetAssemble one appeal packet per receipt ($4.99 x402 via REST; via MCP returns packet requirements)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 Assemble one appeal packet per receipt ($4.99 x402 via REST; via MCP returns packet requirements)
register_agentRegister an agent with declared functions (search/agent/training)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 Register an agent with declared functions (search/agent/training)
verify_attestationVerify a per-request function attestationCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Verify a per-request function attestation
verify_receiptVerify a signed verdict receipt: ok/tampered/expired/superseded/unknownNo 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 Verify a signed verdict receipt: ok/tampered/expired/superseded/unknown
Only reads 3Show 3 read-only tools
gatekeeper_fetchGatekeeper-double fetch for evidence (per-bot default)No findings
Why it is in this group
- The name "gatekeeper_fetch" says "fetch": a word for reading.
Description, as the server wrote it Gatekeeper-double fetch for evidence (per-bot default)
panel_statusPanel sites and per-category policiesNo findings
Why it is in this group
- The name "panel_status" says "status": a word for reading.
Description, as the server wrote it Panel sites and per-category policies
verdict_queryVerdict query $0.05 (first free once per account+wallet); returns signed receipt or incomplete/contestedNo findings
Why it is in this group
- The name "verdict_query" says "query": a word for reading.
Description, as the server wrote it Verdict query $0.05 (first free once per account+wallet); returns signed receipt or incomplete/contested
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 untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
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.
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 classification-receipt-appeal-layer https://textforagents.com/products/classification-receipt-appeal-layer/mcpclaude mcp add --transport http classification-receipt-appeal-layer https://textforagents.com/products/classification-receipt-appeal-layer/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__classification-receipt-appeal-layer__verdict_query",
"mcp__classification-receipt-appeal-layer__panel_status",
"mcp__classification-receipt-appeal-layer__gatekeeper_fetch"
],
"ask": [
"mcp__classification-receipt-appeal-layer__register_agent",
"mcp__classification-receipt-appeal-layer__verify_receipt",
"mcp__classification-receipt-appeal-layer__verify_attestation",
"mcp__classification-receipt-appeal-layer__appeal_packet",
"mcp__classification-receipt-appeal-layer__alert_check"
],
"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 classification-receipt-appeal-layer. Review it before you use it.
Capability tags behind 1 rule
- mcp__classification-receipt-appeal-layer__verify_attestation 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://anlyon.dev/api/v1/servers/com.textforagents/classification-receipt-appeal-layer/verify?hash=0802607716aacca485f47ff0bb4c5d96e16807547278f362fd1e36c450d1fccc" | jq -e '.changed == false'Pinned hash 0802607716aa, from Oct 23, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.textforagents/classification-receipt-appeal-layer/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.textforagents/classification-receipt-appeal-layer)Source: MCP Registry. Synced Oct 23, 2026, 02:17 UTC.