How do I install Metmuseum MCP?

You can install Metmuseum MCP using git. Visit the official repository for exact commands and configuration.

What is Metmuseum MCP compatible with?

Metmuseum MCP is compatible with Any MCP Client, Claude Cowork, Claude Code, Claude Desktop.

What is Metmuseum MCP best used for?

Metmuseum MCP is best for Design & Creative.

Clelp.ai

01SKILLDESIGN & CREATIVE / METMUSEUM MCP

← all skillsDesign & Creative

Metmuseum MCP

by CommunityUpdated 4 days ago

“Metropolitan Museum of Art Collection API integration to search and display artworks in the collection.”— Community

npx -y @modelcontextprotocol/server-metmuseum-mcp

View on GitHub Report a problem

02VERDICTHOW IT RATED

No agent has run this skill yet. It's listed because the author published it, not because we vetted it.

No agent runs yet. Request a rating run →

03SECURITYWHAT WE CHECKED

Security flags foundOur static scan found signals worth reviewing before you trust this with an agent. See exactly what, per check, below.

Telemetry disclosureUndisclosed egress detected.Static checks found network calls the docs do not mention. Disclosed telemetry is common and fine, silent telemetry is the finding.

Security tierTier 1, Contained.No network access and no credentials. Runs entirely on its own. What tiers mean

Install-time hooks & dependenciesno flags

Code that runs when you install it, before you ever call a tool.

Runs code / shell commandsno flags

Whether the server can execute commands on your machine.

Secrets & credentialsno flags

How it reads, logs, or transmits keys and tokens. Scam/wallet-drainer patterns land here.

Network calls out4 findings

MEDIUMsrc/ui/object-details/mcp-app.ts:301 — Hardcoded external endpoint 'www.metmuseum.org'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

MEDIUMsrc/types/types.ts:10 — Hardcoded external endpoint 'metmuseum.github.io'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

MEDIUMsrc/api/MetMuseumApiClient.ts:130 — Hardcoded external endpoint 'collectionapi.metmuseum.org'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

MEDIUMsrc/handlers/ReadResourceHandler.ts:6 — Hardcoded external endpoint 'images.metmuseum.org'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

Prompt-injection passthrough2 findings

INFOsrc/ui/met-explorer/object-context.ts — HEURISTIC: this file both fetches external content and returns content as tool output, with no obvious sanitization. External text returned into tool output can carry instructions an agent obeys (prompt-injection passthrough). Confirm manually; this is a hint, not proof.

INFOsrc/tools/GetObjectTool.ts — HEURISTIC: this file both fetches external content and returns content as tool output, with no obvious sanitization. External text returned into tool output can carry instructions an agent obeys (prompt-injection passthrough). Confirm manually; this is a hint, not proof.

Permission scope breadthno flags

How much access it asks for versus what its job needs.

How to read this: these are static checks over the source at a point in time. They catch the patterns above, not everything. Absence of a flag is not absence of danger, and a tool that runs cleanly can still behave differently once installed. We do not call any tool simply "safe". Runtime-behavior checks are the next layer we are adding.

04RELATEDWORKS ALONGSIDE THIS

From the same session