Add TrickyBird to Websites

[trickybird-net]

Adds TrickyBird to the Websites section.

TrickyBird is a web proxy. Its home page registers one tool, open_site, through document.modelContext.registerTool. It takes one string, the address, validates it, and the tab navigates to the proxied page. The result is one of three fixed strings: ok, invalid_url or refused.

Disclosure: I maintain TrickyBird and I'm submitting my own site.

One detail that may interest the group, since it runs against the grain. Through a proxy every frame is same-origin, so the self default of the tools policy isolates nothing: a frame from the site a reader opened could register tools into the page the agent holds. So our gateway sends tools=() on every document it serves, and a proxied document can register no tools. The tool exists only on our own origin.

[anssiko]

Could you add a FAQ entry for WebMCP where you describe your slightly unusual use case and link to it directly, along the lines of OP? Niche use cases are interesting for the group.

[trickybird-net]

@anssiko The FAQ entry is live and linked from the list: https://trickybird.com/faq#faq-webmcp

Since proxied frames are same-origin, the self default of the tools policy fails to isolate anything, so the gateway refuses WebMCP on every document it serves; the one tool we register lives on our own home page.

Thanks for flagging it.