Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Toronto Tech Week 2026 Events

REMOTE · TTWCHAT.COM · SCANNED SEP 24

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

Available components

0 this week 77 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability84
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Toronto Tech Week 2026 Events MCP server?

Toronto Tech Week 2026 Events is a hosted endpoint at https://ttwchat.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · ttwchat.com

# add to Claude Code
claude mcp add --transport http simistern-ttw-chat 'https://ttwchat.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "simistern-ttw-chat": {
      "url": "https://ttwchat.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "simistern-ttw-chat": {
      "type": "http",
      "url": "https://ttwchat.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.simistern-ttw-chat]
url = "https://ttwchat.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "simistern-ttw-chat": {
      "type": "remote",
      "url": "https://ttwchat.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add simistern-ttw-chat --url 'https://ttwchat.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  simistern-ttw-chat:
    url: "https://ttwchat.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "simistern-ttw-chat": {
      "Transport": "http",
      "Url": "https://ttwchat.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add simistern-ttw-chat -t streamable-http -u 'https://ttwchat.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "simistern-ttw-chat": {
      "type": "http",
      "url": "https://ttwchat.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Sept 26 +1
    • Stability: 0.97 → pass security
  • 2 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Aug 26 73
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 6 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 5 Aug 26 0
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Sept 2026 · Probed https://ttwchat.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ttwchat.com CN=YE1,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 611283130463ef61024f56c6eb649e4448c
SANs: *.ttwchat.com, ttwchat.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ttwchat.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ttwchat.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ttwchat.com/api/mcp Verified 200
http (plaintext) http://ttwchat.com/api/mcp HTTPS enforced 301 https://ttwchat.com/api/mcp
MCP tools · 3 exposed · ~316 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_event ~41

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

NameTypeReqDescription
idintegeryesEvent id from a previous search_events result

No output schema declared.

No examples provided.

list_facets ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_events ~236

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

NameTypeReqDescription
audiencestring–Substring match against target audience, e.g. 'Founders', 'Seed', 'Engineers'
datestring–Single date YYYY-MM-DD
date_rangeobject–Inclusive date range. Use list_facets to see which dates have events.
formatstring–Substring match against event format, e.g. 'Workshop', 'Panel', 'Demo'
free_onlyboolean–Only events marked 'Open to the public'
hoststring–Substring match against host or co-host name
limitinteger–Max results (default 10)
neighborhoodstring–Substring match, e.g. 'Queen West', 'King West', 'Downtown'
qstring–Free-text search across title, description, host, venue
themestring–Substring match against theme tags, e.g. 'AI', 'Climate', 'Web3'

No output schema declared.

No examples provided.

Common questions

What is the Toronto Tech Week 2026 Events MCP server?

Toronto Tech Week 2026 Events is an MCP server listed in the public MCP registry as io.github.simistern/ttw-chat. Search 500+ Toronto Tech Week 2026 events by date, theme, audience, format, and neighborhood. This page covers its hosted endpoint (https://ttwchat.com/api/mcp).

Is the Toronto Tech Week 2026 Events MCP server safe to use?

Toronto Tech Week 2026 Events scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Toronto Tech Week 2026 Events MCP server expose?

Toronto Tech Week 2026 Events exposes 3 tools: search_events, get_event, list_facets. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.

Does the Toronto Tech Week 2026 Events MCP server require authentication?

No. We connected to Toronto Tech Week 2026 Events without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Toronto Tech Week 2026 Events MCP server still maintained?

Toronto Tech Week 2026 Events is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.