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/Dizko-Labs/dizko-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/dizko-labs/dizko-mcp/events)<a href="https://agentmods.dev/mcp/dizko-labs/dizko-mcp/events"><img src="https://agentmods.dev/badge/mcp/dizko-labs/dizko-mcp/events/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/dizko-labs/dizko-mcp/events"><img src="https://agentmods.dev/badge/mcp/dizko-labs/dizko-mcp/events.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
events 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 8d 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
{
"events": {
"command": "npx",
"args": [
"-y",
"dizko-events",
"mcp"
],
"env": {}
}
}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.
- 8d ago First seen · 11 lines scan A 9d3076951654
events is an MCP server published in the GitHub repository Dizko-Labs/dizko-mcp (0 stars, last pushed yesterday), 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
events
Agent-first Austin events concierge — fresh, sourced answers to what's happening in Austin. Remote server at yeehaw.bot.
touch-grass-mcp
MCP server "touch-grass-mcp" as configured in AG-Dynamics-GH/touch-grass-mcp. Runs locally from the touch-grass-mcp Python package.
etix-mcp
Etix event discovery for Claude — search events, venues & performers and fetch event details. Runs locally from the etix-mcp npm package. Needs 1 environment variable to run.
etix
MCP server "etix" as configured in chrischall/etix-mcp. Runs ${CLAUDE_PLUGIN_ROOT}/dist/bundle.js with node.
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
godot-mcp
MCP server for full Godot 4.x engine control with 165 tools for AI-driven game development. Runs locally from the @tugcantopaloglu/godot-mcp npm package.