Other · Local MCP server
Verified Googledocs MCP
MCP server for Google Docs with verified writes - every mutation returns before/after proof.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.michaelrobertsutton/verified-googledocs-mcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2026-06-16
- Updated
- 2026-06-16
- Publisher
- michaelrobertsutton (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/michaelrobertsutton) · how
- Listed under
- Google Docs MCP servers
- Repository
- github.com/michaelrobertsutton/verified-googledocs-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPIruntime: uvx | verified-googledocs-mcp | 0.1.0 | stdio |
How to connect Verified Googledocs MCP
Verified Googledocs MCP runs locally from a Python package published to PyPI: verified-googledocs-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx verified-googledocs-mcp. It reads these environment variables: VERIFIED_GOOGLEDOCS_MCP_CREDENTIALS and VERIFIED_GOOGLEDOCS_MCP_AUDIT_EXCERPTS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"verified-googledocs-mcp": {
"command": "uvx",
"args": [
"verified-googledocs-mcp"
],
"env": {
"VERIFIED_GOOGLEDOCS_MCP_CREDENTIALS": "<value>",
"VERIFIED_GOOGLEDOCS_MCP_AUDIT_EXCERPTS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| VeridictKnow if you can trust your MCP server. Trust judgment for AI agents. | Local · stdio |
| VerifiGet a real human to verify, decide, or improve an AI agent's work. Pay per review via x402 on Base. | Remote · HTTPLive check: ✓ handshake |
| Verificar CURPValida, coteja y verifica CURPs mexicanas en el registro de RENAPO. | Local · stdio |
| Verified FeedContradiction-verified, freshness-SLA'd signed feed: per-record status + as-of date + receipt. | Remote · HTTPLive check: ✓ handshake |
| Verified WagesCurrent source-cited US minimum wage, tipped wage, and FLSA constants for AI agents; cites DOL. | Remote · HTTPLive check: sign-in required |
| VerifiedDRWebsite authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships. | Remote · HTTPLive check: sign-in required |
| VerifierMCP tool observatory: do registry servers answer, and are their answers true? No key. | Remote · HTTPLive check: ✓ handshake |
| VerifiMind PEAS - RefleXion TrinityX-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.64. | Remote · HTTPLive check: ✓ handshake |