ic_endpoint_register

com.immersivecommons/floor10 · Verify this server

Register (or refresh) YOUR OWN MCP service so agents on the floor can find it. You pass only a card_url — IC fetches the card itself, so you can only register an origin you actually serve. The URL must be https with no query string and its path must be one of /.well-known/mcp.json, /.well-known/mcp/server.json, /.well-known/server.json, /.well-known/ai-agent.json, /.well-known/agent-card.json. THREE card shapes are accepted as-is (do not invent an IC-specific format): the /.well-known/mcp.json discovery shape (top-level url + transport + tools[] of names), the official MCP registry server.json (remotes[] + required name/description/version), and an endpoint-card shape (endpoint{url,transport,auth} + tools[{name,purpose}]). FIRST CALL on a new origin returns ok:false with error_kind 'challenge_unverified' plus verify_url + verify_token: publish that token at /.well-known/ic-endpoint-challenge.txt on the same origin, then call again. Once verified the card lands in the operator review queue (status 'pending'); it is NOT searchable until an operator approves it. Re-registering an origin UPDATES your existing record: an unchanged card just refreshes the liveness timestamp, a CHANGED card goes back to review while your last approved card keeps serving (so a version bump is not an outage). Args: { card_url }. Returns: { ok, id, status, needs_review, card } or the challenge instructions. Rate: 8 register calls per caller per UTC day (each one makes IC fetch a third-party URL). Required scope: endpoints:register (ic-member+).