Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/developer-ishan/mcp-pexelsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/developer-ishan/mcp-pexels/pexels)<a href="https://agentmods.dev/mcp/developer-ishan/mcp-pexels/pexels"><img src="https://agentmods.dev/badge/mcp/developer-ishan/mcp-pexels/pexels/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/developer-ishan/mcp-pexels/pexels"><img src="https://agentmods.dev/badge/mcp/developer-ishan/mcp-pexels/pexels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pexels scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"pexels": {
"command": "npx",
"args": [
"-y",
"mcp-pexels"
],
"env": {
"PEXELS_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A 25dcbd9f3bfd
pexels is an MCP server published in the GitHub repository developer-ishan/mcp-pexels (2 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-server
Agent-native global eSIM: buy for 193 countries, per-MB in USDT/USDC. Agents earn 20% referral. Runs locally from the @roamzy/mcp-server npm package. Needs 3 environment variables to run.
roamzy
MCP server for Roamzy — buy and manage global eSIM through Claude, Cursor, Continue, and any MCP client. Runs locally from the @roamzy/mcp-server npm package.
mcp
Provision Postgres databases + webhooks from AI coding agents in one HTTP call. Runs locally from the @instanode/mcp npm package. Needs 2 environment variables to run.
my-mcp-server
MCP server "my-mcp-server" as configured in jason-bourne-gg/my-mcp-server. Runs locally from the @jason-bourne-gg/my-mcp-server npm package.
git_bash
MCP server "gitbash" as configured in code-yeongyu/oh-my-openagent. Runs ../../git-bash-mcp/dist/cli.js with node.
whoop-mcp-server
MCP server "whoop-mcp-server" as configured in yuridivonis/whoop-mcp-server. Runs in Docker (ghcr.io/yuridivonis/whoop-mcp-server:1.4.1). Needs 7 environment variables to run.