Recurring MCP server

by theluckystrike·io.github.theluckystrike/recurring·v0.22.1

Recurring invoices on a schedule: define once, generate the due PDFs, forecast revenue.

A88/100grade A

What users say

No reviews yet

Safety scan

A88/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Recurring yet.

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

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings

–Code scanpackage could not be scannedn/a
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

The registry entry has no remote endpoint or installable package.

Is Recurring MCP server safe?: Yes, by our scan: it is graded A (88/100). Read the Recurring safety report
Does Recurring need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Recurring maintained?: The last commit was in the last day (2026-09-19). The latest release is v0.22.1.