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/shingou-io/shingou-skillsWrote 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/shingou-io/shingou-skills/shingou-shingou)<a href="https://agentmods.dev/mcp/shingou-io/shingou-skills/shingou-shingou"><img src="https://agentmods.dev/badge/mcp/shingou-io/shingou-skills/shingou-shingou/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/shingou-io/shingou-skills/shingou-shingou"><img src="https://agentmods.dev/badge/mcp/shingou-io/shingou-skills/shingou-shingou.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
shingou 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 9d 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
{
"shingou": {
"type": "http",
"url": "${SHINGOU_MCP_URL:-https://api.shingou.io/mcp}",
"headers": {
"x-api-key": "${SHINGOU_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.
- 9d ago First seen · 9 lines scan A b379a84b9416
shingou is an MCP server published in the GitHub repository shingou-io/shingou-skills (0 stars, last pushed 1mo 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
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.
finance-mcp
Live stock, crypto, SEC filings, insider trades, FX and macro data for LLM agents. Runs locally from the finance-data-mcp npm package. Needs 1 environment variable to run.
autonomous-intelligence
MCP server for the Autonomous Intelligence agent execution rail — non-custodial multi-chain token swaps, rug-gate safety checks, and gem discovery. Discovery tools are keyless; swap execution uses a self-serve key and is non-custodial (your key never leav. Runs locally from the autonomousintelligence-mcp npm package.…
pikasim
MCP server "pikasim", hosted remotely at pikasim.com, as configured in codebruinc/pikasim-mcp.
patternfetch
US stocks, ETFs, crypto → compact brief: patterns, S/R, regime + base rates vs baseline. Not advice. Remote server at patternfetch.com.
binance-mcp
MCP server for live crypto trading via Binance.US with comprehensive market intelligence, news, and advanced analytics. Runs locally from the binance-mcp Python package.