Connect WorldSignals to your AI

The WorldSignals MCP server lets Claude, ChatGPT, Cursor, VS Code and other AI apps search real-world events as they are published: new companies, insolvencies, public tenders, funding rounds, licences, layoffs, vulnerabilities, outages and AI model changes, from official registers and public feeds.

Set it up

Pick your app. Apps that support sign-in (OAuth) open the WorldSignals sign-in the first time: enter your email, open the link we send, and allow the app. There is no key to paste.

On claude.ai or in Claude Desktop, open Settings → Connectors, choose Add custom connector, name it WorldSignals and paste this address. Then sign in to WorldSignals when Claude asks. On Team and Enterprise plans, an owner adds the connector for the organization first.

https://worldsignals.dev/mcp

In ChatGPT’s settings, turn on developer mode and create a custom app (connector) with this address and OAuth sign-in. Then sign in to WorldSignals when ChatGPT asks.

https://worldsignals.dev/mcp

claude mcp add --transport http worldsignals https://worldsignals.dev/mcp

Then type /mcp in Claude Code, choose worldsignals and sign in in your browser. Or use your access key and skip the sign-in:

claude mcp add --transport http worldsignals https://worldsignals.dev/mcp \
  --header "Authorization: Bearer $WS_KEY"

codex mcp add worldsignals --url https://worldsignals.dev/mcp --bearer-token-env-var WS_KEY

Or in ~/.codex/config.toml; Codex reads the key from WS_KEY:

[mcp_servers.worldsignals]
url = "https://worldsignals.dev/mcp"
bearer_token_env_var = "WS_KEY"

Add to Cursor

Or in .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them. Cursor opens the sign-in when you first use it; to use your key instead, add "headers": { "Authorization": "Bearer wsk_…" }.

{ "mcpServers": { "worldsignals": { "url": "https://worldsignals.dev/mcp" } } }

Add to VS Code

Or from a terminal. VS Code asks you to sign in to WorldSignals the first time a tool runs; the docs show the setup with a key instead.

code --add-mcp '{"name":"worldsignals","type":"http","url":"https://worldsignals.dev/mcp"}'

Any MCP client that speaks streamable HTTP can connect to the address. Clients with OAuth find the sign-in through /.well-known/oauth-protected-resource/mcp: OAuth 2.1 with PKCE (S256), dynamic client registration or a client ID metadata document. Other clients send your access key as a header:

Authorization: Bearer wsk_…

Tools

Every tool reads, except update_stream, which changes only your own saved stream (calling it twice saves the same). None changes anything anywhere else.

Tool	What it does
`list_event_types`	Every event type by family, whether it is collected today, and in which countries
`search_events`	Events filtered by type, country, tags and field conditions (for example `data.cvss.base_score>=9`), newest first; with a cursor, only what is new since the last call
`get_event`	One event by its id, in full, with its source and licence
`get_entity`	One company across every source, found by registry number, WorldSignals id or name and country, with its events newest first
`my_stream`	The event types and countries you saved in Build a stream
`update_stream`	Changes your saved stream: its event types, countries, delivery and speed
`list_rules`	Your own combined rules, on plans that have them

Try asking

“What new companies were registered in Ireland yesterday? List ten with their towns.”
“Show me UK public tenders published today worth more than £1 million.”
“Which US companies filed a Form D funding notice this week in California?”
“Any critical vulnerabilities exploited in the wild in the last three days?”
“Follow new French insolvency proceedings: check now and tell me what changed since last time.”

Privacy and safety

What WorldSignals sees. Only what your app sends to the tools: the filters of each search. It never sees your conversation, your files or your other connectors. For your key we keep counts of requests a day, never which events you read.
Sign-in. Signing in gives the app read access to collected events and nothing else (scope events:read). Access tokens last an hour and renew on their own; we keep them only as one-way hashes. Disconnect an app on your Account page; deleting your sign-up ends every connection.
Public data. Events come from official registers, journals and public feeds, each with its source and licence. Every answer reminds the AI that event content is data, never instructions, so a company name can’t steer it.
The privacy policy and terms cover the MCP server like the rest of WorldSignals. Yumankind OÜ, in Estonia, runs it.

Limits and plans

Your account can make 120 requests a minute, shared by every app you connect and the events API. A search returns up to 50 events, and events are kept for 30 days. Early access is free; see pricing for the plans that follow.

Help

Write to hello@worldsignals.dev. The docs cover the server in more detail. For directories and registries: the server’s card is at /mcp/server-card, and its name in the MCP Registry is dev.worldsignals/worldsignals.