VTC Spaces

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.vtc/mcp and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 22 Oct 2026. Not supplied by the maker.

• login_with_otp

  Start ZAPI OTP login for an existing account. Then call verify_otp with the code and space group_id. Prefer explain_space_context after auth before querying.

• verify_otp

  Complete OTP login and store a space-scoped JWT in memory only (not on disk). group_id is required for Shared space DB access.

• validate_jwt

  Decode the current session JWT claims (no signature verify — ZAPI verifies on /db/).

• set_session_jwt

  Set/replace the in-memory JWT (space-scoped token from the app). Prefer OTP for interactive use. JWT is never written to disk.

• explain_space_context

  Call this first after auth. Summarizes environment, group_id, user, and role so you do not query the wrong Space or live vs beta.

• search_public

  Search public people by username, and public spaces or networks by name or username (no login). Networks are spaces with kind "network". Use a space or network id with set_guest_context.

• search_public_spaces

  Find public VTC Spaces by space name or space username/slug (no login). Use the returned id with set_guest_context.

• search_public_people

  Find public people by username (optional leading @). No login. People who opted out of search, or who are only in a private network, are omitted. Email is not searchable.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.