Shipvane · 4 AE roles
Marco E. · joined Cargolio
Fleetora · first roles in DEJSON Schema VS Model Context Protocol_
As of 30 October 2026, Model Context Protocol is named by 3,710 companies and JSON Schema by 127; JSON Schema skews to companies under 200 people (34% vs 42%), Model Context Protocol to companies over 1,000 (31% vs 35%).
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: JSON Schema's script and mail records show on hundreds of thousands of small sites, Model Context Protocol rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- JSON Schema: 2–200 employees
- 34%
- Model Context Protocol: 2–200 employees
- 42%
- JSON Schema: 1,000+ employees
- 35%
- Model Context Protocol: 1,000+ employees
- 31%
- Postings per company, 90 days
- 1.9 · 3.2
- 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 | JSON Schema | share | Model Context Protocol | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 5 | 4% | 64 | 2% | JSON Schema |
| 2-10 employees | 6 | 5% | 252 | 7% | Model Context Protocol |
| 11-50 employees | 19 | 15% | 490 | 13% | even |
| 51-200 employees | 18 | 14% | 800 | 22% | Model Context Protocol |
| 201-500 employees | 20 | 16% | 548 | 15% | even |
| 501-1000 employees | 15 | 12% | 408 | 11% | even |
| 1001-5000 employees | 15 | 12% | 612 | 16% | Model Context Protocol |
| 5001-10000 employees | 8 | 6% | 160 | 4% | even |
| 10,001+ employees | 21 | 17% | 376 | 10% | JSON Schema |
| Segment | JSON Schema | share | Model Context Protocol | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 68 | 54% | 1,931 | 52% | even |
| Business & finance services | 23 | 18% | 781 | 21% | Model Context Protocol |
| Manufacturing & industry | 12 | 9% | 276 | 7% | JSON Schema |
| Public, community & associations | 5 | 4% | 82 | 2% | even |
| Media & content | 5 | 4% | 145 | 4% | even |
| Health care | 3 | 2% | 67 | 2% | even |
| Utilities & infrastructure | 3 | 2% | 85 | 2% | even |
| Automotive | 2 | 2% | 30 | 1% | even |
| Consumer services & leisure | 2 | 2% | 85 | 2% | even |
| Transport, logistics & rental | 2 | 2% | 50 | 1% | even |
| Commerce & trade | 1 | 1% | 99 | 3% | even |
| Hospitality & travel | 1 | 1% | – | – | outside top 12 |
| Property & construction | – | – | 48 | 1% | outside top 12 |
| Segment | JSON Schema | share | Model Context Protocol | share | Leans |
|---|---|---|---|---|---|
| United States | 90 | 71% | 2,391 | 64% | JSON Schema |
| United Kingdom | 12 | 9% | 285 | 8% | even |
| Australia | 4 | 3% | 41 | 1% | JSON Schema |
| Canada | 4 | 3% | 106 | 3% | even |
| Brazil | 3 | 2% | 32 | 1% | even |
| India | 2 | 2% | 52 | 1% | even |
| Mexico | 2 | 2% | – | – | outside top 12 |
| Singapore | 2 | 2% | – | – | outside top 12 |
| Austria | 1 | 1% | – | – | outside top 12 |
| Germany | 1 | 1% | 212 | 6% | Model Context Protocol |
| Denmark | 1 | 1% | – | – | outside top 12 |
| France | 1 | 1% | 103 | 3% | even |
| Netherlands | – | – | 52 | 1% | outside top 12 |
| Sweden | – | – | 42 | 1% | outside top 12 |
| Spain | – | – | 33 | 1% | outside top 12 |
| Poland | – | – | 32 | 1% | outside top 12 |
| Segment | JSON Schema | share | Model Context Protocol | share | Leans |
|---|---|---|---|---|---|
| Software engineering | 129 | 42% | 4,101 | 28% | JSON Schema |
| Data & AI | 88 | 28% | 4,805 | 33% | Model Context Protocol |
| IT operations & business systems | 20 | 6% | 1,440 | 10% | Model Context Protocol |
| Legal, compliance & risk | 4 | 1% | – | – | outside top 12 |
| Engineering (non-software) | 3 | 1% | 205 | 1% | even |
| Product, program & project management | 3 | 1% | 659 | 5% | Model Context Protocol |
| Design & UX | 2 | 1% | 109 | 1% | even |
| Sales | 2 | 1% | 461 | 3% | Model Context Protocol |
| Administration & office | 1 | 0% | – | – | outside top 12 |
| arts media and entertainment | 1 | 0% | – | – | outside top 12 |
| Marketing & communications | 1 | 0% | 171 | 1% | even |
| real estate and property | 1 | 0% | – | – | outside top 12 |
| Customer service & success | – | – | 146 | 1% | outside top 12 |
| General management & consulting | – | – | 76 | 1% | outside top 12 |
| Finance & accounting | – | – | 63 | 0% | outside top 12 |
| Business development & strategy | – | – | 62 | 0% | outside top 12 |
The companies behind each column
Companies using JSON Schema →
Companies using Model Context Protocol →
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.
Model Context Protocol is named by 3,710 companies in job postings and JSON Schema by 127; 32 name both. (Breaknorm, 30 October 2026, https://breaknorm.co/compare/json-schema-vs-model-context-protocol)
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.
JSON Schema vs Model Context Protocol: questions
Which is more used, JSON Schema or Model Context Protocol?
By companies naming it in their own job postings, Model Context Protocol (3,710) over JSON Schema (127). By website-and-DNS footprint, Model Context Protocol (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses JSON Schema?
34% of JSON Schema companies have 2 to 200 employees, against 42% for Model Context Protocol. 35% of JSON Schema companies have over 1,000 employees, against 31% for Model Context Protocol.
Do companies run both?
32 companies name both in their postings, usually JSON Schema in marketing and Model Context Protocol 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 JSON Schema or Model Context Protocol, and get 1,000 records free.