Home / MCP registry index / com.seoapi/openai
com.seoapi/openai
com.seoapi/openai in the official MCP registry.
Endpoint https://openai.seoapi.com/mcp.
The registry describes it as: Validate GPTBot and OAI-SearchBot IP addresses. Remote MCP validate_ip tool.
We could not reach this server's endpoint on 2026-10-21. Nothing was checked.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-seoapi-openai)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
| io.github.DarthSander/agentdata-nl io.github.DarthSander/agentdata-nl | 53 tools, nothing matched 2026-10-22 |
| Cleanor app.cleanor/cleanor | 22 tools, nothing matched 2026-10-22 |
| AI Skill Store io.github.garasegae/aiskillstore | 18 tools, nothing matched 2026-10-21 |
| Diogenes Gemini Suite & Agents MCP io.github.stand-out-of-my-sun/diogenes-gemini-suite-mcp | 15 tools, nothing matched 2026-10-21 |
| TANDIU AI infrastructure data cn.tandiu/data | 14 tools, nothing matched 2026-10-22 |
| Pyfile LLM & Data API io.github.pyfile-toolkit/pyfile-llm | 13 tools, nothing matched 2026-10-21 |