MCP.Link

Why STEADY

STEADY (72) because MCP.Link targets a real integration bottleneck — one OpenAPI spec to MCP tools with no custom code — and exposes a coherent create/browse workflow plus a public links directory. Held near the STEADY floor because the captured surface is a landing page with no visible evidence of auth handling, rate limiting, large/non-conformant-spec behaviour, or an adoption/license signal.

Public-surface checklist

• PASS Homepage loads (required)
• PASS Primary value prop (required) — OpenAPI spec to MCP endpoints, no custom code
• PASS Cta present (required) — Create Link / Browse MCP Links / Get Started
• FAIL Pricing or access — No pricing or license surfaced on the captured page
• PASS Evidence or demo — How-It-Works section, links directory, connect-api page

What we saw

4 screenshots captured by the Hlido engine during the reviewed run (run-d77981dd1fefef48-mcp-link-vercel-app). Our own captures — not vendor marketing material.

×

←→

What it does well

• Transforms any OpenAPI spec + target API URL into MCP endpoints — no custom integration code
• Directly removes the per-API MCP-server-writing work that gates new agent integrations
• Coherent workflow: provide a spec, get a link, browse pre-configured links or create your own
• Public directory of MCP links plus GitHub and Discord community

What it fails at

• Reviewed surface is a marketing landing page (vercel.app) — limited evidence of production depth
• No captured evidence of authentication handling, rate limiting, or behaviour on large/non-conformant specs
• No visible license or adoption/star signal on the captured surface
• Reliability on messy real-world OpenAPI specs is asserted, not demonstrated here

Pricing & access

• Pricing findable on the public surfaceFAIL No pricing or license surfaced on the captured page (tested 2026-08-26)

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-08-26.

Compared to

• ViperJuice/mcp-gateway openapi-spec-generation-vs-gateway-routing

  Both bridge existing APIs to MCP; a gateway typically routes/manages many MCP servers, while MCP.Link's angle is spec-to-tools generation from an OpenAPI document. Gateway for centralized routing/management, MCP.Link for fast spec-driven tool creation.

• CentralMind Gateway openapi-source-vs-database-source

  CentralMind focuses on database-to-API/MCP exposure; MCP.Link focuses on OpenAPI-to-MCP for existing HTTP APIs. Different source of truth — pick by whether you start from a database or from an OpenAPI spec.

Agent relevance

API MCP Behavioral-testable

Agentic-Commerce Readiness 67/100 · INTEGRABLE

Independent readiness for agent delegation & transaction. How it’s scored · check live

You point MCP.Link at an OpenAPI spec URL and a target API; it produces MCP endpoints the assistant connects to, exposing the API's operations as MCP tools. This lets an agent call an existing HTTP API without a hand-written MCP server. Depends on the source API publishing a usable OpenAPI specification.

Agent-friendly score: 8/10

Evidence

• Transforms OpenAPI specifications into MCP endpoints with no custom code — source (2026-08-26) verified
• Works with any API that has an OpenAPI specification — source (2026-08-26) verified
• Provides a browsable directory of MCP links and a create-your-own flow — source (2026-08-26) verified