com.pulsemcp/gcs
com.pulsemcp/gcs
Is the com.pulsemcp/gcs MCP server down? No. It is up and needs env, probed 2026-10-31.
MCP server for Google Cloud Storage with fine-grained tool access control.
needs env probed 2026-11-14 · unchanged since 2026-10-31
MCP error -32000: Connection closed [WARN] config: Disabled tools filter active: mcpcost-placeholder [INFO] config: Bucket constraint active: mcpcost-placeholde
- Run it
- npx -y gcs-google-mcp-server@0.1.14 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/pulsemcp/mcp-servers
- Registry
- active, updated 2026-06-17 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- com.pulsemcp/appsignal · alive
- com.pulsemcp/dynamodb · alive
- com.pulsemcp/fetchpet · alive
- com.pulsemcp/fly-io · needs env
- com.pulsemcp/gmail · alive
- com.pulsemcp/good-eggs · alive
- com.pulsemcp/google-calendar · alive
- com.pulsemcp/google-docs · needs env
Servers that mention pulsemcp.
- com.pulsemcp/google-flights · alive
- com.pulsemcp/serpapi-hotels · alive
- com.pulsemcp/twist · alive
- com.pulsemcp/pulse-fetch · needs network
- com.pulsemcp/svg-tracer · alive
- com.pulsemcp.servers/pulse-fetch · needs network
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 exits because an environment variable is missing. The probe starts the package without secrets. A server that starts without secrets and asks for them on the first tool call is measured.