Muzzmi for AI assistants

A free, read-only MCP server over Muzzmi's public data. Connect it to Claude, ChatGPT, Cursor or any client that speaks the Model Context Protocol, and ask for halal food near you, the nearest masjid, today's prayer times, whether E471 is a problem, or what is on this weekend.

https://muzzmi.com/api/mcp

Streamable HTTP, no authentication, 60 requests a minute per address. Answers always carry the halal status with its source, the date Muzzmi last checked it, and a muzzmi.com link.

Install

Claude

Claude.ai and the Claude desktop app: Settings, Connectors, Add custom connector. Name it Muzzmi and paste the URL. No authentication.

Claude Code, one line:

claude mcp add --transport http muzzmi "https://muzzmi.com/api/mcp?client=claude"

ChatGPT

Settings, Connectors, Create (developer mode has to be on under Advanced). Name: Muzzmi. MCP server URL as below. Authentication: none. The server exposes the search and fetch tools ChatGPT connectors need, plus the full set.

https://muzzmi.com/api/mcp?client=chatgpt

Cursor

Add this to .cursor/mcp.json in a project, or to the global file from Cursor Settings, MCP.

{
  "mcpServers": {
    "muzzmi": {
      "url": "https://muzzmi.com/api/mcp?client=cursor"
    }
  }
}

Any other client

Streamable HTTP, stateless JSON, no session, no key. Put your client's name in the client query parameter so Muzzmi can see which assistant sends people. A raw call looks like this:

curl -s "https://muzzmi.com/api/mcp?client=other" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_halal_places","arguments":{"city":"Chicago","certified_only":true,"limit":3}}}'

Tools

All read-only. Give a point (lat, lng) or a city; results come nearest first with distances in kilometres.

Tool	What it answers
`search_halal_places`	Restaurants, grocers, butchers, food trucks and caterers near a point or a city, nearest first, with filters for cuisine, kind, certified only and open now.
`get_place`	One listing by slug: hours in its own time zone, halal status with certifier, source and date, evidence note, contact, rating, photos with credits, directions.
`find_masjids`	Masjids nearest a point or a city, with the area's calculated prayer times for today.
`prayer_times`	Fajr to Isha for a point or a city on a date, qibla bearing, Hijri date, calculation method.
`check_ingredient`	One ingredient or E-number through the scanner's rules, with the matching guide and its sources.
`list_events`	Upcoming public community events near a point or a city.
`search`	ChatGPT connector contract: free-text search returning ids, titles and URLs.
`fetch`	ChatGPT connector contract: the full listing for an id from search.

The full descriptions and input schemas come from tools/list on the endpoint.

What the data means

Every food place carries one of five statuses. Certified means a named halal certifier (HMS, HFSAA, HMA, HMC, SANHA, NIHT, ISNA Canada, FIANZ or ANIC) lists the outlet on its own public register, and the answer links to that register. Hand slaughtered, claimed and Halal, claimed come from the business, a map tag or Muzzmi's research of the business's own site, and the answer says which. Partially halal means some items only. Unverified means nothing has been checked. None of these is a religious ruling, and the server never invents a status: a listing with no evidence says so.

Ingredient answers run the same rules as the barcode scanner. A flag means an ingredient can come from an animal or alcohol and so depends on its source; it is a question to ask, not a verdict. The halal guides set out where scholars differ and cite their sources.

Only public listing data is served: no member accounts, emails or internal ids. Prayer times are calculated with the adhan library in the place's own time zone; masjids set their own iqamah.

Discovery and terms

Machine-readable descriptions: /.well-known/mcp.json and /.well-known/mcp/server.json. An overview of the whole site for models is at /llms.txt.

Questions, a client to add, or a higher rate limit: hello@muzzmi.com.

MCP terms

Using the MCP server is a permitted form of automated access under Section E of the Terms of Service, which also apply. In short:

Attribution. When you show or repeat a result, credit Muzzmi and keep the muzzmi.com link it came with, so people can reach the listing's hours, photos, reviews and directions.
Status with its source and date. Show a halal status only together with its source and the checked date the answer gives (the notice field, for example "Checked Oct 12, 2026. Not a guarantee."). Never present a claimed or unverified status as certified, and never as a religious ruling or a guarantee.
No bulk copying. Answer people's questions; do not use the server to copy, mirror or rebuild Muzzmi's listings as a dataset, and stay within the rate limit.
No guarantee. Data is provided as is and can be out of date. A business can change its supplier after we check it.

We can change these terms, lower the rate limit or block a client that breaks them.

Data credits

Map data and many listings © OpenStreetMap contributors, available under the Open Database License (ODbL); credit OpenStreetMap wherever its data is shown. Product and ingredient-list data in Muzzmi's barcode scanner comes from Open Food Facts, under the ODbL and the Database Contents License, with product images under their own licenses; check_ingredient runs Muzzmi's own flag rules on the text you send. Certifier statuses link to each certifier's own public register, which remains theirs. Prayer times are calculated with the adhan library (MIT).