List your agent

VTC Spaces

MCP server · hosted · v0.5.1 · com.vtc/mcp
Online · tested 3h agoNEW · 4h agoSeen in the registry 3h ago

Search public VTC Spaces and people; sign in to query Space data and run AI actions and workflows.

What it does

VTC Spaces is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version0.5.1
PriceNot in the registry
First seen22 Oct 2026
Last checked3h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 3h ago (live check)

Hosted endpoint

  • https://mcp.vtc.com/mcp streamable-http

In Claude Code: claude mcp add --transport http vtc-spaces https://mcp.vtc.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "vtc-spaces": {
      "url": "https://mcp.vtc.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 3h ago

ONLINE VTC Spaces answered an MCP connection on 22 Oct 2026 and introduced itself as vtc-space-db 0.5.1 (MCP protocol 2025-06-18).

29 tools offered to AI assistants

  • 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.
  • set_guest_context · Bind a Space for guest/public tools (no login). Accepts a numeric id, public slug (dexi), or a name that matches one public space. Prefer search_public_spaces when the name may match several spaces.
  • list_guest_public_apps · List apps on a Space dashboard that allow guest browse (public_guest_access=yes). Uses public ZAPI — no Space JWT.
  • describe_public_app_surface · AI manifest plus guest/public read hints for one app (module_code). No Space JWT required.
  • list_public_collection_documents · Read documents from a collection the Space marked public-read (ZAPI). No JWT.
Show 17 more
  • fetch_app_public_route · GET an allowlisted HTTPS public API URL on *.apps.vtc.com (path must include /public). No JWT.
  • space_db_info · Call after auth (and ideally after explain_space_context). Resolves the current Shared space silo via ZAPI (URI redacted). Does not accept group_id — silo is always the JWT space.
  • list_collections · List collections in the authenticated space silo (excludes system.*). Call this before assuming collection names. Use include_counts sparingly.
  • count_documents · Count documents with an optional filter. Soft-deleted rows (status=deleted) are excluded by default when the collection has status — set include_deleted=true to override.
  • find_documents · Find documents (max 50, skip capped). Prefer narrow filter + projection. Call list_collections and sample_document before guessing schema. Soft-deletes excluded by default; sensitive fields redacted by default.
  • sample_document · Return one document for schema inference. Sensitive fields are redacted by default. Prefer this before large finds.
  • list_developer_catalog · Public ZAPI developer catalog of app-facing API services (no auth). Use when discovering platform endpoints for child apps — not for Space Mongo data.
  • list_space_apps · List apps installed / owned in the authenticated Space (JWT group_id). Call explain_space_context first. Not a Mongo query.
  • get_ai_manifest · Fetch the AI tool manifest for a module_code (installed app). Use after list_space_apps when you need tool schemas — not for inspecting Mongo collections.
  • get_space_summary · Lightweight summary of the authenticated Space from JWT claims (group_id, network_id, role). Does not query Mongo. Prefer this or explain_space_context before DB tools.
  • list_available_actions · List AI Guide tools the current JWT may run (default: platform.* only). Opt into installed app manifests with include_apps or VTC_MCP_ACTION_MODULES. Call explain_space_context first. Does not execute anything.
  • execute_action · Execute an AI Guide tool via ZAPI /ai/tools/execute (same path as in-product Guide). For confirm_required tools: first call WITHOUT confirmation_token returns a proposal; second call WITH confirmation_token performs the action. Read-only to
  • list_workflows · List saved workflows in the authenticated Space. Call explain_space_context first. Read-only.
  • get_workflow · Fetch one space workflow by id (steps, trigger, gaps). Read-only.
  • propose_workflow · Draft a workflow from natural language via ZAPI /ai/propose-workflow. Does not persist — review then save_workflow. Prefer this over inventing step schemas.
  • save_workflow · Create a workflow in the Space (space admin JWT). First call returns confirmation_token; second call with that token persists. Defaults automation_enabled to false unless you set true explicitly. Does not use /ai/execute-agent.
  • run_workflow · Run a saved workflow. dry_run=true (default) previews without side effects. dry_run=false requires confirmation_token from a prior proposal. Does not call /ai/execute-agent.

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://mcp.vtc.com/mcpDECLAREDSRC-001 Official MCP Registry3h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry3h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry3h ago
Websitehttps://vtc.com/developersDECLAREDSRC-001 Official MCP Registry3h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry3h ago
Version0.5.1DECLAREDSRC-001 Official MCP Registry3h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry3h ago

Change history

  • NEW22 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Questions about VTC Spaces

How do I connect VTC Spaces?

Use the hosted endpoint https://mcp.vtc.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does VTC Spaces offer?

When Electra Index connected on 22 Oct 2026, it listed 29 tools: login_with_otp, verify_otp, validate_jwt, set_session_jwt, explain_space_context, search_public, search_public_spaces, search_public_people and more. The full list is in "Live check" above.

Is VTC Spaces online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 3h ago.