Original research · 2026-09-19
The MCP gap in food & beverage
We searched the whole public registry for the systems a CPG or foodservice IT team actually runs.
Of 33,512 servers in the public MCP Registry on , not one is published by a major syndicated retail-data provider, a major supply-chain planning vendor, a retail-media platform, or a foodservice POS vendor. The horizontal enterprise stack is well covered — 33 servers meet our publication criteria — but the systems specific to this industry are absent.
Method
- Population: every latest-version server record in the public MCP Registry — 33,512 records.
- Collected: 2026-09-19.
- Search: by publisher name substring and by reverse-DNS publisher domain.
- Presence test: a server published under a namespace whose claimed domain we could independently match to the server’s own endpoint, website or source repository.
- Coverage limit: a vendor publishing under an unrelated namespace, or outside the public registry entirely, would not be detected. If you know of one, tell us and we will correct this page.
Vendors checked, and not found
| Category | Vendors searched | Servers found |
|---|---|---|
| Syndicated retail data | Nielsen, NielsenIQ, Circana, SPINS, Numerator | 0 |
| Supply-chain planning | Blue Yonder, Kinaxis, o9 Solutions, Manhattan Associates, Coupa, Anaplan, E2open | 0 |
| Retail media | Amazon Ads, Criteo, The Trade Desk | 0 |
| Foodservice POS | Toast, Olo, NCR Aloha, Punchh, Paytronix | 0 |
A second finding: read-only access is often impossible
Of the 34 servers we profile, 17 publish a machine-readable scope list. 9 of those 17 expose a single scope covering both reading and writing — so an administrator cannot grant read-only access. Approving the connection approves everything it can do.
| Server | Published scopes | Read-only grantable |
|---|---|---|
| Supabase | organizations:read, projects:read, projects:write, database:write, database:read, analytics:read, secrets:read, edge_functions:read, edge_functions:write, environment:read, environment:write, storage:read, storage:write | Yes |
| Atlassian Rovo MCP Server | read:me, read:account, offline_access, email, read:jira-work, write:jira-work, search:confluence, read:confluence-user, read:page:confluence, write:page:confluence, read:comment:confluence, write:comment:confluence, read:space:confluence, read:hierarchical-content:confluence, write:component:compass, read:component:compass, read:scorecard:compass, write:scorecard:compass, read:event:compass, read:metric:compass, read:all:twg, write:all:twg | Yes |
| Sanity | global | No |
| Zapier | openid, profile, email | No |
| Figma MCP Server | mcp:connect | No |
| Microsoft Sentinel Data Exploration | 4500ebfb-89b6-4b14-a480-7f749797bfcd/.default | No |
| PayPal | openid, email, profile | No |
| Vercel | openid | No |
| Airtable | data.records:read, data.records:write, schema.bases:read, schema.bases:write, data.recordComments:read, data.recordComments:write, workspacesAndBases:read | Yes |
| Amplitude | mcp:read, mcp:write | Yes |
| Atlasverified Atlas | mcp:*, conversations:read, conversations:write, documents:read, documents:write, suppliers:read, suppliers:write, verification:read, verification:write, reports:read, reports:write, paperwork:write, signatures:read, signatures:write, shipments:read, shipments:write, inventory:read, inventory:write, opportunities:read, opportunities:write, search:read, tradedata:read, account:read, account:write, intelligence:read, intelligence:write, employees:read, employees:write, ingestion:write, readonly, chat, documents | Yes |
| FoodPhoto | studio:read, studio:write, billing:checkout | Yes |
| GitLab | mcp | No |
| Linear | read, write | Yes |
| Notion | default | No |
| Spoonjoy | account:read, account:write, cookbooks:read, kitchen:read, kitchen:write, public:read, recipes:read, shopping_list:read, shopping_list:write | Yes |
| Tastewise | mcp | No |
What this is not
- Not a security assessment, and not a ranking.
- Not a claim about any vendor’s actual controls — only about what is publicly documented.
- Not a prediction. Coverage may look completely different in six months, which is why the collection date is on every figure.
Download the data (CSV, no email required)
Questions
- Which vendors did you check for?
- 20 named vendors across syndicated data, supply-chain planning, retail media and foodservice POS. The full list is published on this page so the finding can be checked and disproved.
- How did you search?
- By publisher name and by publisher domain against the public MCP Registry, covering 33,512 server records on 2026-09-19. A vendor counts as present only if a server is published under a namespace whose domain we could independently match.
- Does this mean those vendors have no AI integration?
- No. It means they do not publish a server in the public MCP Registry. Many offer REST APIs, private integrations or partner programmes. This is a statement about MCP availability only.
Follow this research
We re-run this analysis as the registry changes. The aggregate data above is free and ungated — leave an address if you want to know when the numbers move.