Compare · api specs data formats

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
4,892companies name Model Context Protocol
5,264companies name XML
0name both
16,002 · 12,841postings in 90 days, Model Context Protocol · XML
02 — Side by side

Who chooses which

Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.

By company size
SegmentModel Context ProtocolshareXMLshareLeans
Self-employed1683%992%even
2-10 employees3908%3787%even
11-50 employees61813%91317%XML
51-200 employees1,02021%1,11221%even
201-500 employees68614%70713%even
501-1000 employees51411%4378%Model Context Protocol
1001-5000 employees78316%82216%even
5001-10000 employees2074%2565%even
10,001+ employees50610%54010%even
By industry
SegmentModel Context ProtocolshareXMLshareLeans
Technology & software2,45350%2,44046%Model Context Protocol
Business & finance services1,04821%1,12921%even
Manufacturing & industry3688%51110%XML
Media & content2104%1884%even
Commerce & trade1443%1833%even
Consumer services & leisure1313%1623%even
Public, community & associations1162%1333%even
Utilities & infrastructure1122%1082%even
Health care812%1062%even
Property & construction701%691%even
Transport, logistics & rental681%1132%even
Hospitality & travel441%––outside top 12
Automotive––611%outside top 12
By country
SegmentModel Context ProtocolshareXMLshareLeans
United States3,05963%2,82754%Model Context Protocol
United Kingdom3477%3196%even
Germany2645%3406%even
Canada1383%1613%even
France1233%1543%even
India731%2885%XML
Brazil621%681%even
Netherlands611%832%even
Sweden591%––outside top 12
Australia531%761%even
Spain501%461%even
Poland391%721%even
Switzerland––451%outside top 12
Postings by team (share of each tool's postings)
SegmentModel Context ProtocolshareXMLshareLeans
Data & AI6,05532%1,0945%Model Context Protocol
Software engineering5,24428%11,22152%XML
IT operations & business systems2,52713%2,98614%even
Product, program & project management7824%4822%even
Sales5593%1881%Model Context Protocol
Engineering (non-software)2661%4872%even
Marketing & communications2201%3141%even
Customer service & success1901%3592%even
Design & UX1301%450%even
General management & consulting920%730%even
Finance & accounting740%1411%even
Business development & strategy720%170%even
Unclassified650%920%even
skilled trades and field service320%290%even
Education & training280%370%even
Quality, safety & environment280%860%even
Human resources230%750%even
construction and civil220%220%even
Legal, compliance & risk190%330%even
arts media and entertainment160%4022%even
research and science150%190%even
logistics warehouse and transport70%400%even
Administration & office50%490%even
facilities cleaning and security40%––outside top 12
public safety and protective services30%50%even
manufacturing and production20%70%even
real estate and property20%––outside top 12
Retail & store operations20%40%even
social care and community20%10%even
hospitality and food service10%40%even
procurement and purchasing––80%outside top 12
healthcare clinical––30%outside top 12
Cite this

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)
How we know

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.
FAQ

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.

Companies and people

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.

  1. 01Sign up, no card
  2. 02Connect Claude, ChatGPT or an API key
  3. 03Ask for your market, 1,000 records free