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

Emerging

74/100

10 days ago

Praison

Item: Praison
Rating: 74
Author: M8ven

Praison is a production-ready framework for building multi-agent AI systems that enables intelligent agents to collaborate, reason, self-reflect, and use tools to automate tasks, with support for over 100 LLMs and flexible workflows for both code and no-code usage.

→ Praison-Labs/Praison · listed on github_code

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

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 push why connect →

Who stands behind it

Praison-Labs

Source: github_code

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: OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.

🔐

You'll be asked for 8 credentials: OPENAI_API_KEY, TAVILY_API_KEY, AGENTOPS_API_KEY, CHAINLIT_PASSWORD, HF_TOKEN, NGROK_AUTH_TOKEN, CHAINLIT_AUTH_SECRET, MEM0_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.

🔐 secretOPENAI_API_KEY

configPRAISON_PRETTY

configPRAISON_VERBOSE

configOPENAI_API_BASE

configOPENAI_BASE_URL

🔐 secretTAVILY_API_KEY

configOTEL_SDK_DISABLED

configEC_TELEMETRY

🔐 secretAGENTOPS_API_KEY

configMODEL_NAME

configOPENAI_MODEL_NAME

configOLLAMA_API_BASE

configCHAINLIT_USERNAME

🔐 secretCHAINLIT_PASSWORD

configCHAINLIT_APP_ROOT

configGRADIO_LOGLEVEL

configCHAINLIT_PORT

configPRAISON_WANDB

configPRAISON_WANDB_RUN_NAME

🔐 secretHF_TOKEN

🔐 secretNGROK_AUTH_TOKEN

configPUBLIC

configAUTH_PASSWORD_ENABLED

🔐 secretCHAINLIT_AUTH_SECRET

configFRAMEWORK

configAUTH_OAUTH_ENABLED

configPRAISONAI_CODE_REPO_PATH

configPRAISONAI_MAX_TOKENS

configPRAISONAI_IGNORE_FILES

configFORCE_SQLITE

configSUPABASE_DATABASE_URL

configANONYMIZED_TELEMETRY

🔐 secretMEM0_API_KEY

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

deployDATABASE_URL

// 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

3/3 tools missing one or more hints — tool_def (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_agent_task (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); execute_workflow_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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

1/3 tools referenced in tests (33%)

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

Secrets not logged

4 secret values sent to logger.debug

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/praison-labs/praison)](https://m8ven.ai/mcp/praison-labs/praison)

Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.

commit: da97416c3ae220094906e428f4c6dc7637ad4fed

code hash: 8e51a753397a9b4d5400ad97bfee212c65cca057d2e229df9988778e7bb28f76

verified: 9/3/2026, 5:14:35 PM

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