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.
npx agentmods add mcp/globodai-group/mcp-github-dashboard/globodai-mcp-github-dashboardgit clone --depth 1 https://github.com/globodai-group/mcp-github-dashboardWrote 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/globodai-group/mcp-github-dashboard/globodai-mcp-github-dashboard)<a href="https://agentmods.dev/mcp/globodai-group/mcp-github-dashboard/globodai-mcp-github-dashboard"><img src="https://agentmods.dev/badge/mcp/globodai-group/mcp-github-dashboard/globodai-mcp-github-dashboard.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
globodai-mcp-github-dashboard 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 5d 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
{ "globodai-mcp-github-dashboard": { "command": "npx", "args": [ "-y", "globodai-mcp-github-dashboard" ] } }
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.
- 5d ago First seen · 9 lines scan A f3db0bc53861
globodai-mcp-github-dashboard is an MCP server published in the GitHub repository globodai-group/mcp-github-dashboard (1 stars, last pushed 7mo 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
git-steer
MCP server "git-steer" as configured in ry-ops/git-steer. Runs locally from the git-steer npm package.
github-twin
Personal RAG over your GitHub history (commits, code, review comments), served to Claude Code over MCP. Runs locally from the github-twin Python package. Needs 4 environment variables to run.
github-gist
MCP server to create, read, update, list, and search GitHub Gists from your IDE. Runs locally from the mcp-server-github-gist npm package.
github
GitHub's hosted MCP server: lets the agent search code, read and create issues and pull requests. Remote server at api.githubcopilot.com.
globodai-mcp-git
MCP server "globodai-mcp-git" as configured in globodai-group/mcp-git. Runs locally from the globodai-mcp-git npm package.
github-stars
MCP server "github-stars" as configured in 1036007003-wq/github-stars-mcp. Runs locally from the @1036007003-wq/github-stars-mcp npm package. Needs 2 environment variables to run.