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/SocialGOcompany/socialgo-toolsWrote 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/socialgocompany/socialgo-tools/socialgo)<a href="https://agentmods.dev/mcp/socialgocompany/socialgo-tools/socialgo"><img src="https://agentmods.dev/badge/mcp/socialgocompany/socialgo-tools/socialgo/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/socialgocompany/socialgo-tools/socialgo"><img src="https://agentmods.dev/badge/mcp/socialgocompany/socialgo-tools/socialgo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
socialgo 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 11d 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
{
"socialgo": {
"command": "npx",
"args": [
"-y",
"@socialgo/mcp"
],
"env": {
"SOCIALGO_API_KEY": "",
"SOCIALGO_TOKEN": "",
"SOCIALGO_API_URL": ""
}
}
}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.
- 11d ago First seen · 14 lines scan A 87db874e7f0a
socialgo is an MCP server published in the GitHub repository SocialGOcompany/socialgo-tools (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
src-mcp
MCP server for semantic code search and codebase analysis — Treesitter parsing, AST extraction, and embedding-based indexing for any LLM that supports MCP. Runs locally from the src-mcp npm package.
toreva
Policy-checked Solana wallet actions. Users set the limits. Toreva reads, simulates, prepares unsigned transactions, explains, and receipts every outcome. Runs locally from the @toreva/mcp npm package. Needs 1 environment variable to run.
kit
Policy-checked Solana wallet actions with user-set limits, unsigned transactions, and receipts. Runs locally from the @toreva/mcp npm package.
astravue
MCP server "astravue", hosted remotely at api.astravue.com, as configured in AstravueOrg/astravue-mcp-server.
ellmos-filecommander-mcp
Filesystem MCP server: files, processes, sessions, async search, OCR, archives, safe delete. Runs locally from the ellmos-filecommander-mcp npm package.
umami
MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime. Runs locally from the @mikusnuz/umami-mcp npm package. Needs 4 environment variables to run.