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

ttw-events

https://ttwchat.com

Registry code: eacbaadbe056f73b

api record

Search 500+ Toronto Tech Week 2026 events by date, theme, audience, format, and neighborhood.

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

endpoint
https://ttwchat.com/api/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 ttw-events live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is ttw-events free to use?
Yes — the hub reached it with no key and no payment.
What tools does ttw-events have?
3 tools: get_event, list_facets, search_events.
Is ttw-events 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
116ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 87 checks · signed record
  • unknown → live
_ what it is for
used for
  • search toronto tech week events
  • get event details
  • list event filters
takes → gives
text → data
tools
3 reads
_ 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 3 tools
3 open 3 of 3 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_event reads open 39d ago

    Get full details for one event by id, including description, host, venue, link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "integer",
          "description": "Event id from a previous search_events result"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • list_facets reads open 39d ago

    List all available filter values (dates, themes, audiences, formats, neighborhoods) with counts. Call this first if the user's question is open-ended.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_events reads open 39d ago

    Search Toronto Tech Week 2026 events. Combine `q` with optional filters. Returns lightweight rows; call get_event for full details.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Free-text search across title, description, host, venue"
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Single date YYYY-MM-DD"
        },
        "host": {
          "type": "string",
          "description": "Substring match against host or co-host name"
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results (default 10)"
        },
        "theme": {
          "type": "string",
          "description": "Substring match against theme tags, e.g. 'AI', 'Climate', 'Web3'"
        },
        "format": {
          "type": "string",
          "description": "Substring match against event format, e.g. 'Workshop', 'Panel', 'Demo'"
        },
        "audience": {
          "type": "string",
          "description": "Substring match against target audience, e.g. 'Founders', 'Seed', 'Engineers'"
        },
        "free_only": {
          "type": "boolean",
          "description": "Only events marked 'Open to the public'"
        },
        "date_range": {
          "type": "object",
          "properties": {
            "to": {
              "type": "string",
              "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
            },
            "from": {
              "type": "string",
              "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
            }
          },
          "description": "Inclusive date range. Use list_facets to see which dates have events.",
          "additionalProperties": false
        },
        "neighborhood": {
          "type": "string",
          "description": "Substring match, e.g. 'Queen West', 'King West', 'Downtown'"
        }
      },
      "additionalProperties": false
    }
    arguments 60 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 eacbaadbe056f73b.

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

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.