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.

CULT+MATH Decision Briefs

REMOTE · CULTMATH.COM

Odds and forecasts on the numbers executives plan against, plus free studies and Decision Briefs.

Available components

+4 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

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 Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 22906 tokens (~322/item across 71 items; 71 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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
  • Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 71 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 72 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

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

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
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_standards” rewrote its description, which is the text the model reads security
    • New tool “get_framework” functional
    • New tool “list_frameworks” functional
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “run_college_athletics” functional
    • New tool “run_sports_business_benchmark” functional
    • “run_concentration_benchmark” reworded the description of “peers” cosmetic
    • “run_disclosure_check” reworded the description of “peers” cosmetic
    • “run_peer_benchmark” reworded the description of “metric” cosmetic
  • 18 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “list_standards” rewrote its description, which is the text the model reads security
    • Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
    • Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
    • Tool “run_angle_demand” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
    • Tool “run_channel_mix” rewrote its description, which is the text the model reads security
    • Tool “run_city_profile” rewrote its description, which is the text the model reads security
    • Tool “run_claim_check” rewrote its description, which is the text the model reads security
    • Tool “run_comment_themes” rewrote its description, which is the text the model reads security
    • Tool “run_concentration_benchmark” rewrote its description, which is the text the model reads security
    • Tool “run_contractor_revenue” rewrote its description, which is the text the model reads security
    • Tool “run_cost_squeeze” rewrote its description, which is the text the model reads security
    • Tool “run_customer_concentration” rewrote its description, which is the text the model reads security
    • Tool “run_deal_activity” rewrote its description, which is the text the model reads security
    • Tool “run_deal_comps” rewrote its description, which is the text the model reads security
    • Tool “run_demand_check” rewrote its description, which is the text the model reads security
    • Tool “run_demand_durability” rewrote its description, which is the text the model reads security
    • Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
    • Tool “run_effective_duty” rewrote its description, which is the text the model reads security
    • Tool “run_fad_check” rewrote its description, which is the text the model reads security
    • Tool “run_filing_trend” rewrote its description, which is the text the model reads security
    • Tool “run_launch_lift” rewrote its description, which is the text the model reads security
    • Tool “run_merger_review” rewrote its description, which is the text the model reads security
    • Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
    • Tool “run_premium_check” rewrote its description, which is the text the model reads security
    • Tool “run_private_raises” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
    • Tool “run_revenue_mix” rewrote its description, which is the text the model reads security
    • Tool “run_series_forecast” rewrote its description, which is the text the model reads security
    • Tool “run_share_of_search” rewrote its description, which is the text the model reads security
    • Tool “run_spend_trend” rewrote its description, which is the text the model reads security
    • Tool “run_tariff_clock” rewrote its description, which is the text the model reads security
    • Tool “run_threshold_odds” rewrote its description, which is the text the model reads security
    • Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
    • Tool “run_triangulation” rewrote its description, which is the text the model reads security
    • Tool “run_write_downs” rewrote its description, which is the text the model reads security
    • Schema quality: 285 → 324 ▼ functional
    • Tool coverage: 79% → 85% ▲ functional
    • New tool “run_ai_brand_check” functional
    • New tool “run_ai_readiness” functional
    • New tool “run_audience_map” functional
    • New tool “run_audience_size” functional
    • New tool “run_business_universe” functional
    • New tool “run_buyer_roles” functional
    • New tool “run_channel_benchmark” functional
    • New tool “run_device_clearances” functional
    • New tool “run_incentive_tracts” functional
    • New tool “run_news_pulse” functional
    • New tool “run_news_share_of_voice” functional
    • New tool “run_parcel_mix” functional
    • New tool “run_recall_watch” functional
    • New tool “run_search_vs_ai” functional
    • New tool “run_social_pulse” functional
    • New tool “run_social_share_of_voice” functional
    • New tool “run_topic_views” functional
    • New tool “run_trade_area” functional
    • New tool “run_trial_pipeline” functional
    • New tool “run_wallet_size” functional
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “run_tariff_clock” rewrote its description, which is the text the model reads security
    • Schema quality: 10623 → 13405 ▼ functional
    • New tool “get_standard” functional
    • New tool “list_standards” functional
    • New tool “run_city_profile” functional
    • New tool “run_concentration_benchmark” functional
    • New tool “run_contractor_revenue” functional
    • New tool “run_deal_comps” functional
    • New tool “run_demand_durability” functional
    • New tool “run_merger_review” functional
    • New tool “run_private_raises” functional
    • New tool “tell_cultmath” functional
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_decision_brief” rewrote its description, which is the text the model reads security
    • Tool “list_decisions” rewrote its description, which is the text the model reads security
    • Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
    • New tool “run_effective_duty” functional
    • New tool “run_tariff_clock” functional
  • 15 Nov 26 +2
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_decision_brief” rewrote its description, which is the text the model reads security
    • Tool “get_document” rewrote its description, which is the text the model reads security
    • Tool “list_decision_briefs” rewrote its description, which is the text the model reads security
    • Tool “list_decisions” rewrote its description, which is the text the model reads security
    • Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
    • Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
    • Tool “run_angle_demand” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
    • Tool “run_channel_mix” rewrote its description, which is the text the model reads security
    • Tool “run_claim_check” rewrote its description, which is the text the model reads security
    • Tool “run_comment_themes” rewrote its description, which is the text the model reads security
    • Tool “run_cost_squeeze” rewrote its description, which is the text the model reads security
    • Tool “run_customer_concentration” rewrote its description, which is the text the model reads security
    • Tool “run_deal_activity” rewrote its description, which is the text the model reads security
    • Tool “run_demand_check” rewrote its description, which is the text the model reads security
    • Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
    • Tool “run_fad_check” rewrote its description, which is the text the model reads security
    • Tool “run_filing_trend” rewrote its description, which is the text the model reads security
    • Tool “run_launch_lift” rewrote its description, which is the text the model reads security
    • Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
    • Tool “run_premium_check” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
    • Tool “run_revenue_mix” rewrote its description, which is the text the model reads security
    • Tool “run_series_forecast” rewrote its description, which is the text the model reads security
    • Tool “run_share_of_search” rewrote its description, which is the text the model reads security
    • Tool “run_spend_trend” rewrote its description, which is the text the model reads security
    • Tool “run_threshold_odds” rewrote its description, which is the text the model reads security
    • Tool “run_trade_concentration” rewrote its description, which is the text the model reads security
    • Tool “run_triangulation” rewrote its description, which is the text the model reads security
    • Tool “run_write_downs” rewrote its description, which is the text the model reads security
    • Tool “search_cultmath” rewrote its description, which is the text the model reads security
    • Schema quality: 325 → 281 ▲ functional
    • Tool “run_ai_visibility” now declares an output schema ▲ functional
    • Tool “run_ai_visibility_quick” now declares an output schema ▲ functional
    • Tool “run_angle_demand” now declares an output schema ▲ functional
    • Tool “run_answer_share” now declares an output schema ▲ functional
    • Tool “run_answer_share_quick” now declares an output schema ▲ functional
    • Tool “run_channel_mix” now declares an output schema ▲ functional
    • Tool “run_claim_check” now declares an output schema ▲ functional
    • Tool “run_comment_themes” now declares an output schema ▲ functional
    • Tool “run_cost_squeeze” now declares an output schema ▲ functional
    • Tool “run_customer_concentration” now declares an output schema ▲ functional
    • Tool “run_deal_activity” now declares an output schema ▲ functional
    • Tool “run_demand_check” now declares an output schema ▲ functional
    • Tool “run_disclosure_check” now declares an output schema ▲ functional
    • Tool “run_fad_check” now declares an output schema ▲ functional
    • Tool “run_filing_trend” now declares an output schema ▲ functional
    • Tool “run_launch_lift” now declares an output schema ▲ functional
    • Tool “run_peer_benchmark” now declares an output schema ▲ functional
    • Tool “run_premium_check” now declares an output schema ▲ functional
    • Tool “run_regulatory_clock” now declares an output schema ▲ functional
    • Tool “run_regulatory_trend” now declares an output schema ▲ functional
    • Tool “run_revenue_mix” now declares an output schema ▲ functional
    • Tool “run_series_forecast” now declares an output schema ▲ functional
    • Tool “run_share_of_search” now declares an output schema ▲ functional
    • Tool “run_spend_trend” now declares an output schema ▲ functional
    • Tool “run_threshold_odds” now declares an output schema ▲ functional
    • Tool “run_trade_concentration” now declares an output schema ▲ functional
    • Tool “run_triangulation” now declares an output schema ▲ functional
    • Tool “run_write_downs” now declares an output schema ▲ functional
    • First check of Tool coverage: 80 functional
    • “get_decision_evidence” reworded the description of “decision_id” cosmetic
    • “run_premium_check” reworded the description of “brand” cosmetic
  • 14 Nov 26 0
    • Server version: 1.2.0 → 1.3.0 functional
    • New tool “run_series_forecast” functional
    • New tool “run_threshold_odds” functional
  • 13 Nov 26 +1
    • Tool “run_ai_visibility” rewrote its description, which is the text the model reads security
    • Tool “run_ai_visibility_quick” rewrote its description, which is the text the model reads security
    • Tool “run_angle_demand” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share” rewrote its description, which is the text the model reads security
    • Tool “run_answer_share_quick” rewrote its description, which is the text the model reads security
    • Tool “run_channel_mix” rewrote its description, which is the text the model reads security
    • Tool “run_claim_check” rewrote its description, which is the text the model reads security
    • Tool “run_deal_activity” rewrote its description, which is the text the model reads security
    • Tool “run_demand_check” rewrote its description, which is the text the model reads security
    • Tool “run_disclosure_check” rewrote its description, which is the text the model reads security
    • Tool “run_fad_check” rewrote its description, which is the text the model reads security
    • Tool “run_filing_trend” rewrote its description, which is the text the model reads security
    • Tool “run_peer_benchmark” rewrote its description, which is the text the model reads security
    • Tool “run_premium_check” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_clock” rewrote its description, which is the text the model reads security
    • Tool “run_regulatory_trend” rewrote its description, which is the text the model reads security
    • Tool “run_share_of_search” rewrote its description, which is the text the model reads security
    • Tool “run_spend_trend” rewrote its description, which is the text the model reads security
    • Tool “run_triangulation” rewrote its description, which is the text the model reads security
    • Schema quality: 8000 → 10525 ▼ functional
    • New tool “run_comment_themes” functional
    • New tool “run_cost_squeeze” functional
    • New tool “run_customer_concentration” functional
    • New tool “run_launch_lift” functional
    • New tool “run_revenue_mix” functional
    • New tool “run_trade_concentration” functional
    • New tool “run_write_downs” functional
    • “run_peer_benchmark” reworded the description of “metric” cosmetic
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://cultmath.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=cultmath.com CN=YR1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 64b6c7c8768c332cb6dfd69acad993cff7e
SANs: cultmath.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of cultmath.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
cultmath.com. DS published 2371 13 Verified
cultmath.com. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'self'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src https://fonts.gstatic.com; img-src 'self' data: https://www.googletagmanager.com https://*.google.com https://*.googleadservices.com https://*.doubleclick.net https://px.ads.linkedin.com https://i.ytimg.com; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://www.googleadservices.com https://www.google.com https://snap.licdn.com; frame-src 'self' https://shaman.cultmath.com https://td.doubleclick.net https://www.googletagmanager.com https://www.youtube-nocookie.com; connect-src 'self' https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com https://*.google.com https://*.googleadservices.com https://*.doubleclick.net https://px.ads.linkedin.com
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://cultmath.com/mcp Verified 200
http (plaintext) http://cultmath.com/mcp HTTPS enforced 308 https://cultmath.com/mcp
MCP tools · 71 exposed · ~22,358 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
run_wallet_size ~304

Use when the user is sizing a consumer market in dollars or comparing spend across groups: "how big is the US restaurant market by household income?", "which age group spends most on pets?". Returns the annual mean spend per consumer unit, the national total, and the split by income, age, household size or family type, with each group’s share of the dollars, from the BLS Consumer Expenditure Survey. National only. Refuses before you are charged if the groups do not add up to the total. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: one release (latest Consumer Expenditure Survey); segment: by (income, age, household size, family type), item. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For how many households match the profile, use run_audience_size.

NameTypeReqDescription
bystring–How to split households. Default income.
itemstringyesSpending category (CE item code).
NameTypeReqDescription
availableboolean–false when the run is switched off; then nothing can be charged.
errorstring–Why the inputs were refused, with the expected usage. Nothing is charged.
instructionsobject–How to pay over MPP and x402, and how to ask for publication.
limits––What the run cannot tell you, stated before you pay.
next_stepstring–What to tell the user before paying.
notestring–Why the run is unavailable, when it is.
payment_urlstring–POST here to run and pay. Not a checkout page.
price_usdnumber–Price over MPP (Stripe shared payment token).
recipestring–The run, e.g. "filing-trend".
what_you_getstring–What the paid result will contain for these inputs.
x402_price_usdnumber–Price over x402 (USDC on Base), when offered.

No examples provided.

run_write_downs ~264

Use when the user asks whether a company has impaired a brand or an acquisition, is preparing to sell a brand to a strategic buyer, or wants to know how acquirers have valued past deals. Returns every fiscal year in which the company tagged a goodwill or intangible impairment in its 10-K XBRL, with the amount by line (goodwill, brands and trademarks, other intangibles) and each filing's citation. Refuses before you are charged if none is tagged. Every result carries a run id, a date and a citation line. Calling this tool returns a quote, not the result: what the run measures, its price and a payment_url. The run happens only when you POST to payment_url, and a run that fails its controls refuses there with nothing charged. Dimensions (vary these inputs to cut the answer; each call is its own run): over time: built in: every fiscal year tagged. Price: $0.05 per run over x402 (USDC on Base, no account needed), or $0.50 over MPP (a Stripe shared payment token); charged only when the run comes back sound. For deal activity across a sector, use run_deal_activity.

NameTypeReqDescription
tickerstringyesThe company.
NameTypeReqDescription
availableboolean–false when the run is switched off; then nothing can be charged.
errorstring–Why the inputs were refused, with the expected usage. Nothing is charged.
instructionsobject–How to pay over MPP and x402, and how to ask for publication.
limits––What the run cannot tell you, stated before you pay.
next_stepstring–What to tell the user before paying.
notestring–Why the run is unavailable, when it is.
payment_urlstring–POST here to run and pay. Not a checkout page.
price_usdnumber–Price over MPP (Stripe shared payment token).
recipestring–The run, e.g. "filing-trend".
what_you_getstring–What the paid result will contain for these inputs.
x402_price_usdnumber–Price over x402 (USDC on Base), when offered.

No examples provided.

search_cultmath ~121

Search the free CULT+MATH studies and answers (and the briefs) by keywords. Returns titles, URLs, dates, the lead finding and the brief that goes deeper. Start here for any question; read a result in full with get_document. When nothing published answers it, a run_* tool can measure it fresh.

NameTypeReqDescription
kindstring–Restrict results. Default any.
limitinteger–Default 5.
querystringyesKeywords, e.g. "streaming ad tier" or "retailer concentration".

No output schema declared.

No examples provided.

tell_cultmath ~139

Free. Records one reason, from a fixed list, why a quoted or suggested paid run was not bought, so CULT+MATH can fix the cause: price, no_wallet (no way to pay), user_did_not_ask, wrong_data (the run does not measure what was needed), switched_off, or other. Takes no free text and returns only a confirmation. Counted anonymously by week; nothing about the user is kept.

NameTypeReqDescription
reasonstringyesThe main reason the run was not bought.
runstring–Optional: the run_* tool it was about, e.g. "run_city_profile".

No output schema declared.

No examples provided.

Install

How do I install the CULT+MATH Decision Briefs MCP server?

CULT+MATH Decision Briefs is a hosted endpoint at https://cultmath.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 · cultmath.com

# add to Claude Code
claude mcp add --transport http com-cultmath-decision-briefs 'https://cultmath.com/mcp'
Common questions

What is the CULT+MATH Decision Briefs MCP server?

CULT+MATH Decision Briefs is an MCP server listed in the public MCP registry as com.cultmath/decision-briefs. Odds and forecasts on the numbers executives plan against, plus free studies and Decision Briefs. This page covers its hosted endpoint (https://cultmath.com/mcp).

Is the CULT+MATH Decision Briefs MCP server safe to use?

CULT+MATH Decision Briefs scores 79 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 CULT+MATH Decision Briefs MCP server expose?

CULT+MATH Decision Briefs exposes 71 tools: list_decision_briefs, get_decision_brief, search_cultmath, list_decisions, buy_decision_evidence, and 66 more. Their descriptions and schemas cost roughly 22,358 tokens of context every time the server is loaded.

Does the CULT+MATH Decision Briefs MCP server require authentication?

No. We connected to CULT+MATH Decision Briefs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CULT+MATH Decision Briefs MCP server still maintained?

CULT+MATH Decision Briefs 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 CULT+MATH Decision Briefs MCP server?

VerifyMCP ran 13 checks on CULT+MATH Decision Briefs, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.