Pexels
NPM · @PIPEWORX/MCP-PEXELS · 2 COMPONENTS
Pexels MCP.
Available components
Last scanned (15 hours ago)
Scores higher than 69% of npm servers
Category Design and Media
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pexels). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 391 tokens (~48/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 5 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-pexels@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-pexels |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pexels/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685283051 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:528b62eaea9ca01fbd1793b720328b4f12e5e0e192cbf3bd47a224f26e204ea3e6aa84d0b3ca77b6924dbd8714d7424bae7e9119db1015f511dcd6b55 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
collection_media ~42
Fetch all photos and videos inside a specific Pexels collection by string id; returns paginated mixed media objects with URLs and metadata.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
featured_collections ~34
List Pexels' featured curated collections; returns collection id, title, description, and media counts for photos and videos.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
photo ~45
Fetch full metadata for a single Pexels photo by numeric id, including all sized image URLs, photographer name/URL, dimensions, and alt text.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
photo_curated ~45
Fetch Pexels' curated editorial photo feed; returns paginated photo objects with image URLs in multiple sizes (original, large, medium, small, tiny) and photographer info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
photo_search ~43
Search Pexels photos by keyword (required); returns paginated results with image URLs in multiple sizes, photographer name, and attribution link.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
video ~47
Fetch full metadata for a single Pexels video by numeric id, including file URLs at all available resolutions, duration, width, height, and videographer attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| id | number | yes | – |
No output schema declared.
No examples provided.
video_popular ~37
Fetch Pexels' popular video feed; returns paginated video objects with file URLs at multiple resolutions, duration, and videographer info.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
video_search ~44
Search Pexels videos by keyword (required); returns paginated results with video file URLs at multiple resolutions, duration, and videographer info.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Pexels MCP server?
Pexels runs locally as an npm package, launched with npx -y @pipeworx/mcp-pexels. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-pexels
claude mcp add pipeworx-io-pexels -- npx -y @pipeworx/mcp-pexels
What is the Pexels MCP server?
Pexels is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pexels. Pexels MCP. This page covers its npm package (@pipeworx/mcp-pexels).
Is the Pexels MCP server safe to use?
Pexels scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.
What tools does the Pexels MCP server expose?
Pexels exposes 8 tools: photo_search, photo_curated, photo, video_search, video_popular, and 3 more. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.
Is the Pexels MCP server still maintained?
Pexels is still listed as active in the MCP registry. We last reached this channel on 5 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 Pexels MCP server under?
Pexels 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 Pexels MCP server?
VerifyMCP ran 16 checks on Pexels, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.