$NOS — A read-only MCP setup would make AI agent integration safer to adopt

I compared three sections of Nosana's public documentation: MCP Server, Permissions (Scopes), and Connect with Nosana.

One detail stood out.

The MCP quick-start shows how to connect Codex and Claude to manage GPU deployments. However, the same connection can expose tools that create, stop, or scale deployments, potentially spending credits.

The Permissions documentation already separates deployments:read from deployments:write and warns that wallet:sign deserves special care. The Connect SDK also supports requesting fewer scopes.

The gap: I couldn't find an MCP quick-start example showing how to connect an assistant only for monitoring jobs, deployments, and credit balances.

For developers using autonomous agents, the difference between observing a workload and modifying a paid workload matters.

My suggestion: Add a read-only MCP onboarding example using credits:read, jobs:read, and deployments:read. Include the expected OAuth consent permissions and explain how users can enable write access later.

$NOS — A read-only MCP setup would make AI agent integration safer to adopt.
Question: Can the hosted MCP OAuth flow currently request only these read scopes? If yes, could the team document the exact configuration for Codex or Claude?

This is based on a public documentation review, not a completed OAuth or GPU deployment test.

Sources:
https://learn.nosana.com/mcp/intro.html
https://learn.nosana.com/api/scopes.html
https://learn.nosana.com/connect/