WorldSignals

dev.worldsignalsPublished by worldsignals.devOfficial publisherv1.0.1Updated Oct 29, 2026

Real-world events for agents: new companies, insolvencies, tenders, funding, layoffs, outages, CVEs.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint that gives assistants real-world business and technology event signals such as new companies, insolvencies, tenders, funding, layoffs…

What you can do
  • The manifest lists no individual tools, so capabilities are known only from the provider's description.
  • It is described as supplying real-world events to agents, covering company formation, insolvency, tenders, funding rounds, layoffs, outages and CVEs.
  • Assistants would use it to bring current external event data into answers and workflows rather than relying on model knowledge alone.
When to use it
Useful when an assistant needs up-to-date external signals about companies, markets or technology incidents, for example monitoring business changes or security advisories alongside other work.
Requirements
A remote streamable HTTP endpoint at worldsignals.dev; no local package or runtime is needed. OAuth authentication is required, so the user must sign in or authorize access with the provider. No environment variables or headers are declared.
Before you install
Access requires OAuth authorization to a third-party service, so review what account data and scopes are granted. The server is hosted remotely, meaning queries and results pass through the provider. No tool list is published, so verify what actions it exposes before relying on it.

Installation

In SourceWeft

  1. Open WorldSignals in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/dev.worldsignals%2Fworldsignals/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 29, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.