_ registry / mcp streamable-http · checked 1h ago

Safe-Biter-MCP

https://www.safebiter.com

Registry code: a71445841c368ba7

api record

Restaurant inspection data for Chicago, NYC, Minneapolis, and Milwaukee.

from a public catalogue that lists it, not from the operator

endpoint
https://www.safebiter.com/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Safe-Biter-MCP live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Safe-Biter-MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does Safe-Biter-MCP have?
4 tools: search_restaurants, find_nearby_restaurants, get_milwaukee_inspections, get_city_inspections.
Is Safe-Biter-MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
342ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_city_inspections open 1h ago

    Get restaurant food inspection data for any major US city with full pagination support. Supports Chicago (18k+ records), NYC (20k+ records), Minneapolis (3k+ records), and Milwaukee. Retrieve ALL records by paginating: repeat the call passing the previous response's next_offset until has_more is false. Response includes pagination metadata (total_count, offset, limit, has_more, next_offset).

    mcp-tool

    {
  "type": "object",
  "required": [
    "city"
  ],
  "properties": {
    "city": {
      "enum": [
        "chicago",
        "nyc",
        "minneapolis",
        "milwaukee",
        "austin",
        "denver"
      ],
      "type": "string",
      "default": "chicago",
      "description": "Target city. Chicago has 18k+ records, NYC has 20k+ records, Minneapolis has 3k+ records."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 500,
      "minimum": 1,
      "description": "Number of records per request (1-500). Use 500 to get maximum data per call for large datasets."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Number of records to skip, for pagination. Pass the previous response's next_offset to get the next page. Default 0."
    }
  }
}
    arguments 34 lines
  • search_restaurants unknown never probed

    Fuzzy-search restaurants by name across the full inspections database (40k+ records). Tolerates misspellings and partial names. Returns one entry per restaurant with its last 3 inspections (newest first) and a similarity score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "city": {
      "enum": [
        "all",
        "chicago",
        "nyc",
        "minneapolis",
        "milwaukee",
        "austin",
        "denver"
      ],
      "type": "string",
      "default": "all",
      "description": "Optional city scope."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Max number of matches to return (1-50)."
    },
    "query": {
      "type": "string",
      "description": "Restaurant name or partial name (e.g., 'giordanos', 'shake shak')."
    },
    "history_n": {
      "type": "integer",
      "default": 3,
      "maximum": 20,
      "minimum": 1,
      "description": "How many recent inspections to include per restaurant. Default 3."
    },
    "threshold": {
      "type": "number",
      "default": 0.6,
      "maximum": 1,
      "minimum": 0,
      "description": "Fuzzy match threshold between 0 and 1 (higher = stricter)."
    }
  }
}
    arguments 47 lines
  • find_nearby_restaurants unknown 1h ago

    Find restaurants within a given radius of a location and return each restaurant's last 3 inspections (newest first). Accepts either explicit latitude/longitude or an address string (geocoded via Google Maps). Default radius is a quarter mile (0.25).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "city": {
      "enum": [
        "all",
        "chicago",
        "nyc",
        "minneapolis",
        "milwaukee",
        "austin",
        "denver"
      ],
      "type": "string",
      "default": "all",
      "description": "Optional city filter."
    },
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 100,
      "minimum": 1,
      "description": "Max restaurants to return (1-100)."
    },
    "address": {
      "type": "string",
      "description": "Optional street address; resolved to lat/lng via Google Maps Geocoding API. Used only if latitude/longitude are not supplied."
    },
    "latitude": {
      "type": "number",
      "description": "Center latitude in decimal degrees. Required if no address is provided."
    },
    "history_n": {
      "type": "integer",
      "default": 3,
      "maximum": 20,
      "minimum": 1,
      "description": "How many recent inspections to include per restaurant. Default 3."
    },
    "longitude": {
      "type": "number",
      "description": "Center longitude in decimal degrees. Required if no address is provided."
    },
    "radius_miles": {
      "type": "number",
      "default": 0.25,
      "maximum": 25,
      "minimum": 0.01,
      "description": "Search radius in miles. Defaults to 0.25 (a quarter mile)."
    }
  }
}
    arguments 52 lines
  • get_milwaukee_inspections unknown 1h ago

    Get Milwaukee restaurant food inspection data with full pagination support. Response includes pagination metadata (total_count, offset, limit, has_more, next_offset) to guide further requests. To page through all records, repeat the call passing next_offset until has_more is false.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 500,
      "minimum": 1,
      "description": "Number of records per request (1-500). Use 500 to get maximum data per call."
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "minimum": 0,
      "description": "Number of records to skip, for pagination. Pass the previous response's next_offset to get the next page. Default 0."
    }
  }
}
    arguments 18 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a71445841c368ba7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a71445841c368ba7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a71445841c368ba7/badge.svg)](https://brick.blue/agent/a71445841c368ba7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.