_ registry / mcp streamable-http · checked 57m ago

deallabs-mcp

https://deallabs.net

Registry code: ca39296aafea5fc4

api record

Read-only DealLabs data (data-standard v1). Every answer carries its source, the checked day and the licence; null means not known.

Find a place or station by name, kind or area: search_verified_places (it does not return train times).

endpoint
https://deallabs.net/mcp
protocol
streamable-http ·2025-06-18
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 deallabs-mcp live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is deallabs-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does deallabs-mcp have?
4 tools: search_verified_places, find_active_popups, get_station_exit, plan_local_route.
Is deallabs-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
301ms

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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 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.

  • search_verified_places unknown never probed

    Find places and stations by name, kind, category, area, nearness or opening time. Answers only from data-standard v1 records; null values are reported as not_known. It does not return train times: for a station's exits or its last trains, call get_station_exit with the station name.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "area": {
          "type": "string"
        },
        "city": {
          "enum": [
            "seoul",
            "hongkong",
            "osaka",
            "singapore",
            "busan",
            "taipei",
            "tokyo"
          ],
          "type": "string",
          "description": "City key, e.g. \"seoul\"."
        },
        "kind": {
          "enum": [
            "place",
            "station",
            "exit",
            "venue",
            "popup",
            "event"
          ],
          "type": "string",
          "description": "exit: give the station name in query; returns that station's exits."
        },
        "near": {
          "type": "object",
          "properties": {
            "lat": {
              "type": "number"
            },
            "lng": {
              "type": "number"
            },
            "station": {
              "type": "string"
            }
          },
          "description": "Sort by straight-line distance from {lat, lng} or from a station (name or place_id)."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Matched against name and name_local."
        },
        "open_at": {
          "type": "object",
          "required": [
            "date",
            "time"
          ],
          "properties": {
            "date": {
              "type": "string",
              "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
            },
            "time": {
              "type": "string",
              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
            }
          }
        },
        "category": {
          "type": "string"
        },
        "walk_max": {
          "type": "integer",
          "maximum": 120,
          "minimum": 0,
          "description": "Minutes on foot from the station (only records with a walk)."
        },
        "min_confidence": {
          "enum": [
            "high",
            "medium"
          ],
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 94 lines
  • find_active_popups unknown 57m ago

    Pop-ups running on a day. Returns an empty list with reason_code no_v1_records until the city publishes pop-up records in data-standard v1.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city"
      ],
      "properties": {
        "at": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        },
        "area": {
          "type": "string"
        },
        "city": {
          "enum": [
            "seoul",
            "hongkong",
            "osaka",
            "singapore",
            "busan",
            "taipei",
            "tokyo"
          ],
          "type": "string",
          "description": "City key, e.g. \"seoul\"."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Default: today in the city's own time."
        },
        "station": {
          "type": "string"
        },
        "category": {
          "type": "string"
        },
        "walk_max": {
          "type": "integer",
          "maximum": 120,
          "minimum": 0
        },
        "open_until": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • get_station_exit unknown 57m ago

    The station record, its exits, its last-train times by line and direction (weekday, Saturday and Sunday; Seoul and Busan publish them; other cities answer last_trains as not_published), and (with "to") the walk from the station to a destination record. Takes the station name in common spellings (for example Myeong-dong, Hongik Univ., 명동역) or a place_id. Exit positions are OpenStreetMap data (ODbL 1.0).

    mcp-tool

    {
      "type": "object",
      "required": [
        "city",
        "station"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Optional place_id of the destination."
        },
        "city": {
          "enum": [
            "seoul",
            "hongkong",
            "osaka",
            "singapore",
            "busan",
            "taipei",
            "tokyo"
          ],
          "type": "string",
          "description": "City key, e.g. \"seoul\"."
        },
        "station": {
          "type": "string",
          "description": "Station name or place_id."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • plan_local_route unknown 57m ago

    Can these stops fit in this time, in this order? Judges each stop with its posted hours on the date. The tool does not guess how long a visit takes: visit_min is required.

    mcp-tool

    {
      "type": "object",
      "required": [
        "city",
        "stops",
        "date",
        "start_time",
        "visit_min"
      ],
      "properties": {
        "city": {
          "enum": [
            "seoul",
            "hongkong",
            "osaka",
            "singapore",
            "busan",
            "taipei",
            "tokyo"
          ],
          "type": "string",
          "description": "City key, e.g. \"seoul\"."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "from": {
          "type": "object",
          "properties": {
            "lat": {
              "type": "number"
            },
            "lng": {
              "type": "number"
            },
            "station": {
              "type": "string"
            }
          }
        },
        "stops": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "place_id values, in order."
        },
        "end_time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        },
        "visit_min": {
          "type": "integer",
          "maximum": 600,
          "minimum": 1,
          "description": "Minutes at each stop."
        },
        "start_time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$"
        }
      },
      "additionalProperties": false
    }
    arguments 67 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 ca39296aafea5fc4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ca39296aafea5fc4/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/ca39296aafea5fc4/badge.svg)](https://brick.blue/agent/ca39296aafea5fc4?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.