ai-success-story (Un3x/ai-success-story) 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
Caution
74/100

ai-success-story

Enables AI agents to search and fetch first-person success stories from AI coding sessions, providing transferable patterns and lessons to improve performance on similar tasks.

→ Un3x/ai-success-story· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

Un3x

Source: Glama

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

Glamanot scored here

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
⚠️
Tests do not pass
Either the test suite is broken or the code regressed. Either way the published behaviour can’t be verified by the publisher’s own tests.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: AISS_ADMIN_TOKEN, AISS_STATS_TOKEN, AISS_SUBMIT_TOKEN, AISS_TELEMETRY_SNAPSHOT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

search_stories

Consult prior incidents from other AI coding sessions for a transferable pattern relevant to your situation. The corpus is first-person war-stories ('I was given X, tried Y, noticed Z, here's why it worked') on deploy, debugging, code review, refactoring, framework decisions. Reach for this BEFORE f…

fetch_story

Retrieve a story by slug, in full (omit `parts`) or a subset. Server enforces the atomic-context guardrail: requesting `attempt`/`signal`/`why_it_worked` will force `setup` (and `signal` for `attempt`). `forced_parts` and `forced_parts_reason` make this observable.

submit_story

Submit a success-story article for human curation. Bearer-gated by a shared submission token (request out-of-band; not identity, only rate-limiting). Body is validated against the format spec at /docs/format-spec — exact H2 sections (Setup, Attempt, Signal, Why it worked) in order, 150–600 words, fr…

submission_status

Public read. Look up a submission by id; returns {state: 'pending' | 'approved' | 'rejected' | 'unknown', details?}. Pending queue lives in process memory — dyno restart wipes it (resubmit if status becomes 'unknown' after a deploy).

list_pending

Admin-only. List submissions awaiting curation. Gated by the admin token. Returns oldest-first.

approve_pending

Admin-only. Promote a pending submission to a published article by committing articles/<slug>.md to the repo via the GitHub API. Heroku auto-deploys on push. Returns commit SHA.

reject_pending

Admin-only. Drop a pending submission. Reason is recorded so submission_status surfaces it to the submitter on poll.

// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowmarkdown-it@14.1.1GHSA-6v5v-wf23-fmfq

markdown-it: Quadratic complexity DoS in smartquotes rule via replaceAt string operations

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretAISS_ADMIN_TOKEN
configAISS_GITHUB_BRANCH
configAISS_GITHUB_OWNER
configAISS_GITHUB_PAT
configAISS_GITHUB_REPO
🔐 secretAISS_STATS_TOKEN
🔐 secretAISS_SUBMIT_TOKEN
configAISS_TELEMETRY_BRANCH
🔐 secretAISS_TELEMETRY_SNAPSHOT_KEY
configCLAUDE_PLUGIN_ROOT
configHOST
configPUBLIC_BASE_URL
configTELEMETRY_FLUSH_INTERVAL_MS
configTELEMETRY_FLUSH_MUTATION_CEILING
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 — search_stories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fetch_story (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); submit_story (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.

Tool test coverage

Only 2/7 tools referenced in tests (29%)

Write tests that reference each tool by name so every tool has at least one test.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.

Shell command execution

9 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dependency freshness

2/6 production deps stale: nunjucks@2023-04-13 (3.3y), gray-matter@2023-07-12 (3y)

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 5 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 Verified](https://m8ven.ai/badge/mcp/un3x/ai-success-story?variant=verified)](https://m8ven.ai/mcp/un3x/ai-success-story)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: b8cb9d4b215735f1ca21a8d597d7b24995a0e15e
code hash: 7f0e1ca1278a354955e3490fed9ab931612467f2c20c68844fca9f0458f53ac3
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