Security-first MCP server that connects any OpenAPI, GraphQL, gRPC or SOAP API to AI agents.
MCPpedia last refreshed this data
io.github.TeodorMCP/universal-connector-mcp is an MCP server that security-first MCP server that connects any OpenAPI, GraphQL, gRPC or SOAP API to AI agents. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 85/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"universal-connector": {
"env": {
"UCMCP_ALLOWED_HOSTS": "api.github.com"
},
"args": [
"universal-connector-mcp"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Stop installing a new MCP server for every service: point this one at any OpenAPI/Swagger, GraphQL, gRPC or SOAP spec - or pick one from the built-in catalog of 2500+ public APIs - and your AI agent can call it. Securely, in fewer steps, with fewer tokens.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'universal-connector-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked universal-connector-mcp against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in developer-tools / ai-ml
MCP client bridge: connects to MCP servers and registers their tools on ctx.tools
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
An autonomous agent that conducts deep research on any data using any LLM providers
Chrome DevTools for coding agents
MCP Security Weekly
Get CVE alerts and security updates for io.github.TeodorMCP/universal-connector-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.

Stop installing a new MCP server for every service: point this one at any OpenAPI/Swagger, GraphQL,
gRPC or SOAP spec - or pick one from the built-in catalog of 2500+ public APIs - and your AI agent
can call it. Securely, in fewer steps, with fewer tokens.
Installation · Meta-tools · API catalog · Examples · Configuration · Security

Most "universal API" MCP servers only speak REST/OpenAPI. This project is built around three differentiators:
Operation model with pluggable spec adapters (OpenAPI, GraphQL, gRPC, SOAP). Tools and executors never care which protocol produced an operation.
The agent explores APIs like a filesystem instead of loading hundreds of tools at once (which would blow up the context window on large APIs like Stripe). It searches for operations, inspects the ones it needs, then executes them.
flowchart TD
Agent["AI Agent"] -->|"MCP stdio"| Server["FastMCP Server"]
Server --> Tools["Meta-tools"]
Tools --> Registry["Operation Registry (normalized)"]
Adapters["Spec Adapters"] --> Registry
Tools --> Guard["Security Guard"]
Guard --> Executor["Protocol Executors"]
Executor --> Auth["Auth Manager"]
Executor --> UpstreamAPI["Upstream API"]
| Tool | Purpose |
|---|---|
search_catalog | Find ready-to-load public APIs (curated list + APIs.guru directory, 2500+ specs) |
load_api | Register an API from a spec URL/file (protocol auto-detected) |
list_apis | List loaded APIs |
search_operations | Fuzzy-search operations across loaded APIs |
get_operation | Full parameter/response schema for one operation |
execute | Call an operation (auth + security guard applied); extract returns only the fields you ask for |
execute_chained | Run a sequence of operations in one call, piping results between steps; nested lists run in parallel |
execute_graph | Run a dependency g |