Skip to main content

​
Authentication is Optional

Most tools on the Venturu MCP server work without authentication. You can search businesses, browse brokers, and retrieve details without logging in. Authentication is only required for tools that take action on behalf of a user:

​
How It Works

The Venturu MCP server implements the OAuth 2.0 Authorization Code flow with PKCE (Proof Key for Code Exchange), the standard for MCP authentication. Most MCP clients handle this flow automatically — you just approve the connection.

​
What Happens in Practice

  1. You trigger an authenticated tool — e.g., ask the AI to contact a broker
  2. Your MCP client opens a browser window to the Venturu consent screen
  3. You approve the connection with your Venturu account
  4. The client receives tokens and can make authenticated requests
  5. Tokens refresh automatically — you won’t need to log in again

​
OAuth Endpoints

For client developers building MCP integrations, here are the standard discovery endpoints:

​
Scopes

​
Token Lifetimes

Access tokens are encrypted JWE tokens. When an access token expires, compliant MCP clients will automatically use the refresh token to obtain a new one without requiring you to log in again.

​
Dynamic Client Registration

The Venturu MCP server supports RFC 7591 Dynamic Client Registration. MCP clients can register themselves automatically without manual configuration. This means:
  • No need to pre-register your application
  • No client secrets to manage
  • The client receives a client_id on first connection
If your MCP client supports the standard OAuth 2.0 discovery flow (via .well-known/oauth-authorization-server), authentication will work out of the box with no manual configuration.

​
Troubleshooting

You’re calling a contact tool without being authenticated. Your MCP client should prompt you to log in — check for a browser popup or notification. If not, reconnect to the server and try again.
Some MCP clients may not support OAuth flows yet. Check your client’s MCP documentation for authentication support. You can still use all read-only tools without authentication.
Access tokens last 1 hour. Your MCP client should automatically refresh them. If you’re seeing auth errors after a long session, try disconnecting and reconnecting to the server.