Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/heliosarchitect/wems-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/heliosarchitect/wems-mcp-server/wems)<a href="https://agentmods.dev/mcp/heliosarchitect/wems-mcp-server/wems"><img src="https://agentmods.dev/badge/mcp/heliosarchitect/wems-mcp-server/wems.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
wems scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"wems": {
"command": "uvx",
"args": [
"wems-mcp-server"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 9 lines scan A ec77e9ae4f2f
wems is an MCP server published in the GitHub repository heliosarchitect/wems-mcp-server (1 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
health-system-profiler
MCP server "health-system-profiler" as configured in ajhcs/healthcare-data-mcp. Launched with hc-mcp health-system-profiler.
openfoodfacts-mcp-server
Barcode lookup, nutrition search, and product comparison for 3M+ crowd-sourced food products. Runs locally from the @cyanheads/openfoodfacts-mcp-server npm package. Needs 5 environment variables to run.
clinical-trials-ai-mcp
MCP server for clinical trials ai. Features search trials, check eligibility, get trial details. From MEOK AI Labs. Runs locally from the clinical-trials-ai-mcp Python package.
ensembl
Ensembl REST — vertebrate genomes, sequences, comparative genomics, variation. Remote server at gateway.pipeworx.io.
biopharma-mcp
Enterprise-grade MCP server for Biopharma software infrastructure, FDA 21 CFR Part 11 audit logging, CDISC SDTM exports, 4PL curves, and HIPAA PII redaction. Runs locally from the @seosiri/biopharma-mcp npm package.
mcp-airq
MCP server for direct HTTP communication with air-Q air quality sensor devices. Runs locally from the mcp-airq Python package. Needs 2 environment variables to run.