unified-gateway-mcp

Provides an MCP (Model Context Protocol) gateway that aggregates many external MCP tools/services behind two meta-tools—`search` to discover tools and `execute` to run a selected tool—with authentication via API key or OAuth2.

Evaluated Mar 30, 2026 (0d ago)
Homepage ↗ Repo ↗ DevTools mcp agent-tools gateway ai-agents tool-discovery tool-execution typescript marketplace oauth api-key
⚙ Agent Friendliness
54
/ 100
Can an agent use this?
🔒 Security
67
/ 100
Is it safe for agents?
⚡ Reliability
22
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
65
Error Messages
0
Auth Simplicity
70
Rate Limits
45

🔒 Security

TLS Enforcement
95
Auth Strength
80
Scope Granularity
35
Dep. Hygiene
45
Secret Handling
70

The README claims TLS 1.3, OAuth token refresh, audit logs, rate limiting, DDoS protection, and anomaly detection, but the provided text does not show concrete implementation details. API keys are passed via environment variables in client configs (better than embedding in code), but explicit guidance on secret storage/redaction and token scope minimization is not evidenced.

⚡ Reliability

Uptime/SLA
20
Version Stability
25
Breaking Changes
20
Error Recovery
25
AF Security Reliability

Best When

You want agents to access many MCP-backed tools with minimal integration effort and can authenticate to MCP360.

Avoid When

You require comprehensive, versioned API contracts (OpenAPI/SDK), explicit rate-limit headers, or documented idempotency/retry behavior for reliability-critical operations.

Use Cases

  • Search and select from a large marketplace of MCP tools
  • Dynamically run heterogeneous actions (e.g., SEO, email verification, web scraping) through a single gateway
  • Build agent workflows (Claude/Cursor/VS Code integrations) without integrating each underlying API separately
  • Use/attach custom MCP servers via the same unified gateway interface

Not For

  • High-assurance environments requiring formally specified SLAs/error contracts that are not documented in the README
  • Workloads where you need direct, first-party access to specific APIs instead of an aggregated abstraction
  • Use cases requiring strict, documented data residency or compliance guarantees beyond marketing claims (not evidenced in provided text)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: API key (MCP360_API_KEY) OAuth 2.0 (browser sign-in fallback when API key not provided)
OAuth: Yes Scopes: No

README describes API key configuration and an OAuth2 automatic fallback flow. Provided text does not document exact scopes/permissions granularity for OAuth.

Pricing

Free tier: No
Requires CC: No

Pricing details and limits are not present in the provided README excerpt.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • `execute` is a dynamic router; if tool parameters don’t match the selected tool’s schema, errors may be opaque because schema validation/error formats are not shown in the provided text.
  • Search results may vary based on connected marketplace/custom MCP availability, so an agent may need to re-search before executing in long-running sessions.
  • No documented retry/idempotency semantics for `execute`, so agents should avoid blind retries for side-effecting tools.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for unified-gateway-mcp.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-30.

6533
Packages Evaluated
19870
Need Evaluation
586
Need Re-evaluation
Community Powered