Bragproof

← Reports

@aashari/mcp-server-aws-sso

Starts with no setup4.0.0npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: nothing

5tools listed
0hosts contacted
1file written
0.3 sto start
137dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @aashari/mcp-server-aws-sso@4.0.0

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.

aws_sso_statusNo usable answer replied, but asks for setup: # AWS SSO: Authentication Required You need to authenticate with AWS SSO before using this command. ## How to Authenticate Run th

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

4 tools with commands in capitals or very long text
  • Gives the agent orders in aws_sso_login: token 5. The cached token is used by other AWS SSO tools **IMPORTANT FOR AI ASSISTANTS**: When the tool returns authentication instructions: - ALWAYS check if a browser
  • Gives the agent orders in aws_sso_ls_accounts: lly - Caches account and role information Prerequisites: - MUST first authenticate using `aws_sso_login` - AWS SSO must be configured with a start URL and region
  • Gives the agent orders in aws_sso_exec_command: aches credentials for future use (1 hour) Prerequisites: - MUST first authenticate using `aws_sso_login` - AWS CLI MUST be installed on the system - AWS SSO must b
  • Gives the agent orders in aws_sso_ec2_exec_command: ired. Uses SSM's RunShellScript document. Prerequisites: - MUST first authenticate using `aws_sso_login` - EC2 instance MUST have SSM Agent installed - Instance ne

Common and usually harmless: it is how many makers stress how a tool should be used.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

aws_sso_login launchBrowser
Initiate AWS SSO device authorization flow to obtain temporary credentials.

This flow works as follows:
1. Generates a unique user verification code and authentication URL
2. Opens a browser to AWS SSO login page (if `launchBrowser: true`)
3. You enter the verification code and complete AWS SSO login
4. Background polling automatically collects and caches the token
5. The cached token is used by other AWS SSO tools

**IMPORTANT FOR AI ASSISTANTS**: When the tool returns authentication instructions:
- ALWAYS check if a browser window opened automatically
- If browser opened: Guide the user to complete authentication
- If no browser opened: Instruct user to manually open the URL and enter code
- Always provide both the verification code and URL as backup

Prerequisites:
- AWS SSO must be configured with a start URL and region
- Browser access is required for authentication
- You must have an AWS SSO account with appropriate permissions

Returns: Authentication status, session details, verification code and URL
aws_sso_status
Check current AWS SSO authentication status.

Verifies if a valid cached token exists and its expiration time. Does NOT perform authentication - only checks status. If no valid token exists, instructs you to run `aws_sso_login`.

Use before calling `aws_sso_ls_accounts` or `aws_sso_exec_command`.

Returns: Authentication status, session details, expiration time, next steps
aws_sso_ls_accounts
List all AWS accounts and roles accessible through AWS SSO.

Provides essential information needed for `aws_sso_exec_command`:
- Fetches all accessible accounts with IDs, names, and emails
- Retrieves all available roles for each account
- Handles pagination internally
- Caches account and role information

Prerequisites:
- MUST first authenticate using `aws_sso_login`
- AWS SSO must be configured with a start URL and region

Returns: Account list with IDs, names, roles, and session status
aws_sso_exec_command accountId, roleName, region, command
Execute AWS CLI command using temporary credentials from AWS SSO.

Workflow:
1. Verifies valid AWS SSO authentication token
2. Obtains temporary credentials for account and role
3. Executes the AWS CLI command
4. Caches credentials for future use (1 hour)

Prerequisites:
- MUST first authenticate using `aws_sso_login`
- AWS CLI MUST be installed on the system
- AWS SSO must be configured

Required: `accountId`, `roleName`, `command`
Optional: `region`

Returns: Execution context, command output, errors, exit code
aws_sso_ec2_exec_command instanceId, accountId, roleName, region, command
Execute shell command on EC2 instance via SSM using AWS SSO credentials.

No SSH access or inbound ports required. Uses SSM's RunShellScript document.

Prerequisites:
- MUST first authenticate using `aws_sso_login`
- EC2 instance MUST have SSM Agent installed
- Instance needs IAM role with AmazonSSMManagedInstanceCore policy
- Your role needs `ssm:SendCommand` and `ssm:GetCommandInvocation` permissions

Required: `instanceId`, `accountId`, `roleName`, `command`
Optional: `region`

Returns: Execution context, command output, errors, troubleshooting guidance

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Files it wrote

Paths inside its sandbox, where its home folder is /tmp and its own folder cannot be written to.

Install facts

LicenseISC
Needsnode >=18.0.0
Sourcegithub.com/aashari/mcp-server-aws-sso
Install scripts@aashari/mcp-server-aws-sso declare them. This runner does not run them.
Tarballsha512-5pHEtSV7MGKZ636X4ZRAaIQNjCvM5oznFah/L/DybcSZXiKbEfX/iHnJQdd60LyaRv/d0F3boq1/4bAWuDgfAQ==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@aashari/mcp-server-aws-sso.svg)](https://bragproof.smaverk.com/r/%40aashari/mcp-server-aws-sso)

New version out? Ask for a fresh report.