Asyntai MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Asyntai OAuth stdio bridge to support-agent management: Does the bridge preserve account-scoped conversation and lead access without becoming a separate support engine?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Connect a local MCP client to a hosted website support assistant and its account data.

What we know

Run your website's AI support agent: knowledge, conversations, leads and live replies. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@asyntai/mcp 1.0.2 published 2026-09-08T04:23:13.812Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
OAuth sign-in handled by local stdio bridge
Sensitive access: Website conversations, Lead/contact information, OAuth session

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does the bridge preserve account-scoped conversation and lead access without becoming a separate support engine?

The bounded review of the publisher's documented Asyntai OAuth stdio bridge to support-agent management and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
OAuth sign-in handled by local stdio bridge
Client tool requests are forwarded to hosted Asyntai account MCP.
Sensitive access: Website conversations, Lead/contact information, OAuth session
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
repositoryIdentity: no confirmed package-to-repository binding
writeActions: exact exposed tool mutation authority
cost: plans, pay-per-call charges, and payment authorization details
npm package is a stdio-to-hosted-MCP OAuth bridge, not an independent local server
Exact live account mutation and write scope must be checked
Do not represent the npm bridge as self-contained or infer read-only scope; hosted authenticated service owns the authority.

Original activity observations

@asyntai/mcp 1.0.2 published 2026-09-08T04:23:13.812Z

Technical identity

npm/@asyntai/mcp

Exact implementation source: https://www.npmjs.com/package/@asyntai/mcp ↗
Reviewed resource type: Gateway
Package identity: npm:@asyntai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@asyntai/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
www.npmjs.com/~asyntai
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · retained baseline · Publisher instructions
npx @asyntai/mcp
Configure / authenticate
MCP100 setup guide
Local bridge uses OAuth 2.1 PKCE login with saved tokens; authenticate through the popup/host flow, no static API key.
Check connection
Suggested check
Confirm tool discovery and authenticated read-only tools.
Remove / uninstall / revoke
MCP100 setup guide
Unregister the `asyntai` MCP server from the specific client host, then run `npx @asyntai/mcp logout` to forget saved OAuth tokens. Two separate steps.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Local session logout · separate from client removal / provider revocation · Publisher instructions
npx @asyntai/mcp logout

Official Documentation & Sources

https://www.npmjs.com/package/@asyntai/mcp ↗

What it does

Run your website's AI support agent: knowledge, conversations, leads and live replies. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Communication
Resource type: Gateway
Best fit: Connect a local MCP client to a hosted website support assistant and its account data.

Representative uses

Review site support knowledge and conversations
Manage support-agent functions where token permits

Limitations

npm package is a stdio-to-hosted-MCP OAuth bridge, not an independent local server
Exact live account mutation and write scope must be checked
Do not represent the npm bridge as self-contained or infer read-only scope; hosted authenticated service owns the authority.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth sign-in handled by local stdio bridge
Permissions: Not documented in the reviewed sources
Data handling: Client tool requests are forwarded to hosted Asyntai account MCP.
Cost: Not documented in the reviewed sources
Risk and cautions: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Website conversations Lead/contact information OAuth session
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Review site support knowledge and conversations; Manage support-agent functions where token permits.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @asyntai/mcp. Recorded transport: stdio. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: OAuth sign-in handled by local stdio bridge

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Client tool requests are forwarded to hosted Asyntai account MCP. Recorded sensitive-access context: Website conversations; Lead/contact information; OAuth session.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. npm package is a stdio-to-hosted-MCP OAuth bridge, not an independent local server. Exact live account mutation and write scope must be checked. Do not represent the npm bridge as self-contained or infer read-only scope; hosted authenticated service owns the authority. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.