One URL. Nothing to install.
Give your assistant read access to the RWA Leads intelligence feed — the same scored RWA, tokenization and family-office signals that go out in the digest. It is a standard Model Context Protocol server, so the URL below works in Claude, ChatGPT, Cursor, Codex and any other client that supports remote MCP servers.
Run a real search against the live feed — the top Swiss signals, exactly as your assistant would receive them.
https://rwaleads.com/api/mcp- 01
Open your assistant's connector settings
Claude → Settings → Connectors → Add custom connector. ChatGPT → Settings → Apps & Connectors (developer mode, paid plans). Cursor → Settings → MCP → Add server. Claude Code, Cursor and Codex: use the config snippets below.
- 02
Paste the RWA Leads URL
Name it RWA Leads and save. With no key you get the preview: the top 5 matches per search. On the USD 19/month plan, create a key under Account → API keys and paste the URL with ?key=your-key on the end for the full feed.
- 03
Ask it a research question
"Which Swiss signals scored hot in the last 30 days?" "Find tokenization-interest signals in the EU and brief me on the top one." Plain language in, sourced answers out.
For clients that read an mcp.json file (Cursor and others):
{
"mcpServers": {
"rwa-leads": {
"url": "https://rwaleads.com/api/mcp"
}
}
}Claude Code, one line:
claude mcp add --transport http rwa-leads https://rwaleads.com/api/mcp
Codex, in ~/.codex/config.toml:
[mcp_servers.rwa-leads] url = "https://rwaleads.com/api/mcp"
- search_signals
- Search the scored feed. Filters: free text (q), type, region (CH, EU, UK, US, APAC, MENA, Global), tier (hot / warm / watch / cold), min_score, since_days. Sort by intent or recency.
- get_signal_brief
- One signal in full: the factor-by-factor score breakdown, the entity, and the source URL to cite.
| Read-only | A connected assistant can search and read signals. It cannot write, trade or change anything. |
| Observations, not advice | We never make a recommendation. Every signal links to its public source so you can check it. |
| Scored nightly | The feed is ingested and re-scored once a day. It is not a real-time market data stream. |
| Fair-use limit | 60 requests per 10 seconds. More than any assistant needs; enough to stop a runaway loop. |
Developers: the codebase also carries a simulated paper trade desk for testing agents against a cap-check and an audit trail. It needs an account bearer, which this hosted endpoint does not issue, so connected assistants never see it. No venue is wired and no money moves.