MCP.Market

UMich Dining MCP server

online · 100% uptime
by esreddy2·io.github.esreddy2/umich-dining-mcp·v2.0.0
No reviews yet

Menus, traits, allergens, nutrition and hours of the ten University of Michigan dining halls.

A89/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A89/100

not scanned yet

Adoption
New

0 stars0 downloads/wk

Reviews

Write one

Nobody has reviewed UMich Dining yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

UMich Dining tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How UMich Dining compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
89/100
higher than 80% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
202 ms
faster than 63% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-21, latest 2026-10-29, typically one every 8 days.

Install UMich Dining in Claude Code, Cursor or VS Code

claude mcp add --transport http umich-dining-mcp https://umich-dining-mcp.duckdns.org/mcp
Add to Cursor

UMich Dining: common questions

Is UMich Dining MCP server safe?
Yes, by our scan: it is graded A (89/100). Read the UMich Dining safety report
How do I install UMich Dining?
It runs remotely at umich-dining-mcp.duckdns.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does UMich Dining need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is UMich Dining maintained?
The last commit was 9 days ago (2026-10-26). The latest release is v2.0.0.
Is UMich Dining up?
100% of our last 16 checks got an answer. We check remote servers about four times a day.
How does UMich Dining compare with other MCP servers?
safety score 89/100 (higher than 80% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 202 ms (faster than 63% of 30,031 servers). Full comparison.