Aftercare (Calebux/Aftercare) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Aftercare

Evidence-based recovery for failed agent workflows across GitHub, Linear, and Slack. Human approval, preserved edits, verified outcomes.

→ Calebux/Aftercare· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

Calebux

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: ARGA_GITHUB_TOKEN, ARGA_LINEAR_TOKEN, ARGA_SLACK_TOKEN, OPENROUTER_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAFTERCARE_ALLOWED_HOSTS
configAFTERCARE_DATA_DIR
configAFTERCARE_HOSTED_AIturns AI investigation off unless =1, so visitors cannot spend
configAFTERCARE_PUBLIC_URLSet to the address people will open, for example
configAFTERCARE_SCENARIO_ONLY
🔐 secretARGA_GITHUB_TOKENProvider tokens can be set with , ARGA_LINEAR_TOKEN, and ARGA_SLACK_TOKEN.
🔐 secretARGA_LINEAR_TOKENProvider tokens can be set with ARGA_GITHUB_TOKEN, , and ARGA_SLACK_TOKEN.
configARGA_MCP_AUTHORIZATIONconnecting real apps does not. With an MCP credential (ARGA_MCP_URL and ,
configARGA_MCP_URLconnecting real apps does not. With an MCP credential ( and ARGA_MCP_AUTHORIZATION,
🔐 secretARGA_SLACK_TOKENProvider tokens can be set with ARGA_GITHUB_TOKEN, ARGA_LINEAR_TOKEN, and .
configARGA_TWIN_TTL_MINUTES
configHOSTlistens on 0.0.0.0 and PORT unless is set.
🔐 secretOPENROUTER_API_KEYAdd to the ignored local .env file and restart the server. You can set
configOPENROUTER_MODELto a provider/model ID that supports function tools; the evaluations used
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

7/7 tools missing one or more hints — start_run (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); github_create_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); linear_create_issue (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Secrets not logged

2 secret values sent to log

Redact or omit secret values from log output.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/calebux/aftercare)](https://m8ven.ai/mcp/calebux/aftercare)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 99ba2c59c99dbe848c39527066adac116883c33c
code hash: 96fadbe0d9246f569b60d7d511b06bffcf7e80549a98913d088618a9dec49e10
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client