Model Context Protocol VS XML_
As of 4 November 2026, XML is named by 5,264 companies and Model Context Protocol by 4,892; Model Context Protocol skews to companies under 200 people (41% vs 46%), XML to companies over 1,000 (31% vs 31%).
As of 4 November 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, XML 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
- 41%
- XML: 2–200 employees
- 46%
- Model Context Protocol: 1,000+ employees
- 31%
- XML: 1,000+ employees
- 31%
- Postings per company, 90 days
- 3.3 · 2.4
- 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 | XML | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 168 | 3% | 99 | 2% | even |
| 2-10 employees | 390 | 8% | 378 | 7% | even |
| 11-50 employees | 618 | 13% | 913 | 17% | XML |
| 51-200 employees | 1,020 | 21% | 1,112 | 21% | even |
| 201-500 employees | 686 | 14% | 707 | 13% | even |
| 501-1000 employees | 514 | 11% | 437 | 8% | Model Context Protocol |
| 1001-5000 employees | 783 | 16% | 822 | 16% | even |
| 5001-10000 employees | 207 | 4% | 256 | 5% | even |
| 10,001+ employees | 506 | 10% | 540 | 10% | even |
| Segment | Model Context Protocol | share | XML | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 2,453 | 50% | 2,440 | 46% | Model Context Protocol |
| Business & finance services | 1,048 | 21% | 1,129 | 21% | even |
| Manufacturing & industry | 368 | 8% | 511 | 10% | XML |
| Media & content | 210 | 4% | 188 | 4% | even |
| Commerce & trade | 144 | 3% | 183 | 3% | even |
| Consumer services & leisure | 131 | 3% | 162 | 3% | even |
| Public, community & associations | 116 | 2% | 133 | 3% | even |
| Utilities & infrastructure | 112 | 2% | 108 | 2% | even |
| Health care | 81 | 2% | 106 | 2% | even |
| Property & construction | 70 | 1% | 69 | 1% | even |
| Transport, logistics & rental | 68 | 1% | 113 | 2% | even |
| Hospitality & travel | 44 | 1% | – | – | outside top 12 |
| Automotive | – | – | 61 | 1% | outside top 12 |
| Segment | Model Context Protocol | share | XML | share | Leans |
|---|---|---|---|---|---|
| United States | 3,059 | 63% | 2,827 | 54% | Model Context Protocol |
| United Kingdom | 347 | 7% | 319 | 6% | even |
| Germany | 264 | 5% | 340 | 6% | even |
| Canada | 138 | 3% | 161 | 3% | even |
| France | 123 | 3% | 154 | 3% | even |
| India | 73 | 1% | 288 | 5% | XML |
| Brazil | 62 | 1% | 68 | 1% | even |
| Netherlands | 61 | 1% | 83 | 2% | even |
| Sweden | 59 | 1% | – | – | outside top 12 |
| Australia | 53 | 1% | 76 | 1% | even |
| Spain | 50 | 1% | 46 | 1% | even |
| Poland | 39 | 1% | 72 | 1% | even |
| Switzerland | – | – | 45 | 1% | outside top 12 |
| Segment | Model Context Protocol | share | XML | share | Leans |
|---|---|---|---|---|---|
| Data & AI | 6,055 | 32% | 1,094 | 5% | Model Context Protocol |
| Software engineering | 5,244 | 28% | 11,221 | 52% | XML |
| IT operations & business systems | 2,527 | 13% | 2,986 | 14% | even |
| Product, program & project management | 782 | 4% | 482 | 2% | even |
| Sales | 559 | 3% | 188 | 1% | Model Context Protocol |
| Engineering (non-software) | 266 | 1% | 487 | 2% | even |
| Marketing & communications | 220 | 1% | 314 | 1% | even |
| Customer service & success | 190 | 1% | 359 | 2% | even |
| Design & UX | 130 | 1% | 45 | 0% | even |
| General management & consulting | 92 | 0% | 73 | 0% | even |
| Finance & accounting | 74 | 0% | 141 | 1% | even |
| Business development & strategy | 72 | 0% | 17 | 0% | even |
| Unclassified | 65 | 0% | 92 | 0% | even |
| skilled trades and field service | 32 | 0% | 29 | 0% | even |
| Education & training | 28 | 0% | 37 | 0% | even |
| Quality, safety & environment | 28 | 0% | 86 | 0% | even |
| Human resources | 23 | 0% | 75 | 0% | even |
| construction and civil | 22 | 0% | 22 | 0% | even |
| Legal, compliance & risk | 19 | 0% | 33 | 0% | even |
| arts media and entertainment | 16 | 0% | 402 | 2% | even |
| research and science | 15 | 0% | 19 | 0% | even |
| logistics warehouse and transport | 7 | 0% | 40 | 0% | even |
| Administration & office | 5 | 0% | 49 | 0% | even |
| facilities cleaning and security | 4 | 0% | – | – | outside top 12 |
| public safety and protective services | 3 | 0% | 5 | 0% | even |
| manufacturing and production | 2 | 0% | 7 | 0% | even |
| real estate and property | 2 | 0% | – | – | outside top 12 |
| Retail & store operations | 2 | 0% | 4 | 0% | even |
| social care and community | 2 | 0% | 1 | 0% | even |
| hospitality and food service | 1 | 0% | 4 | 0% | even |
| procurement and purchasing | – | – | 8 | 0% | outside top 12 |
| healthcare clinical | – | – | 3 | 0% | outside top 12 |
The companies behind each column
Companies using Model Context Protocol →
Companies using XML →
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.
XML is named by 5,264 companies in job postings and Model Context Protocol by 4,892; 0 name both. (Breaknorm, 4 November 2026, https://breaknorm.co/compare/model-context-protocol-vs-xml)
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 XML: questions
Which is more used, Model Context Protocol or XML?
By companies naming it in their own job postings, XML (5,264) over Model Context Protocol (4,892). By website-and-DNS footprint, XML (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses Model Context Protocol?
41% of Model Context Protocol companies have 2 to 200 employees, against 46% for XML. 31% of Model Context Protocol companies have over 1,000 employees, against 31% for XML.
Do companies run both?
0 companies name both in their postings, usually Model Context Protocol in marketing and XML 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 XML, and get 1,000 records free.