MCP infrastructure vendors

64 vendors from seven layers around MCP servers, read on 5 November 2026: 10 hosts and runtimes, 8 registries and directories, 13 gateways and proxies, 9 auth providers, 6 security scanners, 8 SDKs and frameworks and 10 connector platforms. Two agent-readiness checks sit beside each vendor's domain.

How the list was built

The list is one row per company. A company that sells more than one layer is typed by its main one, and the others show on its profile as secondary layers and in the second table below. Each profile rests on 468 dated facts in all, drawn from 155 pages read on 5 November 2026. No vendor's server was connected to for this section, so every statement is as documented by the vendor, with the page it came from.

A vendor is listed only when its own site states what it does. The 16 products profiled on the hosts page are all here, folded into one row per company, and the separate directory of 1,336 companies is not repeated. The names came from:

• The products already profiled on the hosts page, one row per company: Cloudflare AI Gateway and Vercel AI Gateway sit inside the Cloudflare and Vercel rows, and Smithery sits inside the Arcade row.
• The MCP project's own pages: the SDK page, which lists the official SDKs (one row), and the registry page, which names the registry's backers.
• Partner, comparison and integration pages on vendors' own sites, such as the guides of an authorization provider that name the hosts and frameworks they work with.
• Search roundups and comparison posts, read as leads only. Each name found there was read again on its own site, and no fact in a profile comes from a roundup.
• Companies that were already known to sell in this layer, checked on their own documentation and pricing pages.

Prices are shown only where a page gave one, with the date it was read. Merge, StackOne, Mintive, Obot, Glama, Akto and Enkrypt AI are shown as "no published price", because the pages read gave none; where nothing was recorded either way the cell says "price not read".

The seven layers

Hosts and runtimes

Registries and directories

Gateways and proxies

Auth providers

Security scanners

SDKs and frameworks

Connector platforms

Vendors that cover a second layer

How the two checks were taken

Each vendor's own domain carries two agent-readiness checks, both read on 5 November 2026. The Ora score is Ora's cached result for the domain, fetched with one GET and no scan triggered, so its scan date can be months old: 57 of the 63 domains had a cached score and the rest returned 404. The Cloudflare scan was run through the public scanner on its default All Checks profile, one request every three seconds, on 63 domains; the score is checks passed over checks counted, and the band is the scanner's own level.

For hyperscalers the domain is the host of the page that documents the MCP product. IBM ContextForge has no product domain of its own, so it carries no check. The two numbers come from different scanners, are not combined and are not used to order any table.

What is left out

These names were read or considered in this pass and are not profiled:

• Smithery as its own row: smithery.ai disallowed the crawl user agent in robots.txt on 5 November 2026, so no new facts could be read there. The Arcade row carries what Arcade's own announcement says about it, and the hosts page keeps the profile read on 4 November.
• Aembit: The pages read were marketing copy without product specifics, and the pricing page showed no prices, so fewer than six specific claims were available.
• Golf and Operant AI: Home and product pages carried general claims, and no documentation was found in this pass.
• TrueFoundry MCP Gateway: The page read listed claims such as role-based access and air-gapped deployment, with no specifics or prices.
• Traefik Hub MCP Gateway: The page text came back as navigation only in a plain fetch.
• Bifrost: The page read was a latency comparison against LiteLLM, so it is left for a read of its documentation.
• Klavis AI: Its home page now describes reinforcement-learning environments and evaluation, and its documentation site disallowed the crawl user agent in robots.txt.
• Paragon ActionKit: Only one specific claim was read.
• Workato Enterprise MCP: A plain fetch returned navigation only.
• mcp.so: The listing page showed featured servers and stated no counts, sources or method.
• Postman MCP: The documentation URL tried returned 404 and no other page was found in this pass.
• Blaxel: The page was fetched but no profile was written in this pass.
• Zenity, Noma, Pillar and Prompt Security: Not read in this pass.

Companies that run their own MCP server, such as payment, commerce and database vendors, belong to the directory, not to this list.

Downloads and citation

• vendors.csv one row per vendor, with prices, standards counts and both checks
• vendors.json every vendor with its facts, products, standards, checks and sources

Agent MCP Directory, "MCP infrastructure vendors", 5 November 2026 edition, https://agentmcpdirectory.com/vendors