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.

ai.jawz/jawz

REMOTE · JAWZ.AI · SCANNED SEP 20

Live macro data for AI agents: regime, conditions, liquidity, with input provenance. No signup.

Available components

+3 this week 89 Trust /100
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 Security94
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3853 tokens (~175/item across 22 items; 22 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 Management80
  • Stability observed for 24 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 (100% 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 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 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
Install

How do I install the ai.jawz/jawz MCP server?

ai.jawz/jawz is a hosted endpoint at https://jawz.ai/api/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 · jawz.ai

# add to Claude Code
claude mcp add --transport http ai-jawz-jawz 'https://jawz.ai/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-jawz-jawz": {
      "url": "https://jawz.ai/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-jawz-jawz": {
      "type": "http",
      "url": "https://jawz.ai/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-jawz-jawz]
url = "https://jawz.ai/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-jawz-jawz": {
      "type": "remote",
      "url": "https://jawz.ai/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-jawz-jawz --url 'https://jawz.ai/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-jawz-jawz:
    url: "https://jawz.ai/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-jawz-jawz": {
      "Transport": "http",
      "Url": "https://jawz.ai/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ai-jawz-jawz -t streamable-http -u 'https://jawz.ai/api/mcp'
// mcp.json
{
  "mcpServers": {
    "ai-jawz-jawz": {
      "type": "http",
      "url": "https://jawz.ai/api/mcp"
    }
  }
}

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

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.

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 15 Sept 26 +47
    • Authorization: unverified → pass security
    • Injection markers: unverified → pass security
    • Schema quality: unverified → fail functional
    • Schema quality: unverified → fail functional
    • Schema quality: unverified → excellent functional
    • Tool coverage: unverified → 100 functional
    • Stability: fail → 0.63 functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Sept 26 −47
    • Authorization: pass → unverified security
    • Tool safety: pass → unverified security
    • Stability: 0.57 → fail security
    • Schema quality: excellent → unverified functional
    • Schema quality: fail → unverified functional
    • Schema quality: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 13 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 8 Sept 26 +1

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

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 20 Sept 2026 · Probed https://jawz.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jawz.ai CN=YR2,O=Let's Encrypt,C=US 11 Aug 2026 9 Nov 2026 RSA 2048 SHA256-RSA 6762cdee3922c754ea53c8c6048522aa42c
SANs: jawz.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 insecure

Validation of jawz.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
jawz.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://jawz.ai/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://jawz.ai/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=63072000

Protected resource metadata

Document https://jawz.ai/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://jawz.ai
Authorisation server https://jawz.ai

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jawz.ai/api/mcp Verified 200
http (plaintext) http://jawz.ai/api/mcp HTTPS enforced 308 https://jawz.ai/api/mcp
MCP tools · 22 exposed · ~3,853 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_chapter ~77

Fetch the full content of a chapter by loop slug and node. Loops not marked open require entitlement; every published loop is currently open and free. Does not log an invocation; run_chapter is the variant that runs the framework and logs.

NameTypeReqDescription
loop_slugstringyesLoop slug
nodestringyesChapter node
NameTypeReqDescription
author_name
content
loop_slug
loop_title
node
terms_glossary
title
version

No examples provided.

get_china_liquidity ~89

Read the latest Mako-curated PBoC balance-sheet publication (CNY trillions + source URL + as_of_month + note). Public read — suitable for surfacing directly when explaining the China leg of global liquidity. The same value is also embedded in get_financial_conditions.pillars.global_liquidity.components.china; this tool exists for direct/auditable access.

Input schema present but exposes no named parameters.

NameTypeReqDescription
row
status
terms_glossary

No examples provided.

get_conditions_history ~375

Financial-conditions read-history — a timeseries of how conditions have moved over recent weeks. Returns one row per sample date with the composite (loose/neutral/tight), direction (easing/stable/tightening), and every pillar's value + class: 10Y real yield, HY/IG credit spreads, DXY, VIX, global-liquidity class. The rate legs behind the real yield are exposed numerically too (dgs10_pct, t10yie_pct, t5yie_pct, t10y2y_pct), so a real-yield move can be read as nominal-led or breakeven-led rather than only as a fused number. Completes the Chapter 1 history trio with get_regime_history (the judgment) and get_liquidity_history (the flow) — this is the price of risk. Surfaces trajectory that a point read hides (e.g. HY spreads widening for six straight weeks while VIX stays calm), and grounds 'conditions are tightening' statements in observed pillar changes. Window deltas per pillar are in 'summary.deltas'; composite/direction/pillar classification changes are listed as events. The response includes a 'presentation' object whose 'display_markdown' is a pre-formatted table; 'data.rows' and 'summary' carry the same values structured. Rows are provenance-tagged 'observed' (live that day, true vintage) or 'reconstructed' (point-in-time from vintage data — each series as it was published on that date, ~4 months deep). Defaults to the last 12 weeks, weekly.

NameTypeReqDescription
intervalstringSample cadence (default weekly)
lookback_weeksnumberHow many weeks of history to cover (default 12, clamped 1–52)
NameTypeReqDescription
data
generated_at
presentation
status
summary
tool
warnings

No examples provided.

get_data_health ~84

Freshness status for every data source Jawz reads: per-source release date, latest observation date, expected cadence, age in days, and whether any source is stale or unavailable. Also reports whether the ingestion pipeline is keeping up, and carries plain-language notices when a scheduled update has not arrived. Applies when the reliability of a figure depends on how current its underlying data is.

Input schema present but exposes no named parameters.

NameTypeReqDescription
any_stale
any_unavailable
as_of
china_release_alert
collector
crons
notices
sources
terms_glossary
umich_release_alert

No examples provided.

get_drift_alerts ~177

Portfolio-wide drift scan. Iterates Decision Records, calls score_position_drift on each, returns flagged positions with severity + why_flagged + review_questions. Flag types: drift_severe (review_now), drift_meaningful (deteriorated), fit_low_structural (score ≤2 but unchanged since entry — low by design, not decay), fit_low_decayed (score ≤2 AND below entry fit — deteriorated after entry), conviction_gap (|gap| ≥3), thesis_undocumented (entry_date or thesis missing). Backs Chapter 4 Mode 4.3 (Thesis Status Sweep) as the portfolio-wide drift scan; flagged names feed a Mode 4.2 (Position Retrospective).

NameTypeReqDescription
portfolioarrayyesArray of Decision Records — one per position the user wants scanned
NameTypeReqDescription
alerts
as_of_date
flagged_positions
positions_without_records
staleness_flags
terms_glossary
total_positions

No examples provided.

get_etf_profile ~173

ETF look-through for Chapter 2 Mode 2.2 (Concentration Check). Given ETF ticker(s), returns each fund's top holdings with weights so the AI can overlay them with the user's direct positions and surface hidden single-name concentration. Each profile carries source='live' (Vanguard API, fresh) or source='catalog' (dated snapshot — see as_of). Holdings are TOP-N only, so any true-exposure figure computed from this is a floor, not exact. Bond and commodity ETFs return no holdings by design. Tickers not in the catalog come back in unknown_tickers; their contents are not known to Jawz and no holdings are returned for them.

NameTypeReqDescription
tickersarrayyesETF ticker symbols to look through (e.g. ['QQQ','VGT','SPY'])
NameTypeReqDescription
coverage
data_sources
guidance
profiles
requested
terms_glossary
unknown_tickers

No examples provided.

get_event_calendar ~292

Scheduled US macro events (FOMC + CPI + NFP + PCE) with dates and consensus. Consensus values are Mako-curated and arrive with provenance (source, source_url, published_at, age_days). An event with no curated consensus carries consensus: null, which means the value is not published rather than zero. Mode 1.2 covers the qualitative-scenario path for events whose consensus is not published. consensus_metrics_expected lists the metric keys a complete consensus would carry for that event type. Market-implied pricing (what_is_priced / CME FedWatch) is a separate quantity and remains deferred. COVERAGE: only fomc, cpi, nfp and pce have dates in this calendar. ecb, boj and boe are accepted for consistency with the consensus vocabulary but carry NO dates, so filtering to them returns an empty list and says so in staleness_flags — that is 'not tracked here', never 'none is scheduled'. Coverage also runs to a fixed last date; a window past it is flagged rather than silently short.

NameTypeReqDescription
event_typesarrayFilter by event types (default: fomc, cpi, nfp, pce). Only those four carry dates; ecb/boj/boe return empty with a staleness flag.
lookahead_daysnumberHow many days forward to look (default 14)
NameTypeReqDescription
as_of
data_sources
events
staleness_flags
terms_glossary

No examples provided.

get_financial_conditions ~175

Full financial conditions read: global liquidity (Fed + ECB + BoJ central-bank balance sheets, FX-converted to USD; PBoC included when a fresh Mako-curated publication is available — basis 'g4' vs 'g3'), real yields, HY/IG credit spreads, DXY, VIX. US net liquidity is retained as a sub-component. Returns composite + direction + per-pillar classifications + drivers. The `scope` and `scope_note` fields tell you whether the read is G4 or G3, and the China sub-component carries Mako-curated provenance (as_of_month, source_url, note). Pass summary_only:true for the lightweight one-line read used in regime composition.

NameTypeReqDescription
summary_onlybooleanIf true, return composite + direction + one-line driver only
NameTypeReqDescription
as_of
composite
data_sources
direction
drivers
pillars
scope
scope_note
staleness_flags
terms_glossary

No examples provided.

get_growth_indicators ~131

Growth pillar indicators: industrial production (ISM proxy), consumer sentiment, yield curve, initial claims, plus the Atlanta Fed GDPNow nowcast of the quarter in progress. GDPNow carries its own reference_quarter, the publication date of the estimate, and the previous estimate of the SAME quarter, so its direction of travel is readable; it is reported, not scored, so it does not move the classification. When no estimate is on file the block reports status: unavailable and says so in staleness_flags — not published, which is not the same as zero. Returns classification (green/yellow/red).

Input schema present but exposes no named parameters.

NameTypeReqDescription
as_of
classification
consumer_sentiment_umcsent
data_sources
gdpnow
ism_manufacturing
leading_indicators
staleness_flags
terms_glossary

No examples provided.

get_inflation_indicators ~56

Inflation pillar indicators: headline + core CPI, headline + core PCE (YoY and MoM), 5Y/10Y breakevens, wage growth. Returns classification (supportive/neutral/headwind).

Input schema present but exposes no named parameters.

NameTypeReqDescription
as_of
breakevens
classification
cpi
data_sources
pce
staleness_flags
terms_glossary
wage_growth

No examples provided.

get_liquidity_history ~396

Global-liquidity read-history — a timeseries of central-bank liquidity over recent weeks. Returns one row per sample date with the full decomposition (Fed / ECB / BoJ / PBoC in USD trillions), the active basis (g4/g3/us_fallback), and the supportive/neutral/draining classification, plus coverage (basis) changes, China-leg publication steps, and classification changes as events. History companion to get_financial_conditions (Chapter 1 Mode 1.5 Global Liquidity Read). Reading note, enforced by the artifact: when the basis flips g4↔g3 (China PBoC publication freshness), the headline total moves by the ~$7T China component, which is a coverage change rather than a liquidity move. The window trend is therefore computed on constant G3 basis, and every basis flip is listed with an explicit note. A China-leg publication step is a DIFFERENT event and is reported separately: PBoC publishes monthly ~15 days in arrears, so on the day a new statement is recorded the PBoC leg absorbs a whole month of balance-sheet change (plus FX) in one step — real change, but not change that happened on that date, and not the same thing as a coverage flip. The response includes a 'presentation' object whose 'display_markdown' is a pre-formatted table; 'data.rows' and 'summary' carry the same values structured. Rows are provenance-tagged 'observed' (live that day, true vintage) or 'reconstructed' (point-in-time from vintage data — each series as it was published on that date, ~4 months deep). Defaults to the last 12 weeks, weekly.

NameTypeReqDescription
intervalstringSample cadence (default weekly)
lookback_weeksnumberHow many weeks of history to cover (default 12, clamped 1–52)
NameTypeReqDescription
data
generated_at
presentation
status
summary
tool
warnings

No examples provided.

get_loop ~61

Get metadata and chapter manifest for a loop by slug. Returns loop info and the list of chapter nodes with titles — no chapter content. All active loops are navigable by anyone.

NameTypeReqDescription
loop_slugstringyesLoop slug (e.g. 'jawz')
NameTypeReqDescription
author_name
chapters
description
improvement_model
methodology_statement
price_cents
pricing_model
slug
terms_glossary
title
version
visibility

No examples provided.

get_macro_regime ~90

Get current macro regime (GREEN/YELLOW/RED) with business cycle positioning. The response carries the same values three ways: 'presentation.display_markdown' is a pre-formatted rendering with tables, 'tables' is the structured form of those tables, and 'data' holds the raw values. A 'provenance' block lists each input with its as-of date and age in days.

Input schema present but exposes no named parameters.

NameTypeReqDescription
data
generated_at
pillars
presentation
staleness_flags
status
summary
tables
tool
warnings

No examples provided.

get_prices ~294

Live prices for one or more holdings, and the answer shows its work. Resolves raw tickers (stocks, ETFs, crypto, international listings) and returns price, value, and day change per symbol, plus per holding: what it resolved to (asset: type, exchange, ISIN, provider id), how surely (resolution: matched_by isin|qualified_symbol|bare_symbol, candidates, mismatch against the caller's hints), the native quote with its own time (quote), the FX rate actually applied, dated and sourced (fx), and the position value native and in the base currency. Optional per-holding hints — isin (equities/ETFs/funds), exchange, asset_class — narrow resolution; a hint that contradicts the result is reported, not silently overridden. Symbols that collide with tokenized-stock proxies on the crypto side (ALAB, LITE, NBIS, GLW, CBRS, DRAM, AIPO) resolve to the listed instrument, never the token; qualifying as NASDAQ:X / X.US does the same explicitly. base_currency defaults to USD; 'native' returns unconverted quotes.

NameTypeReqDescription
base_currencystring|nullCurrency for price, value and totalValue. Omit for USD (default). 'native' or null: no conversion — each line is stated in its quote currency and fx is null.
holdingsarrayyesPortfolio holdings to analyze
NameTypeReqDescription
holdings
terms_glossary
timestamp
totalValue
warnings

No examples provided.

get_regime_history ~379

Macro regime read-history — a timeseries of how the regime and its drivers have moved over recent weeks. Returns one row per sample date (regime color, business-cycle quadrant, growth + inflation class, consumer sentiment, global liquidity, dominant risk, confidence) plus the transitions between them (e.g. SUMMER → FALL). Provides the observed history behind a 'what changed since …' question, rather than a comparison of two separate point reads. Reading note, enforced by the artifact: the Liquidity column steps for two reasons that are NOT the market, and both are listed as first-class events in summary.liquidity_events — a g4↔g3 coverage flip (the whole PBoC component entering or leaving the sum: not a liquidity move at all), and a China-leg publication step (PBoC publishes monthly ~15d in arrears, so the day a new statement is recorded the column absorbs a whole month of change: real change, wrong date). Do not read that column as a trend without checking them; get_liquidity_history carries a constant-basis G3 series that is immune to both. The response includes a 'presentation' object whose 'display_markdown' is a pre-formatted table; 'data.rows' and 'summary' carry the same values structured. Each row is provenance-tagged: 'observed' (captured live that day — true vintage) or 'reconstructed' (computed point-in-time from vintage data — each series as it was published on that date, so later revisions are excluded; depth-limited). Defaults to the last 12 weeks, weekly.

NameTypeReqDescription
intervalstringSample cadence (default weekly)
lookback_weeksnumberHow many weeks of history to cover (default 12, clamped 1–52)
NameTypeReqDescription
data
generated_at
presentation
status
summary
tool
warnings

No examples provided.

get_started ~82

Orientation for a new Jawz connection, and for questions about what Jawz is, what it covers, or how it is used. Returns a description of the Jawz Loop, example opening prompts, a one-line live market read drawn from the current data layer, a note on the plain-English glossary included in Jawz responses, and a link to the full guide.

Input schema present but exposes no named parameters.

NameTypeReqDescription
audience_note
first_prompts
how_to_go_deeper
if_rumo_is_connected
live_now
memory_note
terms_glossary
what_this_is

No examples provided.

get_weekly_data_releases ~226

Past week's data releases with H.4.1 net liquidity update. Anchored to Friday — most current when run Friday morning or later. Each release classifies actual vs consensus where BOTH are on file (both Mako-curated): `surprise` is hot / modestly hot / in-line / modestly cool / cool on the headline metric, `vs_consensus` is the same comparison stated neutrally as above/below/in-line, and `metrics` breaks it down per metric. hot/cool is DIRECTIONAL versus consensus, not a verdict — a hot CPI and a hot payrolls print mean opposite things for the same book. `surprise: "n/a"` means the comparison could not be made; `implication` names which half is missing. consensus_provenance.age_days is measured at week_ending, not at call time, so re-asking for an earlier week returns the same age it did the first time.

NameTypeReqDescription
week_endingstringWeek ending date (YYYY-MM-DD); defaults to last Friday
NameTypeReqDescription
as_of
data_releases
data_sources
fed_h41_update
policy_events
staleness_flags
terms_glossary
week_ending

No examples provided.

get_world_brief ~124

Read the Jawz World Brief — the weekly Mako-bylined market read published at jawz.ai/brief. Returns the latest edition by default, or a specific one by slug (YYYY-MM-DD). Every claim in a brief traces to a Jawz tool read from its week. Setting list_only:true returns the available editions without their content.

NameTypeReqDescription
list_onlybooleanReturn only the list of available editions (slug, title, regimeLine, takeaway).
slugstringEdition to fetch, YYYY-MM-DD. Omit for the latest.
NameTypeReqDescription
available_editions
byline
canonical_url
latest_url
note
regimeLine
sections
slug
takeaway
terms_glossary
title

No examples provided.

list_loops ~54

List all available Jawz loops. Returns loop metadata, access status, and which loop is currently active for this user. Every published loop is free and open. Deprecated loops you are entitled to are included with deprecated: true.

Input schema present but exposes no named parameters.

NameTypeReqDescription
loops
terms_glossary

No examples provided.

run_chapter ~117

Returns a chapter's published framework text: its modes, the questions each asks, and the output format it describes. The framework is reference material for the assistant to apply as it judges appropriate. Repeat calls return the same chapter content — the text is not regenerated per call. Each call appends one usage-counter row and returns a new invocation_id used for feedback.

NameTypeReqDescription
contextstringOptional user context (portfolio details, ticker, question)
loop_slugstringyesLoop slug
nodestringyesChapter node
NameTypeReqDescription
author_name
content_note
framework_content
invocation_id
loop_slug
loop_title
node
terms_glossary

No examples provided.

run_mode ~113

Returns the published framework text for one named mode within a chapter, rather than the full chapter. Repeat calls return the same mode content — the text is not regenerated per call. Each call appends one usage-counter row and returns a new invocation_id used for feedback.

NameTypeReqDescription
contextstringOptional user context
loop_slugstringyesLoop slug
mode_slugstringyesMode slug (e.g. 'equity-screen', 'regime-overlay')
nodestringyesChapter node
NameTypeReqDescription
author_name
content_note
framework_content
invocation_id
loop_slug
loop_title
mode_slug
node
terms_glossary

No examples provided.

score_position_drift ~288

Score how a single position's regime fit has drifted since entry. Returns regime_at_entry, regime_now, fit_score_at_entry, fit_score_now, drift_score (now - entry), drift_label (improved/stable/deteriorated/review_now), explanation, and review_questions. No buy/sell recommendation — output is observational. Supports Chapter 4 Mode 4.2 (Position Retrospective) for single-name regime-fit review and Mode 4.3 (Thesis Status Sweep) for per-position drift across the book.

NameTypeReqDescription
asset_classstringyesAsset class for fit-score lookup, drawn from the holding's actual exposure (Chapter 2 Mode 2.1) rather than from the current regime. A hybrid holding is scored per sleeve and weight-blended. Drives t…
convictionnumberUser-supplied conviction 1–10. Drives conviction_gap if a meaningful gap exists vs the regime fit score.
entry_datestringyesISO date (YYYY-MM-DD) when the position was opened
symbolstringyesTicker or instrument (e.g. AAPL, BTC, TLT)
symbol_typestringPrice-API hint. Inferred from asset_class if omitted.
thesisstringOriginal thesis text. Echoed back word-for-word in review questions.
NameTypeReqDescription
as_of_date
asset_class
classification_warnings
conviction_gap
drift_label
drift_score
entry_date
explanation
fit_score_at_entry
fit_score_now
price_at_entry
price_now
regime_at_entry
regime_now
review_questions
staleness_flags
symbol
terms_glossary
total_return_pct

No examples provided.

Common questions

What is the ai.jawz/jawz MCP server?

ai.jawz/jawz is an MCP server listed in the public MCP registry as ai.jawz/jawz. Live macro data for AI agents: regime, conditions, liquidity, with input provenance. No signup. This page covers its hosted endpoint (https://jawz.ai/api/mcp).

Is the ai.jawz/jawz MCP server safe to use?

ai.jawz/jawz scores 89 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 ai.jawz/jawz MCP server expose?

ai.jawz/jawz exposes 22 tools: get_started, get_world_brief, get_prices, get_macro_regime, get_regime_history, and 17 more. Their descriptions and schemas cost roughly 3,853 tokens of context every time the server is loaded.

Does the ai.jawz/jawz MCP server require authentication?

Yes. ai.jawz/jawz asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the ai.jawz/jawz MCP server still maintained?

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