技能潮 SkillTide 提交收录
官方说明7 个来源MCP 服务8 天前
smaniches/uniprot-mcp

smaniches/uniprot-mcp

Query the UniProt knowledg
在 GitHub 查看 ↗直链 · 无中转页
配置模板(请按你的客户端调整)
claude mcp add uniprot-mcp -- npx -y uniprot-mcp
这是根据仓库名生成的可粘贴骨架,命令行参数与包名请以该项目 README 为准。
★ 数取值
3 ★ · smaniches/uniprot-mcp · 取自该仓库的 GitHub 页面 · (2026-10-16 20:00:20 核对)
来源明细
收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
收录与活跃
收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
评分构成
综合分 703 · 3 ★ · 7 个来源 · mcp
常见问题(答案都来自我们的记录)
怎么安装?
我们【没有】从该仓库取到安装命令(我们的 install 覆盖率只有约 4%)。请看它的 README 或 releases 页。
它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库 smaniches/uniprot-mcp;我们收录于 2026-10-09;最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。
第三方质量标记

UniProt MCP Server

以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →

Produce verifiable, release-aware protein evidence packages from UniProt and linked scientific sources.
Use this MCP server to find proteins, assemble protein, target, and variant evidence, and keep a checkable record of where each result came from. Each successful response records the UniProt release, retrieval time, resolved source URL, and a SHA-256 digest. uniprot_provenance_verify can later determine whether the upstream record is unchanged or has drifted.
The complete tool catalog remains available for specialized research workflows.
> Author: **Santiago Maniches** · ORCID 0009-0005-6480-1987 · TOPOLOGICA LLC
**Research authorship:** Santiago Maniches independently maintains this server and is the sole scientific author of its project-specific research contributions. AI-assisted tools have supported development, testing, and internal review under his direction. UniProt records, linked source data, and underlying third-party methods retain their original authorship; internal tool-assisted review is not external scientific validation.
**Run it in one line:**
---
Verifiable provenance (the receipts)
Every answer this server returns is traceable to a primary-source URL **and**
a content hash you can re-compute yourself. The walkthrough below is a real
run against the live server (UniProt release 2026_01), independently
confirmed against the UniProt REST API.
**Question.** What is the function of human p53 (UniProt P04637), what
heritable cancer syndrome is it associated with, and is the R175H mutation
a documented disease variant?
**Answer, with its provenance footer (verbatim from the server):**
- **Function.** *Cellular tumor antigen p53* (gene TP53, *Homo sapiens*,
393 aa). "Multifunctional transcription factor that induces cell cycle
arrest, DNA repair or apoptosis... Acts as a tumor suppressor in many tumor
types."
- **Disease.** *Li-Fraumeni syndrome* (acronym LFS, UniProt disease id
DI-01904, OMIM 151623) — "an autosomal dominant familial cancer
syndrome... Four types of cancers account for 80% of tumors occurring in
TP53 germline mutation carriers."
- **Variant.** R175H — "in LFS; germline mutation and in sporadic cancers;
somatic mutation; does not induce SNAI1 degradation; reduces interaction
with ZNF385A; dbSNP:rs28934578."
Reproduce it
**1. Run the server and ask the same question** (any MCP client; tool calls shown):
**2. Confirm the hash re-verifies** (re-fetches the URL and re-checks the
release + canonical hash with the server's own code):
**3. Confirm the values against the primary source — no server in the loop:**
**What this proves:** every returned claim is traceable to a primary-source
URL and a content hash. The gene, protein name, disease (with OMIM id), and
variant the server reports all match the live UniProt entry; the footer
SHA-256 is reproducible byte-for-byte from the primary source using a
documented, server-independent recipe. A third party can re-run all three
checks today, or a year from now, without trusting this server.
> Note on the hash: the footer SHA-256 is of the *canonical* UniProt response
> body — the JSON re-serialized with sorted keys and compact separators
> (json.dumps(obj, sort_keys=True, separators=(",", ":"), ensure_ascii=False)),
> so harmless key-order changes within a release do not break verification. A raw
> curl | sha256sum of the bytes will therefore differ; apply the same
> canonicalization (step 3 above) or use uniprot_provenance_verify.
---
Installation
Run without installing (recommended):
Or install into an environment:
> **Note:** There is an unrelated package named uniprot-mcp on PyPI
> (different author, 5 tools, MIT). This package is uniprot-mcp-server.
> Running pip install uniprot-mcp will install the wrong package silently.
For researchers — where to start
If you are a biomedical researcher visiting this repo, the highest-signal places to look are:
| Resource | What it gives you |
|---|---|
| **examples/atlas/** | Two artifacts with deliberately different scopes: • **Curated atlas (25 entries).** TP53, BRCA1, CFTR, HTT, EGFR, BRAF, KRAS, TEM-1 β-lactamase, more — each linking the canonical UniProt accession to MONDO / OMIM / PharmGKB / ARO IDs and the relevant tool sequence. JSON-LD manifest at examples/atlas/atlas.json. • **Comprehensive index (11,590 rows).** UniProt's curated disease + pathogen surface as two TSVs (comprehensive_index.tsv 7,250 human disease rows, comprehensive_index_pathogens.tsv 4,340 pathogen rows). Each row carries a UniProt disease ID and an OMIM cross-reference where available. MONDO / PharmGKB / ARO mappings exist only in the 25-entry curated atlas, not in the 11,590-row index. SHA-256 reproducibility manifest at examples/atlas/manifest.json. Methodology (how compiled, what's verified, what's community-reviewable) at examples/atlas/METHODOLOGY.md. |
来源
awesome · https://github.com/smaniches/uniprot-mcp
按领域浏览
MCP 服务
Traction
3 ★
收录于
昨天

更多MCP 服务

查看MCP 服务全部 5,525 条 →

所属领域与标签

每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。

浏览全部领域 →

← 返回索引