How do I install Ucsc Genome MCP?

You can install Ucsc Genome MCP using pip. Visit the official repository for exact commands and configuration.

What is Ucsc Genome MCP compatible with?

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

What is Ucsc Genome MCP best used for?

Ucsc Genome MCP is best for Design & Creative.

Clelp.ai

01SKILLDESIGN & CREATIVE / UCSC GENOME MCP

← all skillsDesign & Creative

Ucsc Genome MCP

by CommunityUpdated 5 months ago

“MCP server to interact with the UCSC Genome Browser API, letting you find genomes, chromosomes, and more.”— Community

npx -y @modelcontextprotocol/server-ucsc-genome-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 2, Networked.Reaches the live web, but needs no secrets. 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 out2 findings

MEDIUMucsc-genome-mcp.py:21 — Hardcoded external endpoint 'api.genome.ucsc.edu'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

MEDIUMvalidate_api.py:35 — Hardcoded external endpoint 'api.genome.ucsc.edu'. STATIC signal only: this flags a declared destination for human or dynamic-egress confirmation; it does NOT assert exfiltration.

Prompt-injection passthroughno flags

Whether it pipes untrusted external content back as agent instructions.

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