Shipvane · 4 AE roles
Marco E. · joined Cargolio
Fleetora · first roles in DEModel Context Protocol VS YAML_
As of 30 October 2026, YAML is named by 775 companies and Model Context Protocol by 3,710; Model Context Protocol skews to companies under 200 people (42% vs 35%), YAML to companies over 1,000 (40% vs 31%).
As of 30 October 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
The website-and-DNS footprint is not comparable between a marketing suite and a CRM: Model Context Protocol's script and mail records show on hundreds of thousands of small sites, YAML rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- Model Context Protocol: 2–200 employees
- 42%
- YAML: 2–200 employees
- 35%
- Model Context Protocol: 1,000+ employees
- 31%
- YAML: 1,000+ employees
- 40%
- Postings per company, 90 days
- 3.2 · 2.8
- Website or DNS footprint
- 0 · 0
Who chooses which
Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.
| Segment | Model Context Protocol | share | YAML | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 64 | 2% | 11 | 1% | even |
| 2-10 employees | 252 | 7% | 37 | 5% | Model Context Protocol |
| 11-50 employees | 490 | 13% | 90 | 12% | even |
| 51-200 employees | 800 | 22% | 148 | 19% | Model Context Protocol |
| 201-500 employees | 548 | 15% | 105 | 14% | even |
| 501-1000 employees | 408 | 11% | 75 | 10% | even |
| 1001-5000 employees | 612 | 16% | 147 | 19% | YAML |
| 5001-10000 employees | 160 | 4% | 46 | 6% | even |
| 10,001+ employees | 376 | 10% | 116 | 15% | YAML |
| Segment | Model Context Protocol | share | YAML | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 1,931 | 52% | 383 | 49% | Model Context Protocol |
| Business & finance services | 781 | 21% | 185 | 24% | YAML |
| Manufacturing & industry | 276 | 7% | 87 | 11% | YAML |
| Media & content | 145 | 4% | 13 | 2% | Model Context Protocol |
| Commerce & trade | 99 | 3% | 15 | 2% | even |
| Consumer services & leisure | 85 | 2% | 16 | 2% | even |
| Utilities & infrastructure | 85 | 2% | 18 | 2% | even |
| Public, community & associations | 82 | 2% | 17 | 2% | even |
| Health care | 67 | 2% | 8 | 1% | even |
| Transport, logistics & rental | 50 | 1% | 11 | 1% | even |
| Property & construction | 48 | 1% | 10 | 1% | even |
| Automotive | 30 | 1% | 8 | 1% | even |
| Segment | Model Context Protocol | share | YAML | share | Leans |
|---|---|---|---|---|---|
| United States | 2,391 | 64% | 467 | 60% | Model Context Protocol |
| United Kingdom | 285 | 8% | 70 | 9% | even |
| Germany | 212 | 6% | 49 | 6% | even |
| Canada | 106 | 3% | 25 | 3% | even |
| France | 103 | 3% | 20 | 3% | even |
| India | 52 | 1% | 13 | 2% | even |
| Netherlands | 52 | 1% | 24 | 3% | even |
| Sweden | 42 | 1% | – | – | outside top 12 |
| Australia | 41 | 1% | 7 | 1% | even |
| Spain | 33 | 1% | 9 | 1% | even |
| Brazil | 32 | 1% | – | – | outside top 12 |
| Poland | 32 | 1% | 8 | 1% | even |
| Switzerland | – | – | 7 | 1% | outside top 12 |
| Austria | – | – | 6 | 1% | outside top 12 |
| Segment | Model Context Protocol | share | YAML | share | Leans |
|---|---|---|---|---|---|
| Data & AI | 4,805 | 33% | 214 | 8% | Model Context Protocol |
| Software engineering | 4,101 | 28% | 1,329 | 49% | YAML |
| IT operations & business systems | 1,440 | 10% | 567 | 21% | YAML |
| Product, program & project management | 659 | 5% | 43 | 2% | Model Context Protocol |
| Sales | 461 | 3% | 20 | 1% | Model Context Protocol |
| Engineering (non-software) | 205 | 1% | 74 | 3% | even |
| Marketing & communications | 171 | 1% | 10 | 0% | even |
| Customer service & success | 146 | 1% | 26 | 1% | even |
| Design & UX | 109 | 1% | – | – | outside top 12 |
| General management & consulting | 76 | 1% | 7 | 0% | even |
| Finance & accounting | 63 | 0% | – | – | outside top 12 |
| Business development & strategy | 62 | 0% | – | – | outside top 12 |
| Quality, safety & environment | – | – | 18 | 1% | outside top 12 |
| arts media and entertainment | – | – | 9 | 0% | outside top 12 |
| Administration & office | – | – | 4 | 0% | outside top 12 |
The companies behind each column
Companies using Model Context Protocol →
Companies using YAML →
api specs data formats ranked →
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
YAML is named by 775 companies in job postings and Model Context Protocol by 3,710; 0 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/model-context-protocol-vs-yaml)
Read from the source, not self-reported
Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →
- Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
- Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
- SegmentsCountry, size and industry from the company profile built from its website.
- Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
Model Context Protocol vs YAML: questions
Which is more used, Model Context Protocol or YAML?
By companies naming it in their own job postings, Model Context Protocol (3,710) over YAML (775). By website-and-DNS footprint, YAML (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses Model Context Protocol?
42% of Model Context Protocol companies have 2 to 200 employees, against 35% for YAML. 31% of Model Context Protocol companies have over 1,000 employees, against 40% for YAML.
Do companies run both?
0 companies name both in their postings, usually Model Context Protocol in marketing and YAML in sales, or during a migration.
Where do these numbers come from?
From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.
Get either list your way
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
Every company on either tool,
with the person who owns it
Filter on Model Context Protocol or YAML, and get 1,000 records free.