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/zv-louis/updstsWrote 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/plugins/zv-louis/updsts/updsts)<a href="https://agentmods.dev/plugins/zv-louis/updsts/updsts"><img src="https://agentmods.dev/badge/plugins/zv-louis/updsts/updsts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/zv-louis/updsts/updsts"><img src="https://agentmods.dev/badge/plugins/zv-louis/updsts/updsts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
updsts-mcp 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 22d 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
{
"name": "updsts-mcp",
"description": "Get and update AWS STS credential using existing AWS profile.",
"version": "0.8.8",
"author": {
"name": "kanok-one",
"email": "[email protected]"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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.
- 22d ago First seen · 11 lines scan A c535faa3e9f2
updsts-mcp is a plugin published in the GitHub repository zv-louis/updsts (0 stars, last pushed 23d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-26.
Other plugins, from other repositories
unifi-network
UniFi Network MCP server — manage network devices, clients, firewall, VPN, and more.
cloud-run
MCP configuration declaring 1 server: cloud-run.
harness-mcp
AI-native interface to the Harness Platform — ask questions, diagnose failures, and manage deployments without leaving your terminal.
obto
Build, deploy, and operate apps on the OBTO platform — one MCP connection (Google sign-in, auto-provisioned workspace), a /obto:start session command, plus skills for the build loop, large-file deploys (patch-in-place, chunked, and deploy-by-reference), media/binary upload (signed-URL and chunked), agent memory…
aws-billing
Get a non-expert from zero to a Slack-delivered, plain-English, waste-flagged AWS bill breakdown - and cache it so you don't pay per Cost Explorer call.
axcient
Every x360Recover endpoint, plus the fleet-wide backup-health answers the API alone can't give — offline, joined, and agent-ready.