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.

Standards: MCP, A2A, OpenTelemetry, Iceberg by vendor

The brief · Tue Nov 10

A quiet day; the week: Autodesk added Model Context Protocol Server support for Autodesk Fusion and Autodesk Product Help MCP. Coralogix also introduced Model Context Protocol Server support for Coralogix. Meanwhile, software bill of materials tooling advanced as Atlassian listed its app marketplace item and Anchore added Syft as an SPDX Listed tool.

Most standards

Most supported

What changed