Muovi MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Muovi professional discovery and user-published task drafts: Do agents remain limited to drafts and deep links rather than silently publishing marketplace commitments?

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

Best fit

Read-only discovery of verified LATAM local service professionals with strict anti-leakage policy.

What we know

Thin read-only wrapper over Muovi public API for professionals, service catalog, cities, reviews and task-creation deep links. The MCP intentionally never returns phone/email/WhatsApp; hiring/payment/dispute flow stays on-platform.

Maintenance / activity evidence

@muovi/mcp-server 0.4.0 published 2026-10-05T02:19:24.208Z

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.
Read-only public professional/catalog/review access plus deep-link formatting.
Optional API key.
Sensitive access: Public professional data, User local-service search intent

No booking/payment authority; trust/payment/dispute actions happen only after user follows on-platform link.

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

All limitations / Review context

Do agents remain limited to drafts and deep links rather than silently publishing marketplace commitments?

The bounded review of the publisher's documented Muovi professional discovery and user-published task drafts 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.

No booking/payment authority; trust/payment/dispute actions happen only after user follows on-platform link.
Read-only public professional/catalog/review access plus deep-link formatting.
Optional API key.
Public profile/review data from Muovi; package applies an additional local anti-leakage detector.
Sensitive access: Public professional data, User local-service search intent
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.
Two tools were documented as pending production backend fixes in the package README; live status should be rechecked.
Remote hosted transport was documented as not yet fully live; stdio is canonical.
No off-platform contact leakage is allowed.
Package honestly documents some registered tools/remote transport as not yet fully backed by production endpoints; preserve live-status caveat.

Original activity observations

@muovi/mcp-server 0.4.0 published 2026-10-05T02:19:24.208Z

Technical identity

npm/@muovi/mcp-server

Exact implementation source: https://www.npmjs.com/package/@muovi/mcp-server ↗
Reviewed resource type: MCP Server
Repository identity: muovi-latam/mcp-server
Package identity: npm:@muovi/mcp-server

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 ↗
@muovi/mcp-server
Recorded package identity, distribution or download evidence.
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

Publisher documentation reviewed; compatibility with user environment and live service not tested.
Documented by publisher; environment and client prerequisites still required. Placeholder values must not be executed verbatim.
MCP100 normalized this JSON from publisher-documented package, env and/or client examples; not verified byte-for-byte against a live client. This is not Codex config.toml or VS Code servers JSON.
A Muovi API key is optional for authenticated access; do not use credentials from another product.
Read-only verification: muovi_list_services or muovi_list_cities; do not use muovi_create_task_draft as smoke check.
Do not invoke muovi_create_task_draft during verification.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.

Install / connect
Publisher instructions
Public v1 endpoints work keylessly; optional MUOVI_API_KEY for higher rate limits.
publisher install or stdio launch · Publisher instructions
npx -y @muovi/mcp-server
Configure / authenticate
MCP100 setup guide
Muovi stdio config: command npx, args ["-y", "@muovi/mcp-server"]. Muovi API key is optional. Do not set MsgMesh MQ_API_KEY here.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "muovi": { "args": [ "-y", "@muovi/mcp-server" ], "command": "npx" } } }
Check connection
Suggested check
Use official muovi_list_services or muovi_list_cities (read-only) after connecting, rather than saving a task draft.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `muovi`, run `claude mcp remove muovi` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: Muovi API key is optional in publisher documentation. No-key route: revocation not applicable; if supplied, key lifecycle is an independent account operation.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove muovi

Official Documentation & Sources

What it does

Thin read-only wrapper over Muovi public API for professionals, service catalog, cities, reviews and task-creation deep links. The MCP intentionally never returns phone/email/WhatsApp; hiring/payment/dispute flow stays on-platform.

Capability: Search & Web
Resource type: MCP Server
Industry: Professional Services
Best fit: Read-only discovery of verified LATAM local service professionals with strict anti-leakage policy.

Representative uses

Search verified professionals
Read profiles/portfolio/verifications
List services/cities
Read reviews
Create canonical on-platform task link

Limitations

Two tools were documented as pending production backend fixes in the package README; live status should be rechecked.
Remote hosted transport was documented as not yet fully live; stdio is canonical.
No off-platform contact leakage is allowed.
Package honestly documents some registered tools/remote transport as not yet fully backed by production endpoints; preserve live-status caveat.

Reviewed access

Access & risk

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

Authentication: Optional API key.
Permissions: Read-only public professional/catalog/review access plus deep-link formatting.
Data handling: Public profile/review data from Muovi; package applies an additional local anti-leakage detector.
Cost: free
Risk and cautions: No booking/payment authority; trust/payment/dispute actions happen only after user follows on-platform link.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Public professional data User local-service search intent
Risk level: low

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: Search verified professionals; Read profiles/portfolio/verifications; List services/cities; Read reviews; Create canonical on-platform task link.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @muovi/mcp-server. Recorded transport: stdio. Recorded environment-variable notes: MUOVI_API_KEY (optional higher rate limit); MUOVI_API_BASE_URL (optional). No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Public unauthenticated API by default; optional API key for higher rate-limit tier.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only public professional/catalog/review access plus deep-link formatting.

What data-handling boundary should I consider?

Public profile/review data from Muovi; package applies an additional local anti-leakage detector. Recorded sensitive-access context: Public professional data; User local-service search intent.

What limitations and risks should I check before use?

No booking/payment authority; trust/payment/dispute actions happen only after user follows on-platform link. Two tools were documented as pending production backend fixes in the package README; live status should be rechecked. Remote hosted transport was documented as not yet fully live; stdio is canonical. No off-platform contact leakage is allowed. Package honestly documents some registered tools/remote transport as not yet fully backed by production endpoints; preserve live-status caveat. 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.