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/theYahia/kaspi-mcpWrote 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/theyahia/kaspi-mcp/kaspi)<a href="https://agentmods.dev/mcp/theyahia/kaspi-mcp/kaspi"><img src="https://agentmods.dev/badge/mcp/theyahia/kaspi-mcp/kaspi/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/theyahia/kaspi-mcp/kaspi"><img src="https://agentmods.dev/badge/mcp/theyahia/kaspi-mcp/kaspi.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
kaspi 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 10d 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
{
"kaspi": {
"command": "npx",
"args": [
"-y",
"@theyahia/kaspi-mcp"
],
"env": {
"KASPI_API_KEY": "YOUR_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.
- 10d ago First seen · 12 lines scan A e217bbbe4e42
kaspi is an MCP server published in the GitHub repository theYahia/kaspi-mcp (0 stars, last pushed 5d 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
blockrun-mcp
Live data for AI agents: search, research, markets, crypto, X/Twitter. Pay per call. Runs locally from the @blockrun/mcp npm package. Needs 1 environment variable to run.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
frihet
AI-native MCP server for Frihet ERP — 157 canonical operations for invoicing, expenses, CRM, banking, POS and ES/EU fiscal workflows, with conservative capability and side-effect metadata. Runs locally from the @frihet/mcp-server npm package. Needs 1 environment variable to run.
erp
AI-native business management — 52 tools for invoicing, CRM, accounting & tax. Runs locally from the @frihet/mcp-server npm package.
ozon-mcp-server
MCP server for Ozon Seller API + Performance API: 151 tools for prices, promos, ads, orders, returns and finance. Runs locally from the ozon-mcp-server Python package. Needs 5 environment variables to run.
mindbox
MCP server for Mindbox — CDP, customer profiles, orders, segmentation (Russia). Runs locally from the @theyahia/mindbox-mcp npm package. Needs 2 environment variables to run.