Rkvst MCP integration

No. The toolkit is built for retrieval and verification - Get Asset, List Asset Events, Search Events, and the attachment actions read the record, and its only writes are Update App Registration and Promote Member. Recording new evidence stays inside RKVST, which is the consistent position for a chain of custody that would be worth less if any connected assistant could append to it.

Yes. Get Asset accepts an at_time parameter that returns the asset's state as of that moment rather than its current one. That is the difference between reporting today's attributes and evidencing what was actually true when a shipment changed hands.

Visibility, and the toolkit keeps entirely separate actions for each. List Assets, Get Asset, and List Asset Events require tenancy authentication, while List Public Assets, Get Public Asset, and Get Public Asset Event read records that were deliberately published - the route to hand a counterparty evidence without granting them anything inside your tenancy.

Retrieve Caps returns the resource quotas for a given service, which is the check worth making before a bulk retrieval rather than after one fails partway through. It is a read like everything else here, so asking costs nothing against the limit you are checking.