schema-first

This host is a remote MCP server at https://dev-seat.taila782b5.ts.net/mcp.

Tools

• memo_write saves a note. Input is { text }. Result is { id }.
• memo_search finds notes. Input is { query }. Result is { notes: [{ id, text }] }. A note matches when its text contains the query.
• upload stores a file on this server. Send content plus filename, or a url to fetch. Result is { url }. That link is served by this host and anyone can open it.
• transcribe reads audio at a url and returns timestamped text. Input is { url }. Result is { segments: [{ start, text }] }. start is seconds.

Sign-in

Only a client you allow can call the tools. Sign-in is OAuth 2.1, authorization code with PKCE.

1. The client calls the MCP endpoint with no token and gets 401. The header points at the protected resource metadata.
2. The client reads the authorization server from that metadata, then registers or presents a client-id metadata document.
3. You open the connect link. This host shows who is asking. Allow issues a code and sends the client back. Deny sends the client away.
4. The client exchanges the code for a bearer token bound to this MCP endpoint. Later calls must send that token.

Data kept

• Notes: id, text, and the time they were saved.
• Files: id, name, type, bytes, and the time they were stored. The public link stays until the file is deleted.
• Audio for transcribe is downloaded, sent to the transcription service, then deleted. The transcript is returned and not stored.
• Sign-in records: approved clients, one-time codes, and bearer tokens. Tokens are not written to the log.

Local-only requests are not a public address. A public https origin is set only when this process is started with one.