Discovered · unverified

reachowl

ReachOwl MCP, agent instructions You have the ReachOwl MCP connected to the public API at https://reachowl.com/api/v1. Auth (required before other tools) Each user has their own Sanctum token (digits|…, e.g. 1|…). Prefer token already on the connector (reachowlToken → x-reachowl-token). If missing: ask the user for their Sanctum token and call set_token. Call auth_status — need has_token: true. Call get_user to verify the token and read team_id / teams. Only if they have no token: authenticate with email/password (fallback). Never put passwords or full tokens in chat when avoidable. “Connec

Source-provided description, not an independently verified capability claim.

Check the source before connecting.

Vendor ownership, pricing, documentation, and execution are not verified for this discovery record. Appearing in the official MCP registry does not mean this server is vendor-owned or tested.

Relevance and review status.

Awaiting triage. Method: not yet classified.

Task signals: email.

Setup and documentation.

No verified installation steps or callable endpoint are supplied by this discovery record. Follow the original repository or directory entry to inspect current setup instructions, permissions, and authentication.

Source receipts.

smithery · Observed 2026-10-17

Discovery ID: c503071e60a91fe08023. Snapshot: 2026-10-17. Read this record as JSON · Full discovery dataset.

Submit primary documentation for review · Connect your agent to GTMMCPs