Google Oauth Credential Service MCP Server

by getvda Your server? Claim it

answering

Google Oauth Credential Service is answering right now. Last checked 11 min ago. It exposes 2 tools.

Google OAuth Credential Service

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

248 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Google Oauth Credential Service every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add google-oauth-credential-service --transport http https://authenticated-llm-oauth-agent.getvda.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "google-oauth-credential-service": {
      "url": "https://authenticated-llm-oauth-agent.getvda.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.google-oauth-credential-service]
url = "https://authenticated-llm-oauth-agent.getvda.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "google-oauth-credential-service": {
      "url": "https://authenticated-llm-oauth-agent.getvda.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "google-oauth-credential-service": {
      "url": "https://authenticated-llm-oauth-agent.getvda.ai/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

invoke

invoke

Google-OAuth-gated LLM gateway: verify a Google ID token, then run a Gemini (Vertex AI) completion for the verified caller.

selftest

selftest

FREE, no payment required. Runs this agent's real capability on a fixed canned input and returns the genuine result, an honest assertion grade, and the full trust manifest (signed Agent Card, JWKS, governance/licence chain, safety posture) with a proof link for every claim. Intended for registries, graders and auditors: this is behavioural evidence, not a self-description.

Endpoints

URL	Transport	State	Latency	Checked
https://authenticated-llm-oauth-agent.getvda.ai/mcp	streamable-http	answering	170 ms	11 min ago

Alternatives to Google Oauth Credential Service

same job, measured the same way

Google Oauth Langchain Agent

by getvda

Google OAuth LangChain Agent

2 tools answering

Google Docs

by pulsemcp

MCP server for Google Docs integration with OAuth2 and service account support.

72 installs/wk local only

Google_docs

by pipeworx-io

Google Docs MCP Pack — read, create, and edit Google Docs via OAuth.

37 tools answering

SEO Tools: Google Search Console

by antohins

Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).

67 installs/wk local only

MCP Google Sheets Full

by moooonad

Full Google Sheets MCP: 26 tools + run_sheets_script escape hatch. User OAuth, no service account.

71 installs/wk local only

Google MCP

by matiasbattocchia

Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.

answering

Google Trends MCP

by den-indance

Google Trends MCP with proxy rotation, auto-retry on Google blocks, residential-proxy setup.

34 installs/wk local only

Meet Live Assist

by krystiangw

Your own agent inside a live Google Meet or Zoom call. Local-first, no hosted service.

29 installs/wk local only

Google Oauth Credential Service — questions

Answers built from our own checks of this server.

What can Google Oauth Credential Service do?

It exposes 2 tools, read directly from the server on our last check. Among them: invoke, selftest. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Google Oauth Credential Service working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 248 ms. The bar chart above shows every period we have measured.

How do I connect Google Oauth Credential Service?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Google Oauth Credential Service need an API key?

No. Google Oauth Credential Service completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Google Oauth Credential Service?

It answers our handshake in 248 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.