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/Fish-Tacos/sati-commerce-demoWrote 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/fish-tacos/sati-commerce-demo/titan-store)<a href="https://agentmods.dev/mcp/fish-tacos/sati-commerce-demo/titan-store"><img src="https://agentmods.dev/badge/mcp/fish-tacos/sati-commerce-demo/titan-store/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/fish-tacos/sati-commerce-demo/titan-store"><img src="https://agentmods.dev/badge/mcp/fish-tacos/sati-commerce-demo/titan-store.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
titan-store 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 6 lines scan A 98e1353a0cd2
titan-store is an MCP server published in the GitHub repository Fish-Tacos/sati-commerce-demo (0 stars, last pushed 2mo ago), with no licence file. 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
waiaas
WAIaaS MCP server - Model Context Protocol integration for AI agents. Runs locally from the @waiaas/mcp npm package. Needs 2 environment variables to run.
flario
MCP server for Flare Network. FTSO price feeds, FDC cross-chain attestations with local proof verification, FAssets state, and x402 agent payments with chain-verified receipts. Works with Claude, Cursor, and any MCP client. Runs locally from the flario npm package. Needs 4 environment variables to run.
token-safety
Token safety check — honeypot, tax, proxy, blacklist, risk score. GoPlus-powered. x402. Remote server at token-safety.api.klymax402.com.
mcp-server
Agent commerce settlement tools on Base: treasury setup, payment splits, yield and attribution. Runs locally from the @clicks-protocol/mcp-server npm package. Needs 2 environment variables to run.
lucy-agent
MCP server "lucy-agent", hosted remotely at lucyagent.example.com, as configured in Woodman97/lucy-agent.
defi-yield-scanner-mcp
MCP server for DeFi yield scanning, token risk analysis, and portfolio tracking across Base, Ethereum, and Arbitrum. Runs locally from the defi-yield-scanner-mcp npm package.