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/Nas01010101/tenetWrote 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/nas01010101/tenet/tenet-memory)<a href="https://agentmods.dev/mcp/nas01010101/tenet/tenet-memory"><img src="https://agentmods.dev/badge/mcp/nas01010101/tenet/tenet-memory/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/nas01010101/tenet/tenet-memory"><img src="https://agentmods.dev/badge/mcp/nas01010101/tenet/tenet-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tenet-memory 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 1mo 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
{ "tenet-memory": { "command": "uvx", "args": [ "tenet-memory" ] } }
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.
- 1mo ago First seen · 8 lines scan A dc85bcdf9d61
tenet-memory is an MCP server published in the GitHub repository Nas01010101/tenet (0 stars, last pushed 2mo 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
ai-memory
MCP server "ai-memory" as configured in alphaonedev/ai-memory-mcp. Runs in Docker (ghcr.io/alphaonedev/ai-memory:0.5.1). Needs 1 environment variable to run.
estonian
MCP server "estonian", hosted remotely at estonian-mcp.fly.dev, as configured in Elnora-AI/elnora-ai-agent-hackathon-starter-kit.
inspeximus
MCP server "inspeximus", hosted remotely at pypi.org, as configured in DanceNitra/inspeximus. Needs 1 environment variable to run.
llm-usage-mcp
Local-first, multi-provider tool that captures LLM API spend and exposes it to coding agents via MCP. Runs locally from the llm-usage-mcp Python package.
cortexm
Context-M: deterministic, auditable, zero-cost memory for AI agents. Runs locally from the cortexm Python package.
bagos
MCP server for Bags on Solana: token analytics, trade quotes, and gated write operations. Runs locally from the bagos-mcp-server npm package. Needs 11 environment variables to run.