Aging MCP server

by theluckystrike·io.github.theluckystrike/aging·v0.21.0

Age your receivables into 0-30, 31-60, 61-90 and over 90 day buckets by due date.

B73/100grade B

What users say

No reviews yet

Safety scan

B73/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Aging 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.9 · 2026-09-20 · 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 qualitystatic API keys via environment variables6/15
Maintenancelast push 1 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 73/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 Aging MCP server safe?: Mostly: it is graded B (73/100). Read the Aging safety report
Does Aging need an API key?: Yes. The registry entry asks for MCP_LICENSE_KEY.
Is Aging maintained?: The last commit was in the last day (2026-09-19). The latest release is v0.21.0.