Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Track room lifecycle and capability-sharing behavior because the service is intentionally ephemeral
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
Temporary human-agent collaboration
What we know
Temporary rooms for human/agent voice, text, files and screen sharing with a stateless MCP Room API.
Maintenance / activity evidence
- Observed (UTC)chore(agent): prepare runtime release v0.5.56
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.
- Participants retain their own tools and credentials. Writes: Participant-side task actions after room grants/approvals.
- Room-scoped entry.
- Sensitive access: Voice, Text, Files, Screens, Agent context
- Independent agents retain their own credentials/capabilities, so room grants and shared media define an important trust boundary.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
1,208 repository stars
Stars observed Oct 6, 2026.
No canonical package metric applied.
No canonical package metric applied.
No canonical package metric applied.
All limitations / Review context
What MCP capability and privacy boundaries are documented for temporary rooms?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- Independent agents retain their own credentials/capabilities, so room grants and shared media define an important trust boundary.
- Participants retain their own tools and credentials.
- Room-scoped entry.
- Temporary room/media/artifact data is handled by the service.
- Reviewed write actions: Participant-side task actions after room grants/approvals
- Sensitive access: Voice, Text, Files, Screens, Agent context
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- Install command
- Endpoint
- Exact auth mechanism
- Pricing
- Product/technical testbed.
- Rooms expire and do not provide permanent history.
Original activity observations
- 2026-10-05T14:46:11Z: chore(agent): prepare runtime release v0.5.56
Technical identity
github.com/i365dev/free4chat- Exact implementation source
- https://github.com/i365dev/free4chat ↗
- Reviewed resource type
- MCP Server
- Repository identity
- i365dev/free4chat
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
i365dev/free4chat
Recorded repository material and project history.
Setup · Watchlist
Self-hosted gateway service setup
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsPublisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
Connection / UI instruction · Publisher instructions
Connect an MCP HTTP-capable client to https://www.free4.chat/mcpConfigure / authenticate
Publisher instructionsFree4Chat offers a hosted stateless MCP Room API: no API key, OAuth or local package. Do not confuse with local `free4chat-agent` resident Runtime install.
Check connection
Suggested checkDiscover `room_info` and related Room API tools through the client; joining a Room is a separate deliberate operation.
Remove / uninstall / revoke
MCP100 setup guideDelete/disconnect `free4chat` MCP URL from host configuration; if joined, use `leave_room(participantHandle)` first. The Room API is hosted, no local server to uninstall.
What it does
Temporary rooms for human/agent voice, text, files and screen sharing with a stateless MCP Room API.
- Capability
- Communication
- Resource type
- MCP Server
- Best fit
- Temporary human-agent collaboration
Representative uses
- Create/join temporary rooms
- Voice/text collaboration
- Share files/images/screens
- Connect independently running agents
Limitations
- Product/technical testbed.
- Rooms expire and do not provide permanent history.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- Room-scoped entry.
- Permissions
- Participants retain their own tools and credentials.
- Data handling
- Temporary room/media/artifact data is handled by the service.
- Cost
- unknown
- Risk and cautions
- Independent agents retain their own credentials/capabilities, so room grants and shared media define an important trust boundary.
Access scope and cautions
- Write actions
- Participant-side task actions after room grants/approvals
- Sensitive access
- Voice Text Files Screens Agent context
- Risk level
- high
FAQ
Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What authentication is documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
Is this an official MCP?
i365dev is listed as Community implementation in MCP100’s current evidence.