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 · SCANNED SEP 24

AI Agents Framework with Self Reflection and MCP support

Available components

pypi · praisonai 0
0 this week 0 Trust /100

Recent critical change

CVE-2026-44336 affects this package (24 Sept 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 Security24
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 2 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 →

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
// .cursor/mcp.json
{
  "mcpServers": {
    "mervinpraison-praisonai": {
      "command": "uvx",
      "args": [
        "praisonai"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "mervinpraison-praisonai": {
      "command": "uvx",
      "args": [
        "praisonai"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add mervinpraison-praisonai -- uvx praisonai
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mervinpraison-praisonai": {
      "type": "local",
      "command": [
        "uvx",
        "praisonai"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mervinpraison-praisonai --command uvx --arg praisonai
# ~/.hermes/config.yaml
mcp_servers:
  mervinpraison-praisonai:
    command: "uvx"
    args: ["praisonai"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "mervinpraison-praisonai": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "praisonai"
      ]
    }
  }
}
# add to Vellum
assistant mcp add mervinpraison-praisonai -t stdio -c uvx -a praisonai
// mcp.json
{
  "mcpServers": {
    "mervinpraison-praisonai": {
      "command": "uvx",
      "args": [
        "praisonai"
      ]
    }
  }
}
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.

  • 24 Sept 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-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
  • 23 Sept 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-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
  • 22 Sept 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-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
  • 21 Sept 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-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
  • 20 Sept 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-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
  • 19 Sept 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-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
  • 18 Sept 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-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
  • 17 Sept 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-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 24 Sept 2026 · Analysed pypi/praisonai@2.3.42

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

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

Vulnerabilities 162 findings
ID CVE Severity Vector Fix available
GHSA-2763-cj5r-c79m CVE-2026-40088 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H yes
GHSA-29w3-p9w9-wc47 CVE-2026-57145 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-2g3w-cpc4-chr4 CVE-2026-40156 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yes
GHSA-2jgc-f764-c5r2 CVE-2026-55539 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H yes
GHSA-2xgv-5cv2-47vv CVE-2026-40115 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-32vr-5gcf-3pw2 CVE-2026-39890 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-3c4r-6p77-xwr7 CVE-2026-40158 high CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H yes
GHSA-4869-x4pr-q22x CVE-2026-57125 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-4mr5-g6f9-cfrh CVE-2026-47392 critical CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H yes
GHSA-4ph2-f6pf-79wv CVE-2026-39307 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H yes
GHSA-4rx4-4r3x-6534 CVE-2026-39306 high CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H yes
GHSA-4wr3-f4p3-5wjh CVE-2026-40149 high CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N yes
GHSA-5c6w-wwfq-7qqm CVE-2026-47390 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-5cxw-77wg-jrf3 CVE-2026-47395 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-6g6r-q6gw-w8fg CVE-2026-55536 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-78r8-wwqv-r299 CVE-2026-47398 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-8444-4fhq-fxpq CVE-2026-47393 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-86qc-r5v2-v6x6 CVE-2026-47396 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-8ccj-p46r-jwqq CVE-2026-57132 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-8frj-8q3m-xhgm CVE-2026-40114 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N yes
GHSA-8w9j-hc3g-3g7f CVE-2026-34939 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8x8f-54wf-vv92 CVE-2026-40289 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-98f9-fqg5-hvq5 CVE-2026-34953 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-9cq8-3v94-434g CVE-2026-34934 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-9cr9-25q5-8prj CVE-2026-47394 high yes
GHSA-9mqq-jqxf-grvw CVE-2026-44336 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H yes
GHSA-9q28-ghcr-c4x3 CVE-2026-44340 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-9qhq-v63v-fv3j CVE-2026-41497 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-cfg2-mxfj-j6pw CVE-2026-40112 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N yes
GHSA-cfh6-vr3j-qc3g CVE-2026-34952 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-ch89-h4r2-c8f8 CVE-2026-55540 high CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L yes
GHSA-f292-66h9-fpmf CVE-2026-39889 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f2h6-7xfr-xm8w CVE-2026-40148 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-fq2m-6wqh-x44g CVE-2026-57131 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-fvxx-ggmx-3cjg CVE-2026-40113 high CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N yes
GHSA-g985-wjh9-qxxc CVE-2026-40287 high CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-gcq3-mfvh-3x25 CVE-2026-56839 high CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N yes
GHSA-gfq8-hmph-9gjv CVE-2026-55533 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N yes
GHSA-gmjg-hv98-qggq CVE-2026-44339 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L yes
GHSA-hmfx-4v44-9qw9 CVE-2026-55535 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:N/A:N yes
GHSA-hvhp-v2gc-268q CVE-2026-47397 high yes
GHSA-hwg5-x759-7wjg CVE-2026-39891 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H yes
GHSA-j4hj-7hfh-g2f4 CVE-2026-57127 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-jfxc-v5g9-38xr CVE-2026-39305 critical CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H yes
GHSA-p4pj-vh7h-6cqh CVE-2026-57119 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-p75f-6fp4-p57w CVE-2026-57124 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-pj2r-f9mw-vrcq CVE-2026-40159 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
GHSA-pm96-6xpr-978x CVE-2026-40151 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-pv9q-275h-rh7x CVE-2026-40154 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N yes
GHSA-pvph-5j39-v8qc CVE-2026-55532 high CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:L yes

Showing 50 of 162 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 75 packages
Packages resolved 75
Stale 7
No linked repository 2
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.

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 still maintained?

PraisonAI is still listed as active in the MCP registry. We last reached this channel on 24 September 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.