Niches · Cloud & infrastructure

Inspect live resources and debug a failure

Two or three companies' docs show a full fit.

2companies, full fit
6companies, fit with a limit
12companies carry the tag
26share of the category's work
9first-hand accounts

What counts as done

The resources and state the question needs, read with read-only calls, in structured output with paging, with no secrets in the response unless asked for, and a written finding.

How agents ask for it: why did the deploy fail, what is running in this account, check the status of this service, show the routing and security groups

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
AWS MCP Servers C
Amazon Web Services, Inc.
call_aws runs AWS CLI reads with JSON output, READ_OPERATIONS_ONLY=true checks each command against known read operations, and IAM scopes what is reachable; the flag is off by default. source
Azure MCP Server BB
Microsoft Corporation
--read-only removes write operations and --namespace limits the tools; resource graph, Monitor and per-service list and get tools read resources under the caller's RBAC. source

Does the job, with a limit 7

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Cloudflare CLI (cf) B
Cloudflare, Inc.
Results are JSON on stdout and errors on stderr, but lists return one page with paging options varying by command and no paging metadata, and there is no read-only mode beyond the token's permissions. source
Cloudflare MCP Servers BB
Cloudflare, Inc.
search and execute return valid JSON capped at about 6,000 tokens with --- TRUNCATED --- markers, under a token or minimal OAuth scopes; but there's no read-only switch, and domain-server list tools return [object Object] (#468, open). source
DigitalOcean MCP Server B
DigitalOcean, LLC
Per-service endpoints and --services keep the tool list small, but there is no read-only mode (#273, open), and db-cluster-list and db-cluster-get return database passwords in plaintext (#372, open). source
Netlify API + MCP BB
Netlify, Inc.
Lists are JSON with page, per_page and Link-header paging, but tokens have no scopes or read-only form, so a read-only session reaches every team its owner belongs to. source
Railway MCP Server C
Railway Corporation
The local server's list_, environment_status, get_logs and service_metrics tools read state, but there is no read-only grant, and on the hosted server logs go through the natural-language railway-agent. source
Render MCP Server B
Render Services, Inc.
Logs, metrics, deploy history and read-only SQL are available, but there is no read-only mode (#5, open), an API key reaches every workspace, and the docs say sensitive data may still be exposed. source
Terraform MCP Server BB
HashiCorp, Inc. (an IBM Company)
list_workspaces, get_run_details, list_state_versions and get_token_permissions read HCP Terraform state, and --toolsets narrows tools; but this covers only Terraform-managed state, and some writes run without ENABLE_TF_OPERATIONS. source

Doesn't do this job 1

Listings in the category that do something else, with the reason.

ListingWhy
neckbeard B
David Beale (individual, GitHub account bealesh)
No reads of live cloud resources. source

What stops agents finishing

  • no read-only mode, so a read-only session needs a separately scoped key
  • list output loses paging metadata or arrives as unparsed text
  • tool list or one list call fills the context

Around it

Before: observability.investigate-alert. After: infrastructure.change-live-resources, code.open-pr.

Where this comes from

Weight 26 of 100 in Cloud & infrastructure: 9 of 32 accounts; the people who report it working ran the AWS CLI under a read-only credential rather than an MCP listing

The same as data: /api/v1/use-cases/infrastructure.inspect-debug.json, or the MCP tool get_use_case with id infrastructure.inspect-debug. Other jobs in this category: /api/v1/niches?category=infrastructure.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.