Enterprise DNA
M MCP Servers Developer low

FoodXDevelopment/foodblock-mcp

by Various

A content-addressable protocol for universal food data

F

MCP

FoodXDevelopment/foodblock-mcp

Added 1 June 2026

Overview

FoodXDevelopment/foodblock-mcp is a JavaScript library that implements a content-addressable protocol for universal food data. It allows developers to reference and retrieve food-related information using unique content hashes rather than traditional identifiers.

Best for

Best for
Developers building decentralized or interoperable food data systems

Use cases

  • Building decentralized food databases with content-addressable lookups
  • Creating interoperable food data systems across different platforms
  • Developing applications that require verifiable and immutable food data references

Notes

FoodXDevelopment/foodblock-mcp is a JavaScript library that implements a content-addressable protocol for universal food data. It allows developers to reference and retrieve food-related information using unique content hashes rather than traditional identifiers.

0 stars on GitHub. Last updated 2026-03-16. Licensed MIT.

Use cases

  • Building decentralized food databases with content-addressable lookups
  • Creating interoperable food data systems across different platforms
  • Developing applications that require verifiable and immutable food data references

Pros

  • Content addressing ensures data integrity and deduplication
  • Protocol-based approach enables cross-platform compatibility
  • Lightweight JavaScript implementation for easy integration

Cons

  • Zero stars and no community adoption suggests early or experimental stage
  • Limited documentation and examples may hinder onboarding
  • Niche use case may not suit general food data applications

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • Content addressing ensures data integrity and deduplication
  • Protocol-based approach enables cross-platform compatibility
  • Lightweight JavaScript implementation for easy integration

Cons

  • Zero stars and no community adoption suggests early or experimental stage
  • Limited documentation and examples may hinder onboarding
  • Niche use case may not suit general food data applications