UniProt MCP Server

Created By
vitamin3615a year ago
Overview

what is UniProt MCP Server?

The UniProt MCP Server is a Model Context Protocol server that enables language models to access protein information from the UniProt database, facilitating integration with AI applications like Claude Desktop.

how to use UniProt MCP Server?

To use the UniProt MCP Server, clone the repository, set up a virtual environment, install dependencies, and configure it with Claude Desktop to fetch protein data.

key features of UniProt MCP Server?

  • Search for proteins by name, gene, or other criteria.
  • Retrieve detailed information about proteins, including sequences and functions.
  • Access related PDB structures for proteins.

use cases of UniProt MCP Server?

  1. Finding proteins associated with specific diseases.
  2. Retrieving amino acid sequences for research purposes.
  3. Exploring functional annotations of proteins for academic studies.

FAQ from UniProt MCP Server?

  • Can I use this server with other AI applications?

Yes! The server is designed to be compatible with any MCP-compatible AI application.

  • Is there a license for using the UniProt MCP Server?

Yes, it is licensed under the MIT license, allowing for free use and modification.

  • How can I contribute to the project?

Contributions are welcome! You can fork the repository and submit a Pull Request with your changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vitamin3615
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Payai X402 Tools

2 hours ago
Payai X402 Tools

2 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago