IC MCP: module-hash lookup tool, and manifest support for OISY and MULTI/DEX

Uncategorized
1

Hi all,

I use the Internet Computer MCP connector to monitor canister upgrades, and I’ve run into two gaps.

  1. No module-hash lookup. The connector can fetch Candid and run queries, but it has no tool to get a canister’s module hash, controllers or status. A tool like lookup_canister_info_by_id would let agents detect upgrades by comparing hashes. Is something like this planned? If not, could it be added?
  2. OISY and MULTI/DEX can’t be read. The connector only reads canisters that an app lists in /.well-known/ic-architecture. Neither oisy nor multidex.ai publishes that file. oisy returns the SPA’s index.html for that path, and multidex.ai only serves the older ic-app.json. Could the teams behind both apps publish the manifest? The recipe is in the DFINITY docs under service discoverability. For OISY, that likely means exempting /.well-known/* from the SPA rewrite.

Even a manifest that lists only the public, read-only canisters would help. It would let agents and users verify deployments and follow interface changes.

Thanks!