Stillleaf: Memorial program correction, printing and delivery MCP server
com.forevenza.services/stillleafservices.forevenza.comstreamable-httpv1.0.0Scanned
Existing memorial program correction, printing and delivery coordination for funeral homes
7 tools: 1 can delete or cancel things, 2 do something that can't be undone, 2 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 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 Stillleaf: Memorial program correction, printing and delivery MCP server can do
The Stillleaf: Memorial program correction, printing and delivery MCP server is published by services.forevenza.com, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: decline_offer), do things that cannot be undone, such as sending, paying or publishing (submit_request and release_payment) and create or change data (2 tools: request_status and accept_offer). 2 tools only read.
1 tool can send data out of your system (submit_request).
The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 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.
7 tools
Deletes or cancels 1Claude Code: deny
decline_offerDecline an issued offer on its inspected terms.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 destructive (destructiveHint: true).
Description, as the server wrote it Decline an issued offer on its inspected terms.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 2Claude Code: ask
release_paymentConfirm a payment condition only where the inspected order allows the customer to release it.No findings
Why it is in this group
- The name "release_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Confirm a payment condition only where the inspected order allows the customer to release it. This records approval; it does not pay the processor.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
submit_requestSend a requirement to Stillleaf.Can send data outNo findings
Why it is in this group
- The name "submit_request" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
- The input carries an amount (input.budget.amount) and a currency, so it moves money.
- The input addresses people (input.geography.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.geography.to): what the tool writes goes there.
Description, as the server wrote it Send a requirement to Stillleaf. It is kept with a reference number. Your correction and delivery request is recorded and receives a reference number. If no secure link was given, the next step is yours: reply to Stillleaf's first email with the file attached. When the file arrives, Stillleaf reviews it with the correction, resolves open details, and establishes printing and delivery feasibility. We reply by email when you leave an address, with a proposed completion plan and pricing for review. Nothing is ordered or committed until you agree terms; timing and availability are confirmed before acceptance. Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 2Claude Code: ask
accept_offerPlace an order on terms you have inspected and the buyer has authorized you to accept.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 Place an order on terms you have inspected and the buyer has authorized you to accept. Requires the exact terms hash and explicit acceptance. Follow inspect_offer later for payment links and verified payment state.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
request_statusResume a requirement using the receipt credentials.2 findings
Why it is in this group
- The name "request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "Resume a requirement using the receipt credentials. Read the recorded requirement and any..."
- Warn
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
Description, as the server wrote it Resume a requirement using the receipt credentials. Read the recorded requirement and any linked offers. Contact details are kept apart.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
describe_businessWhat Stillleaf does, what happens to a request, and the request fields.No findings
Why it is in this group
- The name "describe_business" says "describe": a word for reading.
Description, as the server wrote it What Stillleaf does, what happens to a request, and the request fields.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
inspect_offerRead the exact authorized terms, terms hash, order state and processor payment links.1 finding
Why it is in this group
- The name "inspect_offer" says "inspect": a word for reading.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...essor payment links. Use the offer link credentials, or credentials of the request explicit..."
Description, as the server wrote it Read the exact authorized terms, terms hash, order state and processor payment links. Use the offer link credentials, or credentials of the request explicitly linked to this offer.
Annotations the server declares
- 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 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.
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 16, 2026, 14:20 UTC, unchanged since Nov 16, 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
- 14
- 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 14 tools that change things (1 destructive, 4 irreversible, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://stillleaf.forevenza.com/mcp: tools/list returned 18 tools to an anonymous client, including decline_offer (destructive), submit_request (irreversible), send_requirement (irreversible), release_payment (irreversible), submit_purchase_order (irreversible) and 9 more
Posture changes
- Nov 16, 2026
- Tools that change things, listed without credentials: 11 to 14
Findings
Matches of fixed checks, with the text they matched.
- Warnrequest_status
The server marks "request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "request_status" says "request": a word for a change.
- Inforequest_status
The description mentions "credentials".
What this check looks forMatched text
description: "Resume a requirement using the receipt credentials. Read the recorded requirement and any..."
- Infoinspect_offer
The description mentions "credentials".
What this check looks forMatched text
description: "...essor payment links. Use the offer link credentials, or credentials of the request explicit..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 14.View diff
- Tools that change things, listed without credentials: 11 to 14
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http stillleaf https://stillleaf.forevenza.com/mcpclaude mcp add --transport http stillleaf https://stillleaf.forevenza.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__stillleaf__describe_business",
"mcp__stillleaf__inspect_offer"
],
"ask": [
"mcp__stillleaf__submit_request",
"mcp__stillleaf__request_status",
"mcp__stillleaf__accept_offer",
"mcp__stillleaf__release_payment"
],
"deny": [
"mcp__stillleaf__decline_offer"
]
}
}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 stillleaf. Review it before you use it.
Capability tags behind 1 rule
- mcp__stillleaf__submit_request 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/com.forevenza.services/stillleaf/verify?hash=c9238f5d0fc693a237bada3c83d452bfe69a61ba6ddc4dc4746465f05dc5adbe" | jq -e '.changed == false'Pinned hash c9238f5d0fc6, from Nov 8, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.forevenza.services/stillleaf/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.forevenza.services/stillleaf)Source: MCP Registry. Synced Nov 8, 2026, 15:17 UTC.
Stillleaf: Memorial program correction, printing and delivery MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Stillleaf: Memorial program correction, printing and delivery MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 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 Stillleaf: Memorial program correction, printing and delivery MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: decline_offer.
Can the Stillleaf: Memorial program correction, printing and delivery MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: submit_request and release_payment.
What tools does the Stillleaf: Memorial program correction, printing and delivery MCP server have?
- 7 tools: 1 destructive, 2 irreversible, 2 write, 2 read. decline_offer, submit_request, release_payment, request_status, accept_offer, describe_business and inspect_offer.
Does the Stillleaf: Memorial program correction, printing and delivery MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Stillleaf: Memorial program correction, printing and delivery MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): submit_request.
Has the Stillleaf: Memorial program correction, printing and delivery MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.