ai.jawz/jawz
ai.jawz/jawz · 1.0.1
Live macro data for AI agents: regime, conditions, liquidity, with input provenance. No signup.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://jawz.ai/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 22 tools.
- Protocol
- 2025-06-18
- Calls itself
- jawz 0.2.0
- Handshake time
- 597 ms
- HTTP status
- 200
The tools it lists (22, as of 8 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_startedOrientation 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.
get_world_briefRead 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.
get_pricesLive 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; asset.isin is filled when you pass an isin hint or the provider profile carries one, and is null otherwise — it is not looked up), 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, date
get_macro_regimeGet 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.
get_regime_historyMacro 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
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.jawz/jawz, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 42 days ago. The registry entry · jawz.ai