Quip MCP Integration Error: Token Verification Failed with Status 400

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.3.2 (24D81)

### Expected behaviour

The Quip MCP integration should successfully authenticate using the environment variable QUIP_API_TOKEN and allow operations like searching Quip documents.

### Actual behaviour

When attempting to use the Quip MCP integration tools (specifically amazon_internal_mcp_server___search_quip), the system returns an error: "Token verification failed: Token verification failed with status 400". This happens despite having a valid Quip API token that works directly with the Quip API.

```
[chat-transcript]
> can you retry a quip test

I'll retry a Quip test to see if your token is working. Let me try a different approach this time.
[Tool uses: execute_bash]

[Tool uses: amazon_internal_mcp_server___search_quip]

I'm still seeing an error with the Quip API token. Let me try a different approach to test your token.
[Tool uses: execute_bash]

Great news! Your new Quip API token is working correctly. I was able to successfully authenticate with the Quip API and retrieve your user information.

Here's what I found:
- Name: Chad Colby
- Email:
- User ID:
- The token has access to your Quip folders and account information

This confirms that your new Quip API token is valid and properly authenticated. The issue we encountered earlier with the Amazon Q MCP server's Quip integration might be specific to that integration, but the token itself is working fine with the Quip API directly.

I'll help you prepare a detailed bug report about the Quip MCP integration issue. Here's a structured report you can submit:
[Tool uses: report_issue]

(...truncated)
```

### Steps to reproduce

1. Set a valid Quip API token in the environment (export QUIP_API_TOKEN="token_value")
2. Verify the token works directly with the Quip API using curl
3. Attempt to use amazon_internal_mcp_server___search_quip or other Quip MCP functions
4. Observe the token verification error

### Environment

```yaml

[q-details]
version = "1.9.1"
hash = "5d2c2807cab9bc6c9dc5fcd05f92c7a979e8a4f7"
date = "2025-04-29T06:22:42.917989Z (11d ago)"
variant = "full"

[system-info]
os = "macOS 15.3.2 (24D81)"
chip = "Apple M1 Pro"
total-cores = 10
memory = "32.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "iTerm 2"
install-method = "unknown"

[env-vars]
PATH = '/Users/USER/.nvm/versions/node/v20.17.0/bin:/Users/USER/.toolbox/bin:/Users/USER/.rbenv/shims:/opt/homebrew/bin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Library/Apple/usr/bin:/Applications/iTerm.app/Contents/Resources/utilities:/Users/USER/.local/bin:/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/bin:/Users/USER/Library/Application\ Support/JetBrains/Toolbox/scripts:/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/bin:/Users/USER/Library/Application\ Support/JetBrains/Toolbox/scripts'
QTERM_SESSION_ID = "988b2bcc2ca04c5dab79bfaa7077a587"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.9.1"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.googlecode.iterm2"

[chat-settings]
interactive=true

[chat-trusted_tools]
amazon_internal_mcp_server___search_quip=true
execute_bash=true

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profiles=
default

global_context=
.amazonq/rules/**/*.md
README.md
AmazonQ.md

profile_context=none

files=none
```

Inizia riproducendo il malfunzionamento con q doctor, q restart, QUIP_API_TOKEN e amazon_internal_mcp_server___search_quip, quindi confrontalo con il controllo curl diretto riuscito di Quip API. Il lavoro è completato quando le Quip MCP tools eseguono l’autenticazione con un token valido e supportano operazioni come la ricerca di documenti Quip.

Scritto dal modello di indicizzazione a partire dal testo della issue.