Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Situation

REMOTE · SITUATION.DIVIDENDSOLO.COM

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

+3 this week 67 Trust /100

Last scanned (18 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category News and Social

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 541 tokens (~77/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 62

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://situation.dividendsolo.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dividendsolo.com CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 36b7d880970df4b20eb9ed1d6d4b03a6
SANs: dividendsolo.com, *.dividendsolo.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of situation.dividendsolo.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
dividendsolo.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'nonce-ZjE3ZDE5NjUtY2M1YS00ODE2LTljNDAtOTU0ZTNmZThhN2Ez' https://datafa.st https://www.youtube.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://tiles.openfreemap.org https://elevation-tiles-prod.s3.amazonaws.com; font-src 'self'; connect-src 'self' https://datafa.st https://tiles.openfreemap.org https://elevation-tiles-prod.s3.amazonaws.com; worker-src 'self' blob:; frame-src 'self' https://www.youtube-nocookie.com https://www.youtube.com https://www.vesselfinder.com https://globe.adsbexchange.com https://gpsjam.org; media-src 'self' blob:
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://situation.dividendsolo.com/mcp Verified 200
http (plaintext) http://situation.dividendsolo.com/mcp HTTPS enforced 301 https://situation.dividendsolo.com/mcp
MCP tools · 7 exposed · ~459 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_data ~50

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

NameTypeReqDescription
slugstringyesthe series: wire-volume, hormuz-air-traffic or roster-members

No output schema declared.

No examples provided.

get_live ~77

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.

NameTypeReqDescription
confirmPaymentSpendboolean–true opens the Polar checkout for the plan and answers its link
planstring–which plan, monthly when left out

No output schema declared.

No examples provided.

get_map_events ~95

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.

NameTypeReqDescription
sincestring–an ISO time, for example 2026-11-09T12:00:00Z; the last 24 hours when left out
situationstring–a situation key from list_situations; every situation when left out

No output schema declared.

No examples provided.

get_stories ~60

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.

NameTypeReqDescription
situationstring–a situation key from list_situations; every situation when left out

No output schema declared.

No examples provided.

get_wire ~67

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

NameTypeReqDescription
limitinteger–how many lines per situation, 20 by default
situationstring–a situation key from list_situations; every situation when left out

No output schema declared.

No examples provided.

list_situations ~48

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

subscribe_daily ~62

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.

NameTypeReqDescription
emailstringyesthe reader's email address

No output schema declared.

No examples provided.

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.

remote · situation.dividendsolo.com

# add to Claude Code
claude mcp add --transport http com-dividendsolo-situation-situation 'https://situation.dividendsolo.com/mcp'
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.