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/AceDataCloud/OpenAIMCPWrote 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/acedatacloud/openaimcp/mcp-openai)<a href="https://agentmods.dev/mcp/acedatacloud/openaimcp/mcp-openai"><img src="https://agentmods.dev/badge/mcp/acedatacloud/openaimcp/mcp-openai/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/acedatacloud/openaimcp/mcp-openai"><img src="https://agentmods.dev/badge/mcp/acedatacloud/openaimcp/mcp-openai.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
mcp-openai 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 21d 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
{
"mcp-openai": {
"command": "uvx",
"args": [
"mcp-openai-pro"
],
"env": {
"ACEDATACLOUD_API_TOKEN": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 21d ago Changed 36c33e5de200
- 1mo ago First seen · 11 lines scan A 3388e59ff9b3
mcp-openai is an MCP server published in the GitHub repository AceDataCloud/OpenAIMCP (1 stars, last pushed yesterday), 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
anythingllm-mcp
MCP server "anythingllm-mcp" as configured in andreperez/anythingllm-mcp. Runs locally from the anythingllm-mcp Python package.
mcp-aichat
MCP Server for AI Dialogue via AceDataCloud API. Runs locally from the mcp-aichat Python package. Needs 1 environment variable to run.
mcp-glm
MCP Server for GLM via AceDataCloud API. Runs locally from the mcp-glm Python package. Needs 1 environment variable to run.
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package. Needs 1 environment variable to run.
repomix
Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search. Runs locally from the repomix npm package.
email-mcp
IMAP/SMTP email MCP server — 52 tools, stdio + HTTP, IMAP IDLE push, multi-account, AI triage. Runs locally from the @codefuturist/email-mcp npm package.