{"schema_version":1,"snapshot_id":"bfb936f5ceae4a7427f93961201723779c3021545a3c4222395e8678314c3e55","generated_at":"2026-10-17T21:51:24.907033+00:00","notice":"Potential GTM matches from directory metadata and model triage. Discovered does not mean vendor-verified or tested. Pending records remain under review; pricing and install details require primary sources.","canonical_url":"https://gtmmcps.com/discoveries/c503071e60a91fe08023","record":{"id":"c503071e60a91fe08023","name":"reachowl","aliases":["reachowl"],"description":"ReachOwl MCP, agent instructions\n\nYou have the ReachOwl MCP connected to the public API at https://reachowl.com/api/v1.\n\nAuth (required before other tools)\n\nEach user has their own Sanctum token (digits|…, e.g. 1|…).\nPrefer token already on the connector (reachowlToken → x-reachowl-token).\nIf missing: ask the user for their Sanctum token and call set_token.\nCall auth_status — need has_token: true.\nCall get_user to verify the token and read team_id / teams.\nOnly if they have no token: authenticate with email/password (fallback). Never put passwords or full tokens in chat when avoidable.\n“Connec","repository_url":null,"sources":[{"source_id":"smithery","url":"https://smithery.ai/servers/usama/reachowl","observed_at":"2026-10-17T21:40:22.481400+00:00","source_record_id":"1ef170b5-8f57-4d3b-9eff-de53b1f729a2","source_record_name":"usama/reachowl"}],"relevance_signals":["email"],"classification":{"label":"pending","method":"not-yet-classified"},"catalog_ids":[],"verification_status":"discovered","vendor_ownership":"not-verified","execution_tested":false,"pricing_status":"not-verified","documentation_status":"not-verified"}}