Method
Where each entry comes from, how it is read, how far the research reaches, and what it cannot tell you
Coverage
The depth target is every company in the fru.dev registry that makes cloud, data, AI, developer, security or internet software or chips, plus every vendor a source names: 407 so far, and it grows with the registry. 148 of them wait as candidates until a source names them.
- Named by a source (tracked)64%
259 of 407. A list, the MCP Registry or the vendor's docs names at least one standard for it.
- Docs researched for every standard in scope79%
320 of 407. A researcher read the vendor's documentation for each standard that fits its products.
- Checked in the MCP Registry64%
259 of 407. Every vendor in scope is also matched against every adopter list on each run.
Sources
553 sources so far: the lists below, the MCP Registry and 540 vendor documentation pages for 237 vendors. Each run also probes for new lists on the standards' own sites and follows list-like links on the ones it reads; a list it finds is read from then on and its entries stay Unverified until checked by hand.
| Source | What it gives | Vendors | Last read |
|---|---|---|---|
| Apache Iceberg vendors pageIceberg · Adopter list One entry per vendor. The role comes from the entry's own words: REST catalog when it serves the catalog API, read and write, read, or listed when it does not say. | One entry per vendor. The role comes from the entry's own words: REST catalog when it serves the catalog API, read and write, read, or listed when it does not say. | 23 | Sep 25, 2026 |
| OpenTelemetry vendors registryOTel · Adopter list Vendors this list names for OpenTelemetry. | Vendors this list names for OpenTelemetry. | 22 | Sep 25, 2026 |
| Delta Lake integrations pageDelta · Adopter list Engines and services that read or write Delta tables. Entries marked Beta show as Preview. | Engines and services that read or write Delta tables. Entries marked Beta show as Preview. | 11 | Sep 25, 2026 |
| A2A partners pageA2A · Adopter list Companies in the Agent2Agent partner program. | Companies in the Agent2Agent partner program. | 41 | Sep 25, 2026 |
| Apache Hudi ecosystem pageHudi · Adopter list Engines with Read or Read + Write support for Hudi tables, each linking to the vendor's own docs. | Engines with Read or Read + Write support for Hudi tables, each linking to the vendor's own docs. | 7 | Sep 25, 2026 |
| Powered by Apache Arrow pageArrow · Adopter list Vendors this list names for Apache Arrow. | Vendors this list names for Apache Arrow. | 4 | Sep 25, 2026 |
| ONNX supported tools pageONNX · Adopter list Vendors this list names for ONNX. | Vendors this list names for ONNX. | 9 | Sep 25, 2026 |
| C2PA membership pageC2PA · Adopter list Vendors this list names for C2PA Content Credentials. | Vendors this list names for C2PA Content Credentials. | 22 | Sep 25, 2026 |
| SPIRE adopters listSPIFFE · Adopter list Vendors this list names for SPIFFE. | Vendors this list names for SPIFFE. | 3 | Sep 25, 2026 |
| SPDX tools pageSPDX · Adopter list Vendors this list names for SPDX. | Vendors this list names for SPDX. | 0 | Sep 25, 2026 |
| CycloneDX Tool CenterCycloneDX · Adopter list Vendors this list names for CycloneDX. | Vendors this list names for CycloneDX. | 0 | Sep 25, 2026 |
| Official MCP RegistryMCP · Registry API Servers published in a vendor's own namespace (its reversed domain or GitHub org), which only the vendor can publish to. | Servers published in a vendor's own namespace (its reversed domain or GitHub org), which only the vendor can publish to. | 40 | Sep 25, 2026 |
| OpenID Foundation certified implementationsOIDC · Adopter list Vendors this list names for OAuth 2.0 and OpenID Connect. | Vendors this list names for OAuth 2.0 and OpenID Connect. | 8 | Sep 25, 2026 |
Recent runs
- Sep 25, 2026150 found · +9 added · 0 changed · +1 vendors · +0 sources (0 probed)
- Sep 25, 2026142 found · +0 added · 0 changed · +0 vendors · +0 sources (30 probed)
- Sep 25, 2026224 found · +142 added · 0 changed · +16 vendors · +0 sources (24 probed)
- Sep 24, 20260 found · +0 added · 0 changed · +0 vendors · +0 sources (0 probed)
- Sep 24, 20260 found · +0 added · 0 changed · +0 vendors · +0 sources (0 probed)
- Sep 24, 20260 found · +0 added · 0 changed · +0 vendors · +0 sources (0 probed)
What "supported" means
Supported means the specification project's own list names the vendor (Apache Iceberg, OpenTelemetry, Delta Lake, A2A, Hudi, Arrow, ONNX, C2PA, SPIRE, SPDX, CycloneDX and the lists found since), the official MCP Registry holds a server in the vendor's own namespace, or the vendor's own documentation names the standard for one of its products. The role is shown where the source states one: MCP Server or Client, Iceberg Read, Read and write or REST catalog, Native OTLP. No evidence means not shown; a blank cell is not a "no".
Preview is support the source calls beta or preview. Dropped is a vendor that left an adopter page, or a documentation page that stopped answering or stopped naming the standard two weeks running.
Iceberg roles are read from each vendor's own entry, sentence by sentence, and never guessed upward: an entry that does not say what the product does with Iceberg shows as Listed. Versions are rarely stated on adopter pages; where a source names a product or version, it is kept in the scope line.
The weekly run, Thursday 11:30 UTC, first takes new companies from the registry, probes for new lists, then re-reads every list, reads the next pages of the official MCP Registry (then only servers that changed) and re-reads a rotating set of vendor documentation pages. A company a source names is tracked from then on. No model is involved: every reading is plain text matching against the page, and the sentence that matched is kept with the entry. Research passes add documentation pages between runs; each is fetched and must name the standard before it counts.
Scope matters. Support usually covers named products, editions or regions, not everything a company sells. From the specification projects' adopter pages and vendors' own documentation on the date shown. Confirm the version and scope with the vendor.
Questions
What is Standards (standards.fru.dev)?
It answers which cloud, data, AI and developer-tool vendors support which open protocols and formats: the Model Context Protocol (server or client), Agent2Agent, the OpenAI-compatible API, OpenTelemetry and native OTLP, OpenLineage, Apache Iceberg, Delta Lake and Hudi, Parquet, Apache Arrow, ONNX, SQL:2023, SPIFFE, OpenID Connect, FIDO2 passkeys, C2PA Content Credentials, SPDX and CycloneDX. Each entry links to its evidence and shows the date it was first seen. New standards, vendors and sources are added as they appear.
Where does the data come from?
From the specification projects' own lists (Apache Iceberg vendors, OpenTelemetry vendors, Delta Lake integrations, A2A partners, the Hudi ecosystem, Powered by Arrow, ONNX tools, C2PA members, SPIRE adopters, SPDX tools and the CycloneDX Tool Center, plus lists the weekly run finds), from the official MCP Registry, and from vendors' own documentation for everything else, with the sentence that names the standard kept. Companies come from the fru.dev registry at companies.fru.dev.
How often is it updated?
A run every Thursday at 11:30 UTC takes new companies from the registry, probes for new lists, re-reads every list, reads the next pages of the official MCP Registry and re-reads a rotating set of vendor documentation pages. What was added or dropped goes into the change log with its date.
Which vendors have an official MCP server?
Pick "Who serves MCP" on the home page: GitHub, Stripe, Cloudflare, Atlassian, Supabase, Snowflake, Databricks, MongoDB, Vercel, Sentry, Elastic, Google Cloud, Microsoft, AWS, Grafana Labs, ClickHouse and Neo4j each document an official MCP server, linked from the cell.
Who supports Apache Iceberg?
Pick "Who speaks Iceberg". Vendors on the Apache Iceberg vendors page are listed with the strongest role their own entry states: REST catalog (Google Cloud BigLake, Microsoft OneLake, MinIO, Snowflake Open Catalog), read and write, read, or listed when the entry does not say.
Which providers offer an OpenAI-compatible API?
Pick "OpenAI-compatible API": Anthropic, Groq, Together AI, Fireworks AI, DeepSeek, xAI, Cohere, OpenRouter, Ollama, Hugging Face, Cloudflare Workers AI and Databricks document endpoints that accept OpenAI SDK requests.
What does Native OTLP mean?
The vendor accepts OpenTelemetry data over the OTLP protocol directly, with no translation layer or proprietary agent in between. The OpenTelemetry project records it per vendor on its vendors page; Standards shows it as the stronger of the two OpenTelemetry roles.
Is a listing the same as full support?
No. An adopter page listing says the vendor works with the standard; the version, the products covered and whether it is generally available vary. The scope column keeps what the source says, and Preview marks entries the source calls beta or preview.