viaSocket
v1.1.0Use your apps from your AI: Gmail, Slack, Google Sheets, HubSpot and 2,300+ more on your accounts.
Endpoint health
online- Last checked
- 11/20/2026, 4:16:47 AM
- Latency
- 1431 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.viasocket.mcp%2Fmcp
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.viasocket.mcp/mcp": {
"url": "https://connect.viasocket.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
21 shown · authentication unknown
call_any_api_of_viasocket
Send a POST, PUT, PATCH or DELETE request to any viaSocket API endpoint for the user and return its response: every write (create, update, publish, delete). For GET requests use call_any_read_api_of_viasocket. Look the endpoint up with get_viasocket_api_docs first to get its URL, headers, query params and body, unless the skill or a dedicated tool on this server already gives them exactly. Load the quickstart-viasocket-developer-hub skill first: it explains which tool to use when. Pass the full url with path variables filled in, the headers the docs list, query params in `query` (not in the url) and the JSON body in `body`. For the auth header the docs name (Authorization, proxy_auth_token, x-api-key, ...), pass it with an empty value "": the signed-in user's token is filled in automatically. Never put a real or made-up token there; if the docs name no auth header, leave it out and the token is sent as Authorization. If the API needs the user to sign in, they're asked the first time. Only for the viaSocket endpoints documented on this server: it attaches the viaSocket sign-in, so never use it for Embarko (ship.embarko.ai) or any other service. Returns { status, ok, headers, data }: the HTTP status and the response body, including error details on failure.
Schema valid · SHA-256 9c9df43b198f…
View input schema
{ "type": "object", "properties": { "url": { "type": "string", "description": "Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here." }, "headers": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {}, "description": "Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value \"\" so the signed-in user's token is filled in; never put a token here yourself. Pass {} when the endpoint needs no headers. Example: {\"proxy_auth_token\": \"\", \"Content-Type\": \"application/json\"}" }, "query": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {}, "description": "Query params as name/value pairs; an array sends the param once per item. Example: {\"type\": \"flow\", \"bringflows\": true}" }, "method": { "type": "string", "enum": [ "POST", "PUT", "PATCH", "DELETE" ], "description": "HTTP method from the endpoint's docs" }, "body": { "type": "object", "propertyNames": { "type": "string" }, "additionalProperties": {}, "description": "JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body." } }, "required": [ "url", "headers", "method" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://connect.viasocket.com/mcp