Unofficial Human Protein Atlas MCP Server

Created By
Augmented-Naturea year ago
Overview

what is ProteinAtlas-MCP-Server?

ProteinAtlas-MCP-Server is an unofficial server that provides comprehensive access to the Human Protein Atlas data, focusing on protein expression, localization, and pathology information.

how to use ProteinAtlas-MCP-Server?

To use the server, clone the repository, install the dependencies, and run the server. You can also integrate it with your MCP client for seamless data access.

key features of ProteinAtlas-MCP-Server?

  • Comprehensive protein search and information retrieval
  • Access to tissue-specific expression profiles
  • Subcellular localization data
  • Cancer-related pathology information
  • Batch processing for multiple protein queries
  • Advanced search capabilities with multiple filters

use cases of ProteinAtlas-MCP-Server?

  1. Researchers looking for detailed protein expression data.
  2. Cancer researchers needing pathology data for specific proteins.
  3. Developers integrating protein data into applications.
  4. Educators using protein data for teaching purposes.

FAQ from ProteinAtlas-MCP-Server?

  • Is the server free to use?

Yes! The ProteinAtlas-MCP-Server is free to use for research and educational purposes.

  • What data sources does the server access?

The server accesses data from the Human Protein Atlas, Tissue Atlas, Blood Atlas, Brain Atlas, and Pathology Atlas.

  • How can I contribute to the project?

Contributions are welcome! Please follow the guidelines in the repository for code contributions and documentation updates.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Augmented-Nature
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago