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

rollin-mcp

https://joinrollin.com

Registry code: 91981386914abf7f

api record

ROLLIN provides wheelchair accessibility data for restaurants, cafes, and bars across the US. Use search_locations with a latitude/longitude to find accessible venues nearby, get_location_details for a full feature and score breakdown of a specific venue, list_regions to see where data coverage is available, submit_feedback to report corrections, and check_health to verify API status. Tool calls require a ROLLIN API key sent as an Authorization: Bearer header or X-Api-Key header. Free keys are available at https://joinrollin.com/portal.html.

endpoint
https://joinrollin.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
1,069ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 5 tools
5 auth-required 5 of 5 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_location_details auth-required never probed

    Get full accessibility details and score breakdown for a specific location. Returns features, score components, and verification status.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Location ID (from search results)"
    }
  }
}
    arguments 12 lines
  • check_health auth-required 14h ago

    Check if the ROLLIN API is operational.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • search_locations auth-required never probed

    Search for wheelchair-accessible restaurants, cafes, and bars near a location. Returns scored results with accessibility features. Requires latitude and longitude.

    mcp-tool

    {
  "type": "object",
  "required": [
    "lat",
    "lng"
  ],
  "properties": {
    "q": {
      "type": "string",
      "description": "Search by name, cuisine, or category (e.g. 'sushi', 'Italian')"
    },
    "lat": {
      "type": "number",
      "description": "Latitude of the search center"
    },
    "lng": {
      "type": "number",
      "description": "Longitude of the search center"
    },
    "limit": {
      "type": "number",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Number of results (default 10, max 50)"
    },
    "radius": {
      "type": "number",
      "default": 5,
      "maximum": 25,
      "minimum": 0.1,
      "description": "Search radius in miles (default 5, max 25)"
    },
    "features": {
      "type": "string",
      "description": "Comma-separated feature filter: wheelchair_entry, accessible_restroom, level_entry, parking, elevator, wide_aisles"
    },
    "lighting": {
      "enum": [
        "bright",
        "moderate",
        "dim"
      ],
      "type": "string",
      "description": "Filter by ambient lighting level: bright, moderate, or dim"
    },
    "min_score": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Minimum accessibility score (0-100)"
    }
  }
}
    arguments 54 lines
  • list_regions auth-required 14h ago

    List all regions where accessibility data is available. Returns states, regions, and location counts for each area.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • submit_feedback auth-required never probed

    Submit a correction or feedback about a location's accessibility. Use this when a user reports that accessibility information is inaccurate.

    mcp-tool

    {
  "type": "object",
  "required": [
    "location_id",
    "feedback_type"
  ],
  "properties": {
    "comment": {
      "type": "string",
      "maxLength": 1000,
      "description": "Additional context (max 1000 characters)"
    },
    "features": {
      "type": "object",
      "description": "Feature corrections, e.g. { wheelchair_entry: true, parking: false }",
      "additionalProperties": {
        "type": [
          "boolean",
          "null"
        ]
      }
    },
    "location_id": {
      "type": "string",
      "description": "Location ID to submit feedback for"
    },
    "feedback_type": {
      "enum": [
        "accurate",
        "inaccurate",
        "correction"
      ],
      "type": "string",
      "description": "Type: 'accurate' to confirm, 'inaccurate' to flag, 'correction' to update features"
    }
  }
}
    arguments 37 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.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/91981386914abf7f/badge.svg)](https://brick.blue/agent/91981386914abf7f)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
90%

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.