Biomarker Investigation
AdvisoryAudited by Static analysis on May 13, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Installing and configuring the skill may give the connected PatSnap MCP service access under the user's PatSnap API account.
The skill requires a PatSnap API key for service access. This is expected for the stated integration, but the credential is sensitive and not declared in the registry requirements.
Log in to https://open.patsnap.com, go to **API Keys**, and create a new key.
Use a least-privilege, revocable PatSnap API key if available, avoid sharing it, and rotate it if it may have been exposed.
Biomarker queries and related research context may be processed by PatSnap's MCP service.
The skill relies on an external MCP server for its core functionality. The server and purpose are disclosed, but user prompts and research queries may be sent to that external service.
claude mcp add --transport http pharma_intelligence "https://connect.patsnap.com/096456/ogic-mcp?apiKey=sk-xxxxxxxxxxxx"
Do not send confidential, regulated, or proprietary research details unless your organization permits using PatSnap for that data.
Each use may trigger a small external connectivity check before the requested analysis begins.
The skill instructs the agent to make an automatic MCP tool call before answering. The call is narrow and disclosed, so this is a notice rather than a concern.
Before processing any user query after this skill loads, the following connectivity check MUST be performed. ... Use `ls_target_fetch` to look up EGFR by name
Be aware that loading the skill can cause an external PatSnap MCP lookup; disconnect the MCP server if you do not want that behavior.