Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add genvjacobc/lightspeed-x-mcp/plugin install lightspeed-xWrote 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/genvjacobc/lightspeed-x-mcp/lightspeed-x)<a href="https://agentmods.dev/mcp/genvjacobc/lightspeed-x-mcp/lightspeed-x"><img src="https://agentmods.dev/badge/mcp/genvjacobc/lightspeed-x-mcp/lightspeed-x.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
lightspeed-x 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 7d 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
{
"lightspeed-x": {
"command": "node",
"args": [
"${CLAUDE_PLUGIN_ROOT}/dist/index.js"
],
"env": {
"LIGHTSPEED_ENV_FILE": "${CLAUDE_PLUGIN_DATA}/credentials.env"
}
}
}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.
- 7d ago First seen · 11 lines scan A b8253c5e9377
lightspeed-x is an MCP server published in the GitHub repository genvjacobc/lightspeed-x-mcp (0 stars, last pushed 12d 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.
lemonsqueezy-mcp
A Model Context Protocol (MCP) server for Lemon Squeezy — 44 audited tools over the official SDK, security-first. Works with any Lemon Squeezy account. Runs locally from the @heysash/lemonsqueezy-mcp npm package.
negotiate-mcp
MCP server for the negotiate.v1 protocol — gives AI agents native tools to negotiate at any negotiate.v1-compliant storefront. Runs locally from the negotiate-mcp Python package.
musette-mcp
AI soigneur for cyclists: Strava ride to an Ien-Vitse-validated nutrition plan + orderable box. Remote server at mcp.musette.cc.
robokassa-mcp
Comprehensive Python client and MCP server for Robokassa payment gateway. Runs locally from the robokassa-mcp Python package. Needs 4 environment variables to run.
sellercloud-mcp
MCP server "sellercloud-mcp" as configured in alveyautomation/sellercloud-mcp. Runs locally from the sellercloud-mcp Python package.