viaSocket MCP (remote)

90/100
Last tested 2026-11-04 (Fresh: tested within 30 days) Working (tool call tested 2026-11-04) No key needed for the tools we called; account tools need a sign-in

Advisories: not checked (remote-only)

Security review: not tested

Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology

  • Install20/20
  • Handshake30/30
  • Maintenance25/25
  • Docs15/15
  • License0/10

Vendor-hosted
viaSocket's hosted endpoint https://connect.viasocket.com/mcp (server viasocket-mcp 1.0.0) completed initialize and tools/list with no sign-in and listed 20 tools. Real calls (no LLM, no credentials): search_viasocket_docs answered a docs question (webhook triggers) with a docs link, and search_apps found Google Sheets in the app catalogue. get_org_details_by_token returned HTTP 401 'Authentication required for this tool', as documented: account, connection, plugin and run_app_action tools need OAuth sign-in and were not called. The registry also lists https://mcp.viasocket.com/mcp (com.viasocket/mcp), which served the same server in our probe.
Tool-call test (2026-11-04, direct MCP stdio client, no LLM): pass. 2 of 3 calls passed: search_viasocket_docs and search_apps. The account tool needs OAuth sign-in. No account; app actions not tested. Evidence: live endpoint probe, Nov 4, 2026.
viaSocket-hosted endpoint. Docs tools and app search answer without sign-in; account tools need OAuth sign-in. The server source isn't public: walkover-mcp/viasocket holds the README and server.json only, with no license file. Listed as a hosted remote (Our review, Nov 3, 2026).
Sources: https://github.com/walkover-mcp/viasocket · https://github.com/walkover-mcp/viasocket/commit/5fdaa70e93 · https://registry.modelcontextprotocol.io/v0/servers?search=com.viasocket.mcp/mcp

Transport (tested 2026-11-04): Streamable HTTP

Token cost (estimate): approx. 4634 tokens, cl100k estimate (20 tools, measured 2026-11-11). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.

Permissions: 15 read, 5 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown

Auth: none. Rate limit: unknown. Pricing unit: unknown.

  • call_any_api_of_viasocket — write (state-changing)
  • call_any_read_api_of_viasocket — read
  • create_connection_link — read
  • get_org_details_by_token — read
  • get_plugin_analytics — read
  • get_viasocket_api_docs — read
  • get_viasocket_embed_secret — write (state-changing)
  • list_action_versions — read
  • list_actions_and_triggers — read
  • list_app_actions — read
  • list_auth_versions — read
  • list_connections — read
  • list_embed_projects — read
  • list_plugins — read
  • quickstart-viasocket-developer-hub — read
  • report_feedback — write (state-changing)
  • report_published — write (state-changing)
  • run_app_action — write (state-changing)
  • search_apps — read
  • search_viasocket_docs — read

remote handshake listed tools without credentials; no recorded key or OAuth

Score 90/100 · Tools 20 · Token cost approx. 4,634 tokens · Compare · Last tested 2026-11-04 · Server version 1.0.0 · Remote endpoint https://connect.viasocket.com/mcp (streamable-http)

Summary: viaSocket MCP (remote) completed an MCP handshake without credentials and exposed 20 tools.

Evidence summary

Handshake
pass
Tools listed
20
Context cost
approx. 4634 tokens, cl100k estimate (20 tools, measured 2026-11-11; an estimate) ranking · add up your servers' context cost
Login
No key needed for the tools we called; account tools need a sign-in
Tested
2026-11-04

Test results

TestResultPointsEvidence
installpass20Endpoint https://connect.viasocket.com/mcp reachable over streamable-http (HTTP 200) in 16.3s; no install step for remote servers.
handshakepass30MCP initialize (protocol 2025-06-18, server viasocket-mcp 1.0.0) + tools/list over streamable-http succeeded with no credentials; 20 tools listed in 16.3s. Tool calls may still need a key.
maintenancepass25Vendor-hosted rule: scored from dated commit in viaSocket's MCP docs repo 2026-11-03 (https://github.com/walkover-mcp/viasocket/commit/5fdaa70e93), 1 day before test. Registry (corroboration only, not scored): com.viasocket.mcp/mcp 1.1.0 published 2026-11-03.
docspass15official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://github.com/walkover-mcp/viasocket).
licensefail0Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source).

Local-model readiness

Token cost (estimate): approx. 4634 tokens, cl100k estimate for 20 tools · about 57% of an 8k context. This is an estimate from our testing (counted with cl100k_base).

Small-model friendly (schema heuristic, not a model result): unknown.

Not tested

Small-model task runs: Not yet tested.

What we tested and what we didn't

Tested on 2026-11-04

  • We connected to the vendor's hosted endpoint with no credentials and asked for its tool list: it listed 20 tools (Method details: MCP initialize then tools/list)
  • Auth response: none. The endpoint answered without any login
  • Vendor docs: official MCP docs page; states the endpoint URL; client setup instructions (15/15)
  • Maintenance: dated vendor source, dated commit in viaSocket's MCP docs repo 2026-11-03 (25/25)
  • License: a hosted service has no license to cite (0/10)
  • Token cost (estimate)

Not tested

  • Security: not audited (hosted service; no code to review, no permission or data-flow analysis)
  • Behaviour after signing in, or with a real account
  • Source code, repository activity or an open-source license (none published for the hosted service)
  • Performance, rate limits or load
  • Real tasks (no functional task runs yet)

Methodology: how we test (vendor-hosted rule). A high score means it responds and its vendor documents and dates it, not that giving it access to your data carries no risk.

Known security issues

Not checked (remote-only): hosted endpoint, version unknown.

Monthly roundup: MCP security issues, October 2026.

Tool list changes

Unchanged since the previous snapshot (latest 2026-11-11).

Snapshot hash (fingerprint of the tool list)

51ccd6da73ee: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.

Feeds: RSS · JSON.

Raw test record (JSON)
{
  "name": "viasocket-remote",
  "version": null,
  "registry": "remote",
  "status": "working",
  "tested": "2026-11-04",
  "tools_count": 20,
  "deprecated": false,
  "archived": null,
  "tests": {
    "install": [
      "pass",
      20,
      "Endpoint https://connect.viasocket.com/mcp reachable over streamable-http (HTTP 200) in 16.3s; no install step for remote servers."
    ],
    "handshake": [
      "pass",
      30,
      "MCP `initialize` (protocol 2025-06-18, server viasocket-mcp 1.0.0) + `tools/list` over streamable-http succeeded with no credentials; 20 tools listed in 16.3s. Tool calls may still need a key."
    ],
    "maintenance": [
      "pass",
      25,
      "Vendor-hosted rule: scored from dated commit in viaSocket's MCP docs repo 2026-11-03 (https://github.com/walkover-mcp/viasocket/commit/5fdaa70e93), 1 day before test. Registry (corroboration only, not scored): com.viasocket.mcp/mcp 1.1.0 published 2026-11-03."
    ],
    "docs": [
      "pass",
      15,
      "official MCP docs page; states the endpoint URL; client setup instructions. Vendor-hosted rule: scored from the vendor's official MCP docs (https://github.com/walkover-mcp/viasocket)."
    ],
    "license": [
      "fail",
      0,
      "Vendor-hosted service with no public repo: no license to cite, so 0 (rule: no points without a cited source)."
    ]
  }
}

Install

https://connect.viasocket.com/mcp

Tools listed

call_any_api_of_viasocket, call_any_read_api_of_viasocket, create_connection_link, get_org_details_by_token, get_plugin_analytics, get_viasocket_api_docs, get_viasocket_embed_secret, list_action_versions, list_actions_and_triggers, list_app_actions, list_auth_versions, list_connections, list_embed_projects, list_plugins, quickstart-viasocket-developer-hub, report_feedback, report_published, run_app_action, search_apps, search_viasocket_docs

Tool history: captured Nov 11, 2026. All tool history.

Quick config

{
  "mcpServers": {
    "viasocket-mcp-remote": {
      "type": "http",
      "url": "https://connect.viasocket.com/mcp"
    }
  }
}

Add to config Opens the config generator with this server selected.

Setup

  1. Install. No install step: it is a remote server at https://connect.viasocket.com/mcp.
  2. Configure. Add the mcpServers entry below to your MCP client config.
  3. Verify. Restart the client and check that tools/list returns tools (20 in our test).
{
  "mcpServers": {
    "viasocket-mcp-remote": {
      "type": "http",
      "url": "https://connect.viasocket.com/mcp"
    }
  }
}

Test history

Follow this server (RSS) · Monthly changelog

FAQ

Is viaSocket MCP deprecated?

No. viasocket-remote was not deprecated or archived when we last tested it on 2026-11-04.

What replaces viaSocket MCP?

Nothing; viaSocket MCP (remote) is not deprecated as of 2026-11-04.

Does viaSocket MCP need an API key?

No key for docs search: search_viasocket_docs and search_apps worked without one. Its account, connection, plugin and app-action tools need a viaSocket sign-in, which we did not test. It completed an MCP handshake with no credentials and listed 20 tools.

Embed the badge

TestedMCP: 90/100, tested 2026-11-04

Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.

Claim this listing · Report an issue