← Home

@executor-js/plugin-mcp

npm Repository Homepage

Register [Model Context Protocol](https://modelcontextprotocol.io) servers as tool sources for an executor. Supports both stdio-launched servers and remote (HTTP) servers, with optional OAuth.

48
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

rhyssullivan

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher is consistent with SLSA-attested automated release pipeline for this repo. ai
phantom-deps phantom-dep:@cfworker/json-schema AI (phantom-deps): Dep is bundled into dist output; not directly imported in source but legitimately used. ai
phantom-deps phantom-dep:@effect/platform-node AI (phantom-deps): @effect/platform-node is a runtime dep in package.json; phantom-dep is a false positive for this package. ai

Versions (showing 48 of 48)

Version Deps Published
2.0.0 6 / 9
1.5.34 6 / 9
1.5.33 6 / 9
1.5.32 6 / 9
1.5.31 6 / 9
1.5.30 6 / 9
1.5.29 6 / 9
1.5.28 6 / 9
1.5.27 6 / 9
1.5.26 6 / 9
1.5.25 6 / 9
1.5.24 6 / 9
1.5.23 6 / 9
1.5.22 6 / 9
1.5.21 6 / 9
1.5.20 6 / 9
1.5.19 6 / 9
1.5.18 6 / 9
1.5.17 6 / 9
1.5.16 6 / 9
1.5.15 6 / 9
1.5.14 6 / 9
1.5.13 6 / 9
1.5.12 6 / 9
1.5.11 6 / 9
1.5.10 6 / 9
1.5.9 6 / 9
1.5.8 6 / 9
1.5.7 6 / 9
1.5.1 6 / 9
1.5.0 6 / 9
1.4.33 7 / 8
1.4.32 7 / 8
1.4.31 6 / 9
1.4.30 6 / 9
1.4.29 6 / 10
1.4.28 6 / 10
1.4.27 6 / 10
1.4.26 6 / 10
1.4.25 6 / 10
1.4.24 6 / 10
1.4.23 6 / 10
1.4.21 6 / 10
1.4.20 6 / 10
0.2.1 6 / 10
0.1.0 5 / 10
0.0.2 5 / 10
0.0.1 6 / 11

v2.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.34

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.33

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.32

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.31

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.30

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.29

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.28

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.27

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.26

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.25

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.24

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.22

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.5.21

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.2

2 findings
HIGH Provenance attestation missing — previous versions had it provenance

This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.

INFO Publisher changed: GitHub Actions → rhyssullivan (on 2026-05-02, known maintainer) provenance

This version was published by a different npm account (rhyssullivan) than the most recent previously approved version (GitHub Actions) on 2026-05-02, but rhyssullivan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.