Luca Chang

One very last change (we're doing a hard cutoff on additional changes here): adding a `lastUpdatedAt` to the `Task` object: https://github.com/modelcontextprotocol/modelcontextprotocol/pull/1875

> Hi @LucaButBoring -- it's probably worth considering this alongside: #198 Looks like that's close to getting merged, any idea who to tag for more traction on that (also I...

Rebased and added a section to the spec on resource links.

Is that hypothetically possible to accomplish? Clients could simply misreport models if they choose to do so, and the server would be none the wiser. It only works if the...

In other words, the model provider would act as the root of the chain of trust, and transaction tokens would be verifiable against them? That sounds useful, particularly for compliance...

Since #1020 was closed, I took a look at the code here, leaving a few comments: 1. We should avoid duplicating dynamic client registration code and metadata discovery. 2. Client...

Sorry for the late turnaround, going to bring this to the WG tomorrow for initial thoughts - can you give an example of what the client or some other system...

Right, but what specifically would be done with the additional information? I don't fully understand that part, yet.

Linking for discoverability for others, though you've already read this: https://github.com/modelcontextprotocol/modelcontextprotocol/discussions/1927 Discussion essentially just came back to the same question: > Right, but what specifically would be done with the...

I think this should be split into separate SEPs for the immediate result mode and the streaming mode, if you have no objections to that (partial results has been a...