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/sarthak-pansare/oci-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/sarthak-pansare/oci-mcp-server/oci)<a href="https://agentmods.dev/mcp/sarthak-pansare/oci-mcp-server/oci"><img src="https://agentmods.dev/badge/mcp/sarthak-pansare/oci-mcp-server/oci/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/mcp/sarthak-pansare/oci-mcp-server/oci"><img src="https://agentmods.dev/badge/mcp/sarthak-pansare/oci-mcp-server/oci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
oci 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 10d 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
{
"oci": {
"command": "uv",
"args": [
"--directory",
"/absolute/path/to/oci-mcp-server",
"run",
"oci-mcp-server"
]
}
}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.
- 10d ago First seen · 11 lines scan A 80a133539d93
oci is an MCP server published in the GitHub repository sarthak-pansare/oci-mcp-server (1 stars, last pushed 2mo ago), licensed Apache-2.0. 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
hostinger-api-mcp
MCP server for Hostinger API. Runs locally from the hostinger-api-mcp npm package. Needs 1 environment variable to run.
diagrams-so-mcp
Generate and edit AWS, Azure, GCP and Kubernetes architecture diagrams as editable draw.io files. Runs locally from the @diagrams-so/mcp npm package. Needs 3 environment variables to run.
vercel-mcp-pro
Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API. Runs locally from the vercel-mcp-pro npm package. Needs 3 environment variables to run.
antideploy-mcp
Deploy an application to Antideploy from a coding agent. MCP server and CLI. Runs locally from the antideploy-mcp npm package.
server-ops-mcp
Server ops MCP: logs, monitoring, code edit, Nginx & certs. Local + SSH, confirmations & redaction. Runs locally from the server-ops-mcp npm package. Needs 8 environment variables to run.
k8s-mcp-go
MCP server "k8s-mcp-go" as configured in kaneg/k8s-mcp-go. Launched with https://github.com/kaneg/k8s-mcp-go/releases/download/v0.4.6/k8s-mcp-go_0.4.6_da.