Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PraisonAI

PYPI · PRAISONAI

AI Agents Framework with Self Reflection and MCP support

Available components

+19 this week 19 Trust /100

Last scanned (13 hours ago)

Scores higher than 3% of PyPI servers

Category AI and Machine Learning

Recent critical change

CVE-2026-44336 affects this package (18 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security32
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: a known high-severity CVE affects praisonaiagents 1.8.1, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 8 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (8)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (6)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 0
    • Package version: 4.7.26 → 4.8.0 functional
  • 18 Nov 26 +19
    • CVE-2026-44336 affects this package: high ▼ critical
    • CVE-2026-57127 affects this package: high ▼ critical
    • CVE-2026-57125 affects this package: high ▼ critical
    • CVE-2026-40154 affects this package: high ▼ critical
    • CVE-2026-41497 affects this package: high ▼ critical
    • CVE-2026-40289 affects this package: high ▼ critical
    • CVE-2026-61444 affects this package: high ▼ critical
    • CVE-2026-61445 affects this package: high ▼ critical
    • CVE-2026-39305 affects this package: high ▼ critical
    • CVE-2026-34952 affects this package: high ▼ critical
    • CVE-2026-47392 affects this package: high ▼ critical
    • CVE-2026-34953 affects this package: high ▼ critical
    • CVE-2026-40088 affects this package: high ▼ critical
    • CVE-2026-47391 affects this package: high ▼ critical
    • CVE-2026-57145 affects this package: high ▼ critical
    • CVE-2026-40288 affects this package: high ▼ critical
    • CVE-2026-55536 affects this package: high ▼ critical
    • CVE-2026-39890 affects this package: high ▼ critical
    • CVE-2026-57124 affects this package: high ▼ critical
    • CVE-2026-47396 affects this package: high ▼ critical
    • CVE-2026-57131 affects this package: high ▼ critical
    • CVE-2026-47393 affects this package: high ▼ critical
    • CVE-2026-34934 affects this package: high ▼ critical
    • CVE-2026-112938 affects this package: high ▼ security
    • CVE-2026-56074 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-112912 affects this package: high ▼ security
    • CVE-2026-112911 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • GHSA-x462-jjpc-q4q4 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-112908 affects this package: high ▼ security
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects praisonaiagents 1.7.24, a direct dependency. A fixed version is available. security
    • Score status: failed → scored ▲ functional
    • Package version: 2.3.42 → 4.7.26 functional
  • 17 Nov 26 0
    • CVE-2026-44336 affects this package: high ▼ critical
    • CVE-2026-57127 affects this package: high ▼ critical
    • CVE-2026-57125 affects this package: high ▼ critical
    • CVE-2026-40154 affects this package: high ▼ critical
    • CVE-2026-41497 affects this package: high ▼ critical
    • CVE-2026-40289 affects this package: high ▼ critical
    • CVE-2026-61444 affects this package: high ▼ critical
    • CVE-2026-61445 affects this package: high ▼ critical
    • CVE-2026-39305 affects this package: high ▼ critical
    • CVE-2026-34952 affects this package: high ▼ critical
    • CVE-2026-47392 affects this package: high ▼ critical
    • CVE-2026-34953 affects this package: high ▼ critical
    • CVE-2026-40088 affects this package: high ▼ critical
    • CVE-2026-47391 affects this package: high ▼ critical
    • CVE-2026-57145 affects this package: high ▼ critical
    • CVE-2026-40288 affects this package: high ▼ critical
    • CVE-2026-55536 affects this package: high ▼ critical
    • CVE-2026-39890 affects this package: high ▼ critical
    • CVE-2026-57124 affects this package: high ▼ critical
    • CVE-2026-47396 affects this package: high ▼ critical
    • CVE-2026-57131 affects this package: high ▼ critical
    • CVE-2026-47393 affects this package: high ▼ critical
    • CVE-2026-34934 affects this package: high ▼ critical
    • Malware scan: pass → unverified ▼ security
  • 16 Nov 26 0
    • CVE-2026-57131 affects this package: high ▼ critical
    • CVE-2026-44336 affects this package: high ▼ critical
    • CVE-2026-57127 affects this package: high ▼ critical
    • CVE-2026-57125 affects this package: high ▼ critical
    • CVE-2026-40154 affects this package: high ▼ critical
    • CVE-2026-41497 affects this package: high ▼ critical
    • CVE-2026-40289 affects this package: high ▼ critical
    • CVE-2026-61444 affects this package: high ▼ critical
    • CVE-2026-61445 affects this package: high ▼ critical
    • CVE-2026-39305 affects this package: high ▼ critical
    • CVE-2026-34952 affects this package: high ▼ critical
    • CVE-2026-47392 affects this package: high ▼ critical
    • CVE-2026-34953 affects this package: high ▼ critical
    • CVE-2026-40088 affects this package: high ▼ critical
    • CVE-2026-47391 affects this package: high ▼ critical
    • CVE-2026-57145 affects this package: high ▼ critical
    • CVE-2026-40288 affects this package: high ▼ critical
    • CVE-2026-55536 affects this package: high ▼ critical
    • CVE-2026-39890 affects this package: high ▼ critical
    • CVE-2026-57124 affects this package: high ▼ critical
    • CVE-2026-47396 affects this package: high ▼ critical
    • CVE-2026-47393 affects this package: high ▼ critical
    • CVE-2026-34934 affects this package: high ▼ critical
  • 15 Nov 26 0
    • CVE-2026-44336 affects this package: high ▼ critical
    • CVE-2026-57127 affects this package: high ▼ critical
    • CVE-2026-57125 affects this package: high ▼ critical
    • CVE-2026-40154 affects this package: high ▼ critical
    • CVE-2026-41497 affects this package: high ▼ critical
    • CVE-2026-40289 affects this package: high ▼ critical
    • CVE-2026-61444 affects this package: high ▼ critical
    • CVE-2026-61445 affects this package: high ▼ critical
    • CVE-2026-39305 affects this package: high ▼ critical
    • CVE-2026-34952 affects this package: high ▼ critical
    • CVE-2026-47392 affects this package: high ▼ critical
    • CVE-2026-34953 affects this package: high ▼ critical
    • CVE-2026-40088 affects this package: high ▼ critical
    • CVE-2026-47391 affects this package: high ▼ critical
    • CVE-2026-57145 affects this package: high ▼ critical
    • CVE-2026-40288 affects this package: high ▼ critical
    • CVE-2026-55536 affects this package: high ▼ critical
    • CVE-2026-39890 affects this package: high ▼ critical
    • CVE-2026-57124 affects this package: high ▼ critical
    • CVE-2026-47396 affects this package: high ▼ critical
    • CVE-2026-57131 affects this package: high ▼ critical
    • CVE-2026-47393 affects this package: high ▼ critical
    • CVE-2026-34934 affects this package: high ▼ critical
    • Malware scan: unverified → pass ▲ security
  • 14 Nov 26 0
    • CVE-2026-44336 affects this package: high ▼ critical
    • CVE-2026-57127 affects this package: high ▼ critical
    • CVE-2026-57125 affects this package: high ▼ critical
    • CVE-2026-40154 affects this package: high ▼ critical
    • CVE-2026-41497 affects this package: high ▼ critical
    • CVE-2026-40289 affects this package: high ▼ critical
    • CVE-2026-61444 affects this package: high ▼ critical
    • CVE-2026-61445 affects this package: high ▼ critical
    • CVE-2026-39305 affects this package: high ▼ critical
    • CVE-2026-34952 affects this package: high ▼ critical
    • CVE-2026-47392 affects this package: high ▼ critical
    • CVE-2026-34953 affects this package: high ▼ critical
    • CVE-2026-40088 affects this package: high ▼ critical
    • CVE-2026-47391 affects this package: high ▼ critical
    • CVE-2026-57145 affects this package: high ▼ critical
    • CVE-2026-40288 affects this package: high ▼ critical
    • CVE-2026-55536 affects this package: high ▼ critical
    • CVE-2026-39890 affects this package: high ▼ critical
    • CVE-2026-57124 affects this package: high ▼ critical
    • CVE-2026-47396 affects this package: high ▼ critical
    • CVE-2026-57131 affects this package: high ▼ critical
    • CVE-2026-47393 affects this package: high ▼ critical
    • CVE-2026-34934 affects this package: high ▼ critical
    • Malware scan: pass → unverified ▼ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed pypi/praisonai@4.8.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 16 findings
ID CVE Severity Vector Fix available
GHSA-567q-5qvw-pf92 CVE-2026-112907 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-6627-m3xw-93mp CVE-2026-112908 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L yes
GHSA-69hj-f68j-2879 CVE-2026-112909 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N yes
GHSA-8mx5-7m5m-r77g CVE-2026-112910 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L yes
GHSA-9c4x-gm8v-wgc4 CVE-2026-112911 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H yes
GHSA-9j6q-wvj5-jgjg CVE-2026-112912 low CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N yes
GHSA-9vhv-jxww-xfm5 CVE-2026-112913 low CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L yes
GHSA-cwqr-hh33-gh44 CVE-2026-112915 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-fq56-3cx3-fjxp CVE-2026-112935 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-j8f7-rjxc-mr56 CVE-2026-112936 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L yes
GHSA-m462-7rxw-wvpg CVE-2026-112938 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H yes
GHSA-rfpc-qcw5-3pc4 CVE-2026-112939 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N yes
GHSA-v4x8-3wr5-3wq8 CVE-2026-112940 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H yes
GHSA-ffp3-3562-8cv3 CVE-2026-56074 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-x462-jjpc-q4q4 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N yes
PYSEC-2026-2946 CVE-2026-56074 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 100 packages
Packages resolved 100
Stale 7
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the PraisonAI MCP server?

PraisonAI runs locally as a PyPI package, launched with uvx praisonai. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · praisonai

# add to Claude Code
claude mcp add mervinpraison-praisonai -- uvx praisonai
Common questions

What is the PraisonAI MCP server?

PraisonAI is an MCP server listed in the public MCP registry as io.github.MervinPraison/praisonai. AI Agents Framework with Self Reflection and MCP support. This page covers its PyPI package (praisonai).

Is the PraisonAI MCP server safe to use?

PraisonAI scores 19 out of 100 on VerifyMCP. We recorded 16 known advisories against it as of 21 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the PraisonAI MCP server still maintained?

PraisonAI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the PraisonAI MCP server under?

PraisonAI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the PraisonAI MCP server?

VerifyMCP ran 8 checks on PraisonAI, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about PraisonAI: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.