In-depth, multi-region pharmaceutical intelligence search and synthesis, plus drug repurposing, target discovery, clinical evidence review, and bioactivity a...
Security Analysis
medium confidenceThis is a mostly coherent research skill, but it uses an undeclared third-party MCP endpoint and may send optional API keys through that endpoint without clear credential handling disclosures.
The skill’s purpose—pharmaceutical, regulatory, clinical-trial, patent, literature, and biomedical intelligence—is coherent with its documented use of public biomedical and regulatory data sources.
The skill asks the agent to consult it broadly for pharma or biomedical research questions and to perform multi-source searches; this is broad but aligned with the stated intelligence-gathering purpose.
There is no install spec and no code files; the skill is instruction-only.
The skill instructs the agent to call a third-party JSON-RPC MCP endpoint directly via web_fetch or curl, and some documented tool calls include user API keys even though no credentials are declared.
No persistence or local privilege escalation is shown, but the embedded _meta.json owner/version differs from the registry metadata, creating a provenance consistency note.
Guidance
Install only if you are comfortable with biomedical research queries being sent to mcp.sciminer.tech. Do not provide private company intelligence, unpublished research, patient information, or API keys unless you trust that endpoint and understand how it handles credentials.
Latest Release
v1.0.1
pharma-intelligence 1.0.1 - Search workflow and per-intent sequences have been moved to a dedicated reference file ([references/pharma-intelligence-workflow.md]). - Streamlined SKILL.md: now refers to newly added reference documentation for workflows and regional source maps. - Updated MCP server instructions: users must call the endpoint directly via HTTP POST using web_fetch or run_in_terminal; no built-in MCP tool. - Approval/trial workflows now emphasize explicit, step-by-step instructions and highlight which source to use when MCP coverage is lacking. - Centralized region-by-region source list and workflow examples into referenced documentation for easier updates and clarity.
More by @sciminer
Published by @sciminer on ClawHub
