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/ndunl075/alfred-pennyworthWrote 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/ndunl075/alfred-pennyworth/alfred-core)<a href="https://agentmods.dev/mcp/ndunl075/alfred-pennyworth/alfred-core"><img src="https://agentmods.dev/badge/mcp/ndunl075/alfred-pennyworth/alfred-core/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/ndunl075/alfred-pennyworth/alfred-core"><img src="https://agentmods.dev/badge/mcp/ndunl075/alfred-pennyworth/alfred-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
alfred-core 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 11d 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
{ "alfred-core": { "command": "uvx", "args": [ "alfred-core" ] } }
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.
- 11d ago First seen · 8 lines scan A 4883fe1c67c4
alfred-core is an MCP server published in the GitHub repository ndunl075/alfred-pennyworth (0 stars, last pushed 23d ago), licensed Apache-2.0. 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
mooncite
MCP server "mooncite" as configured in WhenMoon-afk/claude-memory-mcp. Runs dist/cli.js with node.
tg-recall
MCP server "tg-recall" as configured in Rerowros/tg-recall. Runs locally from the tg-recall Python package.
shelfmark
Give AI agents the right context, not your entire filesystem. A local, governed, metadata-only catalogue of the documents you already have — built for MCP. Runs locally from the shelfmark Python package.
agent-kudos
Local-first recognition and accomplishment infrastructure for AI agents. Runs locally from the agent-kudos npm package.
lexiconlocal
MCP server "lexiconlocal" as configured in alexeymohr/LexiconLocal. Runs locally from the lexiconlocal Python package.
finance
MCP server "finance" as configured in Marcusdt-UX/finance-mcp-server. Runs dist/index.js with node. Needs 1 environment variable to run.