MCP.Market

McpStamp Delivery Schedule MCP server

online · 21% uptime
by theluckystrike·io.github.theluckystrike/deliverable-tracker·v0.23.0·2 stars
No reviews yet

Dated deliverables for client work: status, late items with value at risk, sign-off documents.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed McpStamp Delivery Schedule yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

McpStamp Delivery Schedule tools (12, 3 write)

write = sends, deletes, buys or posts
  • deliverable_addFree

    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.

  • deliverable_deletewrite actionFree

    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.

  • deliverable_statusFree

    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.

  • delivery_schedule_createwrite actionFree

    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.

  • delivery_schedule_deletewrite actionFree

    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.

  • delivery_schedule_documentFree

    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.

  • delivery_schedule_getFree

    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.

  • delivery_schedule_listFree

    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.

  • late_reportFree

    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.

  • license_activateFree

    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.

  • license_statusFree

    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.

  • milestone_payloadFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

1 high
  • –Code scanpackage could not be scannedn/a
  • Live reliabilityremote reachable in 3013ms17/20
  • Tool poisoning12 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How McpStamp Delivery Schedule compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 48,255 servers
Tools
12
the typical server has 7
Tools that change things
25%
typical: 0%. Fewer write tools means less an agent can break
Uptime
21%
of our recent checks; the typical remote server answers 100%
Response time
8 ms
faster than 99% of 30,031 servers
GitHub stars
2
more than 75% of 28,688 servers

What its tools let an agent do: 9 read · 3 change

Release history: 5 versions in the registry since 2026-09-17, latest 2026-11-02, typically one every 19 days.

Install McpStamp Delivery Schedule in Claude Code, Cursor or VS Code

claude mcp add --transport http deliverable-tracker https://mcp.zovo.one/mcp/delivery-schedule
Add to Cursor

What the publisher says

From the McpStamp Delivery Schedule repository's README, as published. We do not edit it. Read it on GitHub

MCP servers by theluckystrike

<!-- gen:badge --> <!-- /gen:badge -->

Practical Model Context Protocol servers for people who work inside Claude, Cursor and other MCP clients. Every server runs locally over stdio, keeps all data on your machine, and has a genuinely useful free tier. Pro unlocks the limits for a one-time payment: $19 per server or $39 for the bundle, lifetime.

<!-- gen:counts --> 46 servers plus the office-suite aggregator, 45 of them also reachable as a hosted endpoint with no install. <!-- /gen:counts -->

No install? Use any server instantly as a hosted endpoint: https://mcp.zovo.one/mcp/ — or browse the catalog at mcp.zovo.one.

<!-- gen:install -->

That is the invoice server answering a real prompt: a client, some hours, a VAT rate, and a numbered PDF at the end. Every server in the table below has a demo like it.

Two ways to run any of these, both working today.

  1. One click. Download the server's .mcpb bundle from the latest release and open it in Claude Desktop. No terminal, no config file.
  2. No install at all. Point a client at https://mcp.zovo.one/mcp/. GET https://mcp.zovo.one/mcp/connect mints a free token and prints a ready URL for each server.

A third way is coming and does not work yet: the npm packages are unpublished, so npx -y @theluckystrike/mcp- returns 404 today. The commands below are written for the day it is published; use one of the two paths above until then. <!-- /gen:install -->

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-02restoreD → Bscore 77: Write-action tools reachable without authentication
  • 2026-09-24downgradeA → Dscore 48: Remote endpoint did not respond
  • 2026-09-19restoreC → Ascore 88

McpStamp Delivery Schedule: common questions

Is McpStamp Delivery Schedule MCP server safe?
Mostly: it is graded B (77/100). Read the McpStamp Delivery Schedule safety report
How do I install McpStamp Delivery Schedule?
It runs remotely at mcp.zovo.one. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does McpStamp Delivery Schedule need an API key?
Yes. The registry entry asks for MCP_LICENSE_KEY.
Is McpStamp Delivery Schedule maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v0.23.0.
Is McpStamp Delivery Schedule up?
21% of our last 28 checks got an answer. We check remote servers about four times a day.
How does McpStamp Delivery Schedule compare with other MCP servers?
safety score 77/100 (higher than 50% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 25% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.