Google Business Profile Verifications integrationGoogle Business Profile Verifications logo

Google Business Profile Verifications integration for AI agents.

Google Business Profile Verifications integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Google Business Profile Verifications tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

What your agents can do

Real Google Business Profile Verifications actions, managed and audited.

Your user connects Google Business Profile Verifications once; your agent can then fetch verification options, start and complete location verification, and inspect voice-of-merchant state — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

  1. 1

    Your user grants Google Business Profile Verifications access once (OAuth) — the token lands in the vault.

  2. 2

    Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.

  3. 3

    Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Google Business Profile Verifications tools.

6 tools are generated from the published Google Business Profile Verifications catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 6 tools. All published catalog entries are included in this page's server-rendered HTML.

Mybusinessverifications Locations FetchVerificationOptions
Reports all eligible verification options for a location in a specific language.
locations
Mybusinessverifications Locations GetVoiceOfMerchantState
Gets the VoiceOfMerchant state.
locations
Mybusinessverifications Locations Verifications Complete
Completes a `PENDING` verification. It is only necessary for non `AUTO` verification methods. `AUTO` verification request is instantly `VERIFIED` upon creation.
locations
Mybusinessverifications Locations Verifications List
List verifications of a location, ordered by create time.
locations
Mybusinessverifications Locations Verify
Starts the verification process for a location.
locations
Mybusinessverifications VerificationTokens Generate
Generate a token for the provided location data to verify the location.
verificationtokens
FAQ

Google Business Profile Verifications integration, answered

How do AI agents use Google Business Profile Verifications through Open Connector?
Your user connects Google Business Profile Verifications once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Google Business Profile Verifications tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Google Business Profile Verifications MCP server?
Yes. Open Connector can serve Google Business Profile Verifications as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Google Business Profile Verifications actions with credentials injected server-side.
Where do Google Business Profile Verifications credentials live?
In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Google Business Profile Verifications — keep the keys.

Open source, self-hostable, with Google Business Profile Verifications credentials that never leave your infrastructure. Run it from source today.