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/gohluke/dayze-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/gohluke/dayze-mcp/dayze)<a href="https://agentmods.dev/mcp/gohluke/dayze-mcp/dayze"><img src="https://agentmods.dev/badge/mcp/gohluke/dayze-mcp/dayze/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/gohluke/dayze-mcp/dayze"><img src="https://agentmods.dev/badge/mcp/gohluke/dayze-mcp/dayze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dayze 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
{
"dayze": {
"type": "http",
"url": "https://dayze.com/api/mcp"
}
}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 · 6 lines scan A f7dd5de9b603
dayze is an MCP server published in the GitHub repository gohluke/dayze-mcp (0 stars, last pushed 7d 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-09-04.
Other mcp servers, from other repositories
hive-mcp-backup
Snapshot and restore service for agent state and DID-bound configuration. Remote server at hive-mcp-backup.onrender.com.
hive-mcp-agent-storage
Encrypted A2A object storage for autonomous agent state and artifacts. Remote server at hive-mcp-agent-storage.onrender.com.
prism-coder
Session memory for coding agents: local-first recall, drift detection, on-device inference. Runs locally from the prism-mcp-server npm package. Needs 8 environment variables to run.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
hypermnesia-mcp
Scientifically-grounded memory system based on computational neuroscience research. Runs locally from the hypermnesia-mcp Python package.
state-memory-mcp
Deterministic, persistent graph server for tracking workflow state, decisions, and blockers. Runs locally from the @putervision/state-memory-mcp npm package.