# Situation (remote · situation.dividendsolo.com)

Live world situations for agents: the wire, the map's events and the stories behind them.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `situation.dividendsolo.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation.md), [page](https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation)

## Channel facts

- Endpoint: `https://situation.dividendsolo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 541 tokens (~77/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "subscribe_daily" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Situation MCP server?

Situation is a hosted endpoint at https://situation.dividendsolo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-dividendsolo-situation-situation 'https://situation.dividendsolo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-dividendsolo-situation-situation": {
      "url": "https://situation.dividendsolo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-dividendsolo-situation-situation": {
      "type": "http",
      "url": "https://situation.dividendsolo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-dividendsolo-situation-situation]
url = "https://situation.dividendsolo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dividendsolo-situation-situation": {
      "type": "remote",
      "url": "https://situation.dividendsolo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-dividendsolo-situation-situation --url 'https://situation.dividendsolo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-dividendsolo-situation-situation:
    url: "https://situation.dividendsolo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-dividendsolo-situation-situation": {
      "Transport": "http",
      "Url": "https://situation.dividendsolo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-dividendsolo-situation-situation -t streamable-http -u 'https://situation.dividendsolo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-dividendsolo-situation-situation": {
      "type": "http",
      "url": "https://situation.dividendsolo.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 62)

First indexed and scored.

## MCP tools (7)

### `list_situations` (~48 tokens)

List the situations

The situation keys and names Situation follows: Iran and the Strait of Hormuz, Ukraine and Russia, US Debt and Currency, the Plague Tracker, Weather, and AI and Hacking.

### `get_wire` (~67 tokens)

Read the wire

The newest lines on a situation's wire, newest first, each with its source and its source time.

Input parameters:

- `limit` (integer): how many lines per situation, 20 by default
- `situation` (string): a situation key from list_situations; every situation when left out

### `get_map_events` (~95 tokens)

Read the map's events

The events the map draws for a situation: the place, what kind of place it is, and the time of the line that named it.

Input parameters:

- `since` (string): an ISO time, for example 2026-11-09T12:00:00Z; the last 24 hours when left out
- `situation` (string): a situation key from list_situations; every situation when left out

### `get_stories` (~60 tokens)

Read the stories

The stories of the last 24 hours: what broke first, who broke it, how many lines it has and whether one source has it alone.

Input parameters:

- `situation` (string): a situation key from list_situations; every situation when left out

### `get_data` (~50 tokens)

Read a data series

One of the /data series as text: wire-volume, hormuz-air-traffic or roster-members.

Input parameters:

- `slug` (string, required): the series: wire-volume, hormuz-air-traffic or roster-members

### `subscribe_daily` (~62 tokens)

Subscribe to Situation Daily

Send the confirm email for Situation Daily to an address new to Situation. The subscription starts only when the reader clicks the link in it. A reader who already has an account turns Daily on in the account menu.

Input parameters:

- `email` (string, required): the reader's email address

### `get_live` (~77 tokens)

Live access and its price

Without confirmPaymentSpend this only answers the price: nothing is charged and nothing is opened. With confirmPaymentSpend: true it answers the Polar checkout link for that plan.

Input parameters:

- `confirmPaymentSpend` (boolean): true opens the Polar checkout for the plan and answers its link
- `plan` (string): which plan, monthly when left out

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 65
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 63
- 2026-11-12: 63
- 2026-11-11: 62

## Common questions

### What is the Situation MCP server?

Situation is an MCP server listed in the public MCP registry as com.dividendsolo.situation/situation. Live world situations for agents: the wire, the map's events and the stories behind them. This page covers its hosted endpoint (https://situation.dividendsolo.com/mcp).

### Is the Situation MCP server safe to use?

Situation scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Situation MCP server expose?

Situation exposes 7 tools: list_situations, get_wire, get_map_events, get_stories, get_data, and 2 more. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.

### Does the Situation MCP server require authentication?

No. We connected to Situation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Situation MCP server still maintained?

Situation is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Situation MCP server?

VerifyMCP ran 12 checks on Situation, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Situation: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://situation.dividendsolo.com/mcp
- Website: https://situation.dividendsolo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation.json
- HTML version of this page: https://verifymcp.io/servers/com-dividendsolo-situation-situation/situation
