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/cyanheads/met-museum-mcp-serverWrote 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/plugins/cyanheads/met-museum-mcp-server/met-museum-mcp-server)<a href="https://agentmods.dev/plugins/cyanheads/met-museum-mcp-server/met-museum-mcp-server"><img src="https://agentmods.dev/badge/plugins/cyanheads/met-museum-mcp-server/met-museum-mcp-server/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/plugins/cyanheads/met-museum-mcp-server/met-museum-mcp-server"><img src="https://agentmods.dev/badge/plugins/cyanheads/met-museum-mcp-server/met-museum-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
met-museum-mcp-server 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 today.
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
{
"name": "met-museum-mcp-server",
"version": "0.5.1",
"description": "Search the Metropolitan Museum of Art collection, fetch full artwork records and open-access images via MCP. STDIO or Streamable HTTP.",
"author": {
"name": "cyanheads"
},
"homepage": "https://github.com/cyanheads/met-museum-mcp-server#readme",
"repository": "https://github.com/cyanheads/met-museum-mcp-server",
"license": "Apache-2.0",
"mcpServers": {
"met-museum-mcp-server": {
"command": "npx",
"args": ["-y", "@cyanheads/met-museum-mcp-server"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio"
}
}
}
}
What it installs
The manifest is a name and a version. 33 skills, 1 MCP server travel with it, and installing the plugin installs all of them — 2,441 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill release-and-publish A 155 tokens
- Skill design-mcp-server A 62 tokens
- Skill add-tool A 35 tokens
- Skill api-linter A 86 tokens
- Skill api-context A 79 tokens
- Skill api-canvas A 85 tokens
- Skill api-errors A 54 tokens
- Skill api-testing A 46 tokens
- Skill maintenance A 75 tokens
- Skill orchestrations A 159 tokens
- Skill security-pass A 118 tokens
- Skill api-config A 43 tokens
- Skill api-telemetry A 85 tokens
- Skill git-wrapup A 104 tokens
- Skill polish-docs-meta A 54 tokens
- Skill tool-defs-analysis A 177 tokens
- Skill add-app-tool A 41 tokens
- Skill add-service A 38 tokens
- Skill add-test A 41 tokens
- Skill api-workers A 51 tokens
- Skill report-issue-framework A 52 tokens
- Skill report-issue-local A 44 tokens
- Skill setup A 58 tokens
- Skill add-resource A 32 tokens
- Skill api-auth A 58 tokens
- Skill api-mirror A 68 tokens
- Skill release-pr-review A 139 tokens
- Skill add-prompt A 37 tokens
- Skill api-utils A 37 tokens
- Skill code-simplifier A 124 tokens
- Skill techniques A 79 tokens
- Skill field-test B 93 tokens
- Skill api-services A 32 tokens
- MCP server met-museum-mcp-server A not measured
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.
- today Changed e009b2308784
- 10d ago First seen · 21 lines scan A 44eb3a14dc9a
met-museum-mcp-server is a plugin published in the GitHub repository cyanheads/met-museum-mcp-server (4 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
smithsonian-mcp-server
Search 14.5M Smithsonian Open Access objects across 20+ museums via MCP, and retrieve CC0 images for the 5.2M that carry openly-licensed media. STDIO or Streamable HTTP.
postey
Draft, schedule, and manage social media posts across X, LinkedIn, Instagram, TikTok, YouTube, Threads, Bluesky, Facebook, and Pinterest.
captain-memo
Cross-AI local memory layer (Claude Code, Codex, Gemini, Cursor) — hybrid search, three summarizer providers, self-hosted embedder. Replaces claude-mem.
worldbank-mcp-server
Query 29,500+ World Bank development indicators for 200+ countries across 60+ years via MCP. STDIO or Streamable HTTP.
treasury-fiscaldata-mcp-server
Query US Treasury national debt, interest rates, exchange rates, and fiscal datasets via MCP.
cpsc-recalls-mcp-server
Search and retrieve US consumer product recalls from the CPSC (Consumer Product Safety Commission) via MCP. STDIO or Streamable HTTP.