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.

Serena MCP: the IDE for your agent

PYPI · SERENA-AGENT

A powerful toolkit for coding, providing semantic retrieval and editing capabilities.

Available components

0 this week 34 Trust /100

Last scanned (14 hours ago)

Scores higher than 19% of PyPI servers

Category Developer Tools

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 Security82
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects cryptography 46.0.7, a direct dependency. A fixed version is available. View diagnostics → Fail
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 97 of 98 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks 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 we can run it. How we score packages →

What we tested

Checks we ran (9)

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

Checks we could not complete (5)

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.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, 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 0
    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-115563 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • CVE-2026-69249 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
  • 20 Nov 26 0
    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 affects this package: high ▼ security
    • CVE-2026-112913 affects this package: high ▼ security
    • CVE-2026-112909 affects this package: high ▼ security
    • CVE-2026-115563 affects this package: high ▼ security
    • CVE-2026-112939 affects this package: high ▼ security
    • CVE-2026-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • CVE-2026-69249 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
  • 19 Nov 26 +15
    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 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-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • CVE-2026-69249 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
    • Malware scan: unverified → pass ▲ security
  • 18 Nov 26 0
    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 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-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • CVE-2026-69249 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
  • 17 Nov 26 0
    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 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-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • CVE-2026-69249 affects this package: high ▼ security
    • CVE-2026-116684 affects this package: high ▼ security
    • CVE-2026-52870 affects this package: high ▼ security
  • 16 Nov 26 −15

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

    • CVE-2026-53537 affects this package: high ▼ security
    • CVE-2026-53538 affects this package: high ▼ security
    • CVE-2026-102598 affects this package: high ▼ security
    • CVE-2026-97687 affects this package: high ▼ security
    • CVE-2026-112915 affects this package: high ▼ security
    • CVE-2026-112936 affects this package: high ▼ security
    • GHSA-537c-gmf6-5ccf affects this package: high ▼ security
    • CVE-2026-112940 affects this package: high ▼ security
    • CVE-2026-59951 affects this package: high ▼ security
    • CVE-2026-97688 affects this package: high ▼ security
    • CVE-2026-48817 affects this package: high ▼ security
    • CVE-2026-116685 affects this package: high ▼ security
    • CVE-2026-97689 affects this package: high ▼ security
    • CVE-2026-69248 affects this package: high ▼ security
    • CVE-2026-54283 affects this package: high ▼ security
    • CVE-2026-59950 affects this package: high ▼ security
    • CVE-2026-116686 affects this package: high ▼ security
    • CVE-2026-112910 affects this package: high ▼ security
    • CVE-2026-54282 affects this package: high ▼ security
    • CVE-2026-48710 affects this package: high ▼ security
    • CVE-2026-53539 affects this package: high ▼ security
    • CVE-2026-112935 affects this package: high ▼ security
    • CVE-2026-112907 affects this package: high ▼ security
    • CVE-2026-53540 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-48818 affects this package: high ▼ security
    • CVE-2026-52869 affects this package: high ▼ security
    • CVE-2026-69247 affects this package: high ▼ security
    • Malware scan: pass → unverified ▼ security
  • 14 Nov 26 +21

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

  • 13 Nov 26 −21

    We did not load change detail this far back for this component, so this day may have recorded more than is shown.

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/serena-agent@1.5.3

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 hatchling.build

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

Vulnerabilities 53 findings
ID CVE Severity Vector Fix available
GHSA-537c-gmf6-5ccf high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g6cj-pr64-35w5 CVE-2026-69247 high yes
GHSA-jwv3-5hgf-82ww CVE-2026-69249 high yes
GHSA-m2h6-j472-rp4c CVE-2026-69248 medium yes
PYSEC-2026-3552 CVE-2026-69247 none yes
PYSEC-2026-3553 CVE-2026-69249 none yes
PYSEC-2026-3554 CVE-2026-69248 none yes
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-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-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-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-5h93-6whr-6q8j CVE-2026-116685 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-84m7-p3x7-pcfv CVE-2026-59951 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hvrp-rf83-w775 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-qx49-fqc8-xw99 CVE-2026-115563 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-rwrf-2pqf-9j8j CVE-2026-116686 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
GHSA-w4fh-qvv9-3v23 CVE-2026-116684 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
PYSEC-2026-3481 CVE-2026-52870 high CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes
GHSA-5rvq-cxj2-64vf CVE-2026-53539 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6jv3-5f52-599m CVE-2026-53538 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-v9pg-7xvm-68hf CVE-2026-53540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-vffw-93wf-4j4q CVE-2026-53537 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-3036 CVE-2026-53539 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-3037 CVE-2026-53538 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-3040 CVE-2026-53540 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L yes
PYSEC-2026-3041 CVE-2026-53537 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-82w8-qh3p-5jfq CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-86qp-5c8j-p5mr CVE-2026-48710 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-jp82-jpqv-5vv3 CVE-2026-54282 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-wqp7-x3pw-xc5r CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-x746-7m8f-x49c CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-161 CVE-2026-48710 none yes
PYSEC-2026-2280 CVE-2026-48817 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-2281 CVE-2026-48818 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-248 CVE-2026-54282 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-249 CVE-2026-54283 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8988-9cw3-xx77 CVE-2026-97687 high yes
GHSA-gh4c-6fx4-qh6g CVE-2026-97688 medium yes
GHSA-vxq7-64xx-v4gw CVE-2026-97689 high yes
PYSEC-2026-4175 CVE-2026-97687 none yes
PYSEC-2026-4176 CVE-2026-97688 none yes

Showing 50 of 53 vulnerabilities.

Background: What a vulnerability scan can and cannot prove →

Dependencies 97 packages
Packages resolved 97
Stale 10
No linked repository 2
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

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 Serena MCP: the IDE for your agent server?

Serena MCP: the IDE for your agent runs locally as a PyPI package, launched with uvx serena-agent. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · serena-agent

# add to Claude Code
claude mcp add oraios-serena -- uvx serena-agent

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

Common questions

What is the Serena MCP: the IDE for your agent server?

Serena MCP: the IDE for your agent is listed in the public MCP registry as io.github.oraios/serena. A powerful toolkit for coding, providing semantic retrieval and editing capabilities. This page covers its PyPI package (serena-agent).

Is the Serena MCP: the IDE for your agent server safe to use?

Serena MCP: the IDE for your agent scores 34 out of 100 on VerifyMCP. We recorded 53 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 Serena MCP: the IDE for your agent server still maintained?

Serena MCP: the IDE for your agent 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 Serena MCP: the IDE for your agent server under?

Serena MCP: the IDE for your agent 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 Serena MCP: the IDE for your agent server?

VerifyMCP ran 9 checks on Serena MCP: the IDE for your agent, covering Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 5 items could not be completed, a gap on our side rather than a finding about Serena MCP: the IDE for your agent: Schema quality, Stability, Tool coverage, Tool safety and 1 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.