
CDT Express by Riskthinking.AI
io.github.RiskThinkingPublished by GitHub account RiskThinkingv0.7.0Updated Oct 29, 2026
Interact with climate metrics via Riskthinking.AI's CDT Express API in supported AI chat experiences
Overview
Connects an AI assistant to Riskthinking.AI's CDT Express climate risk data, covering hazards, assets, companies and market climate metrics.
- What you can do
- Look up climate exposure and impact metrics and the metric glossary
- Query hazard distributions for a location, scenario and year
- Find physical assets and companies and retrieve their climate risk scores
- Read market climate risk indexes
- All 40 tools are read-only; results depend on the account's permissions and quota
- When to use it
- Useful when you want an assistant to answer questions about physical climate risk — heat or other hazard exposure at coordinates, a company's climate risk scores under a scenario such as ssp245, or the meaning of metrics like dcr_score and cvar_95 — using Riskthinking.AI data instead of general knowledge.
- Requirements
- A VELO account with CDT Express access. Remote option: add the hosted Streamable HTTP endpoint and sign in with OAuth (automatic client registration; leave manual client ID, secret and API key empty). Local option: install the MCPB extension in Claude Desktop and enter a CDT Express API key from VELO. Internet access is needed either way; workspace admins may have to allow custom connectors.
Installation
In SourceWeft
- Open CDT Express by Riskthinking.AI in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.RiskThinking%2Fcdt-express-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"cdt-express-by-riskthinking-ai": {
"type": "http",
"url": "https://mcp.riskthinking.ai/mcp"
}
}
}README
CDT Express MCP
Explore climate hazards, physical assets, companies, and market climate risk with Riskthinking.AI data in your AI app.
Connect by URL (recommended)
Use the hosted Streamable HTTP server. You need a VELO account with CDT Express access.
- Add a custom MCP connection in your AI app. Name it CDT Express and paste the URL above. If asked for a transport, choose Streamable HTTP.
- Connect with OAuth. Sign in to VELO and approve access. Keep automatic client registration or the client's published identity selected; leave manual client ID, client secret, and API key fields empty.
- Enable CDT Express in your conversation and try a prompt below.
Where to add the connection:
Custom connections depend on your app and workspace permissions. A workspace administrator may need to add or allow the connection first. No local server installation or API key is needed for the remote connection.
Try it
- “Explain dcr_score and cvar_95 using the CDT Express metric glossary.”
- “Show extreme-heat exposure for Toronto at latitude 43.6532, longitude -79.3832, under ssp245 in 2050.”
- “Find Microsoft in CDT Express and retrieve its climate risk scores for ssp245 in 2050.”
The 40 read-only tools cover climate exposure and impact metrics, hazard distributions, assets, companies, and market indexes. Available data depends on your account permissions; API calls may consume your quota. Use narrower filters or ask for a small sample when exploring large datasets.
Local Claude Desktop extension (MCPB)
The MCPB runs the connector on your computer and uses your CDT Express API key. It still needs an internet connection to retrieve data.
- Install Claude Desktop and
download the latest
cdt-express.mcpb. - Open Settings → Desktop app, select Manage next to Extensions, then Advanced settings → Install Extension and choose the file. Older Claude versions show Settings → Extensions → Advanced settings.
- Enter your API key from VELO, finish installation, and enable the extension's tools in your conversation.
To update, install the newer MCPB and choose Update. See Claude's extension guide if the settings differ in your version.
Need help?
- Can't add a connection? Check that your app and workspace allow custom MCP servers. Use the setup guide for your client above.
- Sign-in expired or access stopped? Disconnect and reconnect to authorize again. For local MCPB, check the API key in the extension settings.
- Permission or quota error? Check your CDT Express access and usage in VELO.
- Large response or timeout? Narrow the filters or request fewer results.
Report an issue with your client, tool name, and error message. Remove API keys, tokens, authorization URLs, and private data before sharing. More detailed checks are in the client testing guide.
Privacy
Read RiskThinking.ai’s Privacy Policy.
Tool inputs, such as coordinates and company searches, are sent to the CDT Express API; results return to your AI app. The connector does not request your whole conversation. Remote authorization uses VELO; the local extension uses the API key you configure in Claude. Your AI app and connected services apply their respective data-handling policies.
For developers
See development and releases, hosting configuration, and OAuth state management. This project is MIT licensed.
Source: README.md at commit 9795061
Tools
0Version history
2- v0.7.0LatestOct 29, 2026
- v0.6.0Sep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts