beacio MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Beacio iOS Safari Bluetooth SDK and extension guidance tools: Do tool guidance and platform limitations stay aligned with current Safari SDK and extension versions?

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

Best fit

Scaffold and troubleshoot Web Bluetooth integrations for iOS Safari, including beacio-specific extension APIs.

What we know

Developer-assistance MCP that can scaffold projects, choose Bluetooth filters/UUIDs, expose premium beacioIOS API docs and troubleshoot Safari-extension setup.

Maintenance / activity evidence

@beacio/mcp 2.2.0 published 2026-09-19T20:01:07.917Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Project scaffolding/documentation authority. Writes: Modify/scaffold project files.
Authentication not yet verified.
Sensitive access: Source code/project config

Local code mutation is the main authority; Bluetooth device control remains in the resulting app/browser runtime.

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

All limitations / Review context

Do tool guidance and platform limitations stay aligned with current Safari SDK and extension versions?

The bounded review of the publisher's documented Beacio iOS Safari Bluetooth SDK and extension guidance tools 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.

Local code mutation is the main authority; Bluetooth device control remains in the resulting app/browser runtime.
Project scaffolding/documentation authority.
Project metadata and requests are handled locally/through beacio docs; exact telemetry not established.
Reviewed write actions: Modify/scaffold project files
Sensitive access: Source code/project config
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.
This MCP is developer tooling; runtime Bluetooth permissions still belong to the browser/app.
Scaffolding can modify a local project.
Premium APIs require relevant beacio product access.
No evidence of direct arbitrary Bluetooth control through the MCP itself.

Original activity observations

@beacio/mcp 2.2.0 published 2026-09-19T20:01:07.917Z

Technical identity

npm/@beacio/mcp

Exact implementation source: https://www.npmjs.com/package/@beacio/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@beacio/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 metadata ↗
@beacio/mcp
Recorded package identity, distribution or download evidence.
Repository document ↗
wklm/beacio-sdk
Recorded repository material and project history.
Evidence source ↗
beacio.com/mcp
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

App account access and any external authorization are independent from local MCP uninstall; provider revoke route not independently verified.
Publisher baseline documentation retained; live recheck unavailable. This update does not establish a fresh publisher-source verification.
Reviewed actionability is baseline documentation only; client compatibility and runtime operation have not been verified.
Literal command/entry path confirmed against official README; does not validate runtime or host compatibility.
Prior reviewed safety note: Do not delete user data or assume this cancels upstream authorizations.
Prior reviewed safety note: beacio init/migrate modify application code and are NOT valid harmless connection tests.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.

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 -y @beacio/mcp
Configure / authenticate
MCP100 setup guide
MCP server gives developer tools for Beacio integration; `npx beacio init` installs application polyfill separately. Do not confuse Beacio SDK integration with MCP registration.
Check connection
Suggested check
Run official `npx beacio check` for app integration plus MCP tool discovery separately.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `beacio`, remove the client entry with `claude mcp remove beacio`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove beacio

Official Documentation & Sources

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

What it does

Developer-assistance MCP that can scaffold projects, choose Bluetooth filters/UUIDs, expose premium beacioIOS API docs and troubleshoot Safari-extension setup.

Capability: Developer Tools
Resource type: MCP Server
Best fit: Scaffold and troubleshoot Web Bluetooth integrations for iOS Safari, including beacio-specific extension APIs.

Representative uses

Scaffold Web Bluetooth project integration
Choose peripheral/service filters
Look up UUID/filter shapes
Read premium iOS API docs
Troubleshoot extension settings/entitlements

Limitations

This MCP is developer tooling; runtime Bluetooth permissions still belong to the browser/app.
Scaffolding can modify a local project.
Premium APIs require relevant beacio product access.
No evidence of direct arbitrary Bluetooth control through the MCP itself.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Project scaffolding/documentation authority.
Data handling: Project metadata and requests are handled locally/through beacio docs; exact telemetry not established.
Cost: freemium_or_premium
Risk and cautions: Local code mutation is the main authority; Bluetooth device control remains in the resulting app/browser runtime.

Access scope and cautions

Write actions: Modify/scaffold project files
Sensitive access: Source code/project config
Risk level: moderate

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: Scaffold Web Bluetooth project integration; Choose peripheral/service filters; Look up UUID/filter shapes; Read premium iOS API docs; Troubleshoot extension settings/entitlements.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @beacio/mcp. Recorded transport: stdio. Prerequisites: MCP client; project workspace. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No separate MCP credential documented for basic docs/scaffolding.

Can it modify data or perform write operations?

Documented write actions include: Modify/scaffold project files. Recorded permission boundary: Project scaffolding/documentation authority.

What data-handling boundary should I consider?

Project metadata and requests are handled locally/through beacio docs; exact telemetry not established. Recorded sensitive-access context: Source code/project config.

What limitations and risks should I check before use?

Local code mutation is the main authority; Bluetooth device control remains in the resulting app/browser runtime. This MCP is developer tooling; runtime Bluetooth permissions still belong to the browser/app. Scaffolding can modify a local project. Premium APIs require relevant beacio product access. No evidence of direct arbitrary Bluetooth control through the MCP itself. 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.