McpStamp Delivery Schedule MCP server
io.github.theluckystrike/deliverable-trackertheluckystrikestreamable-httpv0.23.0Scanned
Dated deliverables for client work: status, late items with value at risk, sign-off documents.
12 tools: 2 can delete or cancel things, 9 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. 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 McpStamp Delivery Schedule MCP server can do
The McpStamp Delivery Schedule MCP server is published by the GitHub account theluckystrike. It has 12 tools. It can delete or cancel things (2 tools: deliverable_delete and delivery_schedule_delete) and create or change data (9 tools: delivery_schedule_create, deliverable_add, deliverable_status, delivery_schedule_get and 5 more). 1 tool only reads.
1 tool reads private data (deliverable_status); 1 tool brings in text other people can write (license_status).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.23.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.
12 tools
Deletes or cancels 2Claude Code: deny
deliverable_deleteDelete one deliverable still planned with no history.No findings
Why it is in this group
- The name "deliverable_delete" says "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete one deliverable still planned with no history. One started, delivered or accepted is refused, naming when: add a corrected deliverable instead. The D number on a schedule is never reissued.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
delivery_schedule_deleteDelete a schedule carrying no deliverables, freeing an open slot.No findings
Why it is in this group
- The name "delivery_schedule_delete" says "schedule": a word for a change.
- The description's first verb is "delete": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Delete a schedule carrying no deliverables, freeing an open slot. One holding any is refused, naming them, since they record what was owed. The DS number is never reissued. Free on every tier.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 9Claude Code: ask
deliverable_addAdd one dated deliverable and return its D number and the new counts.No findings
Why it is in this group
- The name "deliverable_add" says "add": a word for a change.
Description, as the server wrote it Add one dated deliverable and return its D number and the new counts. value_minor is NET of VAT in whole MINOR units. A due date before the reference document's own date is refused. It starts as planned.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
deliverable_statusRecord a dated move on one deliverable: planned, in_progress, delivered, then accepted with a note.Reads private data1 finding
Why it is in this group
- The name "deliverable_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Findings
- Warn
The server marks "deliverable_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "deliverable_status" says "status": a word for reading.
Description, as the server wrote it Record a dated move on one deliverable: planned, in_progress, delivered, then accepted with a note. An out-of-order move, or a date before the reference document, is refused. The date drives lateness.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
delivery_schedule_createOpen a delivery schedule against a quote, work order or change order and return its DS-YYYY-NNNN number: the reference, its own date, the client, a title and the currency.No findings
Why it is in this group
- The name "delivery_schedule_create" says "schedule": a word for a change.
Description, as the server wrote it Open a delivery schedule against a quote, work order or change order and return its DS-YYYY-NNNN number: the reference, its own date, the client, a title and the currency. Free tier: 3 open.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
delivery_schedule_documentRender one schedule as a plain-text document for the client: every deliverable with its due date, status, delivered and accepted dates and value, the counts as at a date, and a sig…No findings
Why it is in this group
- The name "delivery_schedule_document" says "schedule": a word for a change.
Description, as the server wrote it Render one schedule as a plain-text document for the client: every deliverable with its due date, status, delivered and accepted dates and value, the counts as at a date, and a sign-off block. Pro.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
delivery_schedule_getReturn one schedule in full as at a date: every deliverable with due date, status, delivered and accepted dates, note and value, plus what is late and the totals.No findings
Why it is in this group
- The name "delivery_schedule_get" says "schedule": a word for a change.
Description, as the server wrote it Return one schedule in full as at a date: every deliverable with due date, status, delivered and accepted dates, note and value, plus what is late and the totals. The answer names the as_of it used.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
delivery_schedule_listList schedules oldest reference first with client, currency and counts as at a date: late, still owed, accepted.No findings
Why it is in this group
- The name "delivery_schedule_list" says "schedule": a word for a change.
Description, as the server wrote it List schedules oldest reference first with client, currency and counts as at a date: late, still owed, accepted. Filter by client, reference and state open or complete. Free.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
late_reportWhat has slipped as at a date: every deliverable still owed past its due date, worst first, with value at risk per currency, and what was delivered late kept apart.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 What has slipped as at a date: every deliverable still owed past its due date, worst first, with value at risk per currency, and what was delivered late kept apart. A reference with no schedule is refused.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
license_activateTurn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle.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 Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
milestone_payloadBuild the delivered-and-accepted deliverables as invoice_create-ready items in MAJOR units and quote_create-ready items in MINOR units, with VAT at the shared profile rate.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 Build the delivered-and-accepted deliverables as invoice_create-ready items in MAJOR units and quote_create-ready items in MINOR units, with VAT at the shared profile rate. Writes nothing. Pro.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
license_statusReport this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL.Reads text others writeNo findings
Why it is in this group
- The name "license_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
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 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 17, 2026, 15:24 UTC, unchanged since Nov 17, 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
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule
- Authorization servers
- https://mcp.zovo.one
- 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 11 tools that change things (2 destructive, 9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.zovo.one/mcp/delivery-schedule: tools/list returned 12 tools to an anonymous client, including deliverable_delete (destructive), delivery_schedule_delete (destructive), delivery_schedule_create (write), deliverable_add (write), deliverable_status (write) and 6 more
Posture changes
- Nov 17, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule
- Nov 10, 2026
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule to https://mcp.zovo.one/.well-known/oauth-protected-resource
Findings
Matches of fixed checks, with the text they matched.
The server marks "deliverable_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "deliverable_status" says "status": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource -> https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource to https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule
PostureRemote posture changed. RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule -> https://mcp.zovo.one/.well-known/oauth-protected-resource.View diff
- RFC 9728 protected resource metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/delivery-schedule to https://mcp.zovo.one/.well-known/oauth-protected-resource
Install
Pinned to version 0.23.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http deliverable-tracker https://mcp.zovo.one/mcp/delivery-scheduleclaude mcp add --transport http deliverable-tracker https://mcp.zovo.one/mcp/delivery-scheduleRun 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__deliverable-tracker__license_status"
],
"ask": [
"mcp__deliverable-tracker__delivery_schedule_create",
"mcp__deliverable-tracker__deliverable_add",
"mcp__deliverable-tracker__deliverable_status",
"mcp__deliverable-tracker__delivery_schedule_get",
"mcp__deliverable-tracker__delivery_schedule_list",
"mcp__deliverable-tracker__late_report",
"mcp__deliverable-tracker__delivery_schedule_document",
"mcp__deliverable-tracker__milestone_payload",
"mcp__deliverable-tracker__license_activate"
],
"deny": [
"mcp__deliverable-tracker__deliverable_delete",
"mcp__deliverable-tracker__delivery_schedule_delete"
]
}
}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 deliverable-tracker. Review it before you use it.
Capability tags behind 2 rules
- mcp__deliverable-tracker__deliverable_status private-data
- mcp__deliverable-tracker__license_status 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/io.github.theluckystrike/deliverable-tracker/verify?hash=7afb6e7719ae6e8dae20ff346c6fa3416fbb67636aa2966a1bce05ef2043bfde" | jq -e '.changed == false'Pinned hash 7afb6e7719ae, from Nov 15, 2026, 07:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.theluckystrike/deliverable-tracker/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.theluckystrike/deliverable-tracker)Source: MCP Registry · repository. Synced Nov 2, 2026, 03:18 UTC.
McpStamp Delivery Schedule MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the McpStamp Delivery Schedule MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 11 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the McpStamp Delivery Schedule MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: deliverable_delete and delivery_schedule_delete.
Can the McpStamp Delivery Schedule 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 McpStamp Delivery Schedule MCP server have?
- 12 tools: 2 destructive, 9 write, 1 read. deliverable_delete, delivery_schedule_delete, delivery_schedule_create, deliverable_add, deliverable_status, delivery_schedule_get, delivery_schedule_list, late_report and 4 more.
Does the McpStamp Delivery Schedule MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the McpStamp Delivery Schedule MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the McpStamp Delivery Schedule MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.