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

Back to MCP Trust IndexM8ven
C
Emerging
74/100

Noshy

Provide persistent knowledge storage for AI agents using ICM and MCP standards to manage facts and memory graphs across sessions.

→ slickpurse464/Noshy· 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

slickpurse464

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
🚨
Secret credentials may flow to a network call
1 flow detected: API_SERVER_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: NOSHY_HTTP_TOKEN, OPENAI_API_KEY, API_SERVER_KEY, NOSHY_EMBED_API_KEY, NOSHY_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.
configNOSHY_LOG_FILERotating request logs — set or run in a container to get ~/.noshy/noshy.log (5MB x 3 rotation)
🔐 secretNOSHY_HTTP_TOKENWhen is set, the dashboard shows a token prompt modal on
configNOSHY_CONFIGCreate ~/.noshy/config.toml (or set to a custom path):
🔐 secretOPENAI_API_KEYBest
🔐 secretAPI_SERVER_KEYVaries
configOPENAI_API_BASE
🔐 secretNOSHY_EMBED_API_KEYEmbedding API key
configNOSHY_EMBED_MODELEmbedding model name
configNOSHY_EMBED_PROVIDERNoshy auto-detects the best available embedding provider. Set to override:
configNOSHY_API_BASELLM API for extraction
🔐 secretNOSHY_API_KEYLLM API key
configNOSHY_MODELModel for extraction
configNOSHY_DBDatabase path
// 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

20/20 tools missing one or more hints — noshy_store_memory (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); noshy_store_memoir (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); noshy_recall (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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

6/20 tools referenced in tests (30%)

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

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 3 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/slickpurse464/noshy)](https://m8ven.ai/mcp/slickpurse464/noshy)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: b4bb0cb3dc4149544fe199d626c9eb6d8709b54b
code hash: 6d8b56eaa2ef1e3be9152def641589b42b5ba6b32f5c2d9ac8a62e90b129e248
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