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/observer-protocol/at-directoryWrote 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/observer-protocol/at-directory/directory)<a href="https://agentmods.dev/mcp/observer-protocol/at-directory/directory"><img src="https://agentmods.dev/badge/mcp/observer-protocol/at-directory/directory/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/observer-protocol/at-directory/directory"><img src="https://agentmods.dev/badge/mcp/observer-protocol/at-directory/directory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
directory 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.
This is a copy
88% identical to mcp — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{ "directory": { "url": "https://mcp.agenticterminal.ai/mcp", "type": "streamable-http" } }
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 · 6 lines scan A 7e743e8adf15
directory is an MCP server published in the GitHub repository observer-protocol/at-directory (0 stars, last pushed 18d 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. It is 88% identical to mcp, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
opensea
MCP server "opensea", hosted remotely at mcp.opensea.io, as configured in ProjectOpenSea/opensea-skill.
x402-commerce
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 8 environment variables to run.
x402-commerce-solana
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 7 environment variables to run.
x402-commerce-sandbox
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 4 environment variables to run.
loyal-spark
Base MCP (39 tools) on Base: programs, mint, rewards. lsk key; plan limits enforced. /for-agents. Remote server at api.loyalspark.online.
marketplace-mcp
Publish Nostr marketplace listings (NIP-15 + Shopstr kinds 30019/30402) so agents can run a store. Runs locally from the marketplace-mcp npm package. Needs 4 environment variables to run.