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

ai.withby/withby

https://withby.ai

Registry code: 7016b22521bb8821

api record

Use WithBy when someone asks whether a Washington mountain pass or floating bridge is open right now, or asks for a story about a place along Washington's highways.

Passes: WithBy checks WSDOT every few minutes and gives its own verdict for each direction of Snoqualmie, Stevens, White and Blewett passes (open, chains or closed, with the time it checked), and WSDOT's own words for 12 other passes. `pass_status` answers for one pass or for the I-90 or SR 520 floating bridge, `passes_now` for all the passes.

endpoint
https://withby.ai/mcp
protocol
http-sse ·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 ai.withby/withby live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ai.withby/withby free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does ai.withby/withby have?
7 tools: stories_near, pass_status, story, stretch_stories, save_for_drive, passes_now, my_next_drive.
Is ai.withby/withby 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
523ms

last good check

priced tools
0

of 7 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 7 tools
1 open1 auth-required 5 never probed 2 of 7 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.

  • passes_now open 1h ago

    Use this when someone asks about mountain passes in general, which passes are open, or wants the whole list: Washington's mountain passes in depth, and the passes on the roads out of it. Gives WithBy's verdict for Snoqualmie, Stevens, White and Blewett passes in one line each, then 12 other passes in WSDOT's words, seasonal closures marked, then the passes on the way out, each in its agency's words, with the time WithBy checked. Not for navigation or bookings.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • my_next_drive auth-required 1h ago

    Use this when someone asks which stories they saved for their next drive, or which one comes first. Lists their WithBy next-drive list in road order with each story's length. Needs their WithBy account. Not for navigation or bookings.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • stories_near unknown never probed

    Use this when someone asks what stories Sal has near a town, city, landmark, or highway in Washington (e.g. "North Bend", "Snoqualmie Falls", "I-90"). Gives up to 3 nearby stories or nearest covered towns. Not for navigation, bookings, or places outside Washington.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "place"
  ],
  "properties": {
    "place": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The town, city, landmark, or highway in Washington by name (e.g. \"North Bend\", \"Snoqualmie Falls\", \"I-90\")"
    }
  }
}
    arguments 15 lines
  • pass_status unknown 1h ago

    Use this when someone asks whether a mountain pass or the I-90 or SR 520 floating bridge is open, what the restrictions or chain rules are, or how long the crossing takes. Answers for Snoqualmie, Stevens, White and Blewett passes with WithBy's verdict for each direction and the crossing time against the usual, for the two bridges with their crossing times and alerts, and for 12 other passes with WSDOT's words. Covers Washington's mountain passes in depth, and the passes on the roads out of it, in their agency's words. Every answer carries the time WithBy checked and the agency's own report time. Not for navigation or bookings.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "pass"
  ],
  "properties": {
    "pass": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The pass or bridge by name, e.g. \"Snoqualmie Pass\", \"Stevens\" or \"SR 520 bridge\""
    }
  }
}
    arguments 15 lines
  • story unknown never probed

    Use this when someone asks for a story about a place, landmark, or town along Washington's highways, or asks what Sal knows about a specific location or story by id. Gives Sal's story, place and stretch, its length, and Wikipedia / source credit. Not for navigation, bookings, or places outside Washington.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "story"
  ],
  "properties": {
    "story": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The story by id (e.g. \"12\"), title (e.g. \"Snoqualmie Falls\"), or place name"
    }
  }
}
    arguments 15 lines
  • stretch_stories unknown never probed

    Use this when someone asks what stories Sal has along a highway or stretch of road in Washington (e.g. "SR 520 east", "I-90 west from Seattle", or stretch id "sr520-03"). Gives the stories on that stretch in driving order with their durations and total time. Not for navigation, bookings, or roads outside Washington.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "stretch"
  ],
  "properties": {
    "dir": {
      "enum": [
        "north",
        "south",
        "east",
        "west"
      ],
      "type": "string",
      "description": "Optional direction (north, south, east, west) if not in the stretch name"
    },
    "stretch": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "The stretch by road and direction (e.g. \"SR 520 east\", \"I-90 west\") or stretch id (e.g. \"sr520-03\")"
    }
  }
}
    arguments 25 lines
  • save_for_drive unknown never probed

    Use this when someone wants particular stories saved for their next drive: it adds 1 to 50 stories, by the ids the story, stretch and nearby-stories answers give, to their WithBy next-drive list, the same list as Save for my drive on withby.ai. Needs their WithBy account. Not for navigation, bookings or places outside Washington.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "story_ids"
  ],
  "properties": {
    "story_ids": {
      "type": "array",
      "items": {
        "type": "integer",
        "maximum": 9999999999,
        "minimum": 1
      },
      "maxItems": 50,
      "minItems": 1,
      "description": "The stories' ids, as the story, stretch and nearby-stories answers give them"
    }
  }
}
    arguments 20 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 7016b22521bb8821.

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

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.