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/awizemann/scarfWrote 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/awizemann/scarf/memophant)<a href="https://agentmods.dev/mcp/awizemann/scarf/memophant"><img src="https://agentmods.dev/badge/mcp/awizemann/scarf/memophant/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/awizemann/scarf/memophant"><img src="https://agentmods.dev/badge/mcp/awizemann/scarf/memophant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
memophant 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 9d 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
{
"memophant": {
"args": [
"--project-root",
".",
"--default-project",
"scarf"
],
"command": "./.memophant/mcp/memophant-mcp",
"type": "stdio"
}
}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.
- 9d ago First seen · 12 lines scan A 8f706baae71d
memophant is an MCP server published in the GitHub repository awizemann/scarf (849 stars, last pushed 4d 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-30.
Other mcp servers, from other repositories
personal-model
Local-first macOS Runtime for screen-context memory, personal modeling, and MCP. Runs locally from the personal-model Python package.
memophant
MCP server "memophant" as configured in awizemann/harness. Launched with ./.memophant/mcp/memophant-mcp --project-root . --default-project harness.
markview
Native macOS markdown preview with MCP server for Claude Code. Swift/SwiftUI, no Electron. Runs locally from the mcp-server-markview npm package.
plonk
MCP server for Plonk, a macOS window manager: zones you draw yourself, workspaces, keep-awake, screenshots and on-device OCR, as tools an agent can call. Runs locally from the plonk-mcp npm package.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
assemblyai-docs
MCP server "assemblyai-docs", hosted remotely at mcp.assemblyai.com, as configured in AssemblyAI/blurt.