From Claude
- Use the GST tools inside Claude on the web or Claude Desktop
- One key to paste at the consent page. No code, no config files
- Works for 72 hours, then the connector simply stops
Try the GST MCP server for 3 days
- Tools
- The sixteen diligence, portfolio and regulatory tools, the reference library and regulation resources, and every gst_ prompt. Radar tools and feeds are excluded.
- Ceilings
- 15 calls per minute, 100 per day. Non-contractual capacity limits, not an SLA.
- After 72 hours
- The credentials stop authenticating. Nothing is charged and nothing renews. One trial per network. Signing up again replaces the previous credentials.
From code
- For a script, pipeline or agent framework
- OAuth 2.1 client_credentials: exchange the pair for an hourly bearer token
The secret is shown onceAfter you click, the trial key appears on this page a single time. It cannot be retrieved later. You will need to copy or download it before leaving.After you click, the client secret appears on this page a single time. It cannot be retrieved later. You will need to copy or download it before leaving.
Verifying your browserUsually under a second. Please keep this page open.
Your previous secret has stopped working
The secret is shown onceThis is the only time the trial key will be displayed. Copy it or download the file before you leave this page. If it is lost, the only option is to sign up again, which replaces it.This is the only time the client secret will be displayed. Copy it or download the file before you leave this page. If it is lost, the only option is to sign up again, which replaces it.
Trial credentials
Your client ID and secret joined by a colon, exactly as the consent page expects it. Treat it like a password. GST does not store it in recoverable form.
Treat it like a password. It is not stored by GST in recoverable form.
Use it from Claude
Follow the GST MCP connector guide. It walks through adding the custom connector in Claude on the web or Claude Desktop; when the consent page asks for your key, paste the trial key shown above. Keep this tab open until the key is saved.
The connection ends with the trialThe approval you give at the consent page lasts exactly as long as the trial, even if you approve on the last day. Radar tools are refused for trial connections. When the trial ends the connector stops authenticating; remove it from Claude.
Endpoint https://mcp.globalstrategic.tech/mcp. Once the trial ends, approving at the consent page fails and the key is refused.
Use it from a script or pipeline
This is a machine-to-machine credential (OAuth 2.1 client_credentials) for code you run: a script, a pipeline, an agent framework. It does not work in the connector settings of Claude, Cursor or ChatGPT. The two commands below are prefilled with your pair; the full guide covers the token's one-hour life, the SDK provider that handles it, and the trial's ceilings.
Exchange the pair for a bearer token
POST both values to /token. The response carries an mcp_m2m_ access token valid for one hour.
Call the server with the token
Send it as Authorization: Bearer on every request to /mcp. Below, a tools/list call as a smoke test.
The token expires every hourThere is no refresh token. When a call returns 401, repeat step 01 and continue; a 401 on step 01 itself means the trial has ended. Keep the client ID and secret in your secret store, not the token. Details in the guide.
Endpoint https://mcp.globalstrategic.tech/mcp. Once the trial ends, the token exchange and every call return 401. Delete the pair from your secret store.
The invisible bot check did not pass. This happens with some privacy extensions and VPNs. Retrying usually works; if not, try another browser.This network has hit the sign-up limit. Wait a moment and try again. No credentials were issued.This is on our side, not yours. Nothing was issued. Try again in a minute; if it persists, check the status page.