com.locus-intelligence/reach
Reach (Google Business Profile)
Is the Reach (Google Business Profile) MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Hosted Google Business Profile MCP server: reviews, posts, profile edits, Maps rank. OAuth sign-in.
needs auth probed 2026-11-14 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"No authorization provided"}- Endpoint
- https://reach.locus-intelligence.com/api/mcp (streamable-http)
- Host
- reach.locus-intelligence.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://reach.locus-intelligence.com/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server reach.locus-intelligence.com, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://reach.locus-intelligence.com/google-business-profile-mcp
- Registry
- active, updated 2026-10-19 · registry entry
Compare this server with others.
More servers
Servers that mention reach.
- Getlead ad.getle/leads · alive
- Inside Ads ad.inside/inside-ads · alive
- BAMF.ai ai.bamf/bamf · not MCP
- ai.enginy/mcp · needs auth
- Fine Structure ai.finestructure/fine-structure · alive
- MentionAgent ai.mentionagent/mentionagent · needs auth
- Onsa ai.onsa/onsa · alive
- ai.openhelm/email-outreach · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.