Home / MCP registry index / ai.jawz/jawz
ai.jawz/jawz
ai.jawz/jawz in the official MCP registry.
Endpoint https://jawz.ai/api/mcp.
The registry describes it as: Live macro data for AI agents: regime, conditions, liquidity, with input provenance. No signup.
We read its 24 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
get_started get_dashboard get_world_brief get_prices get_macro_regime get_regime_history get_liquidity_history get_conditions_history get_indicator_history get_data_health get_financial_conditions get_growth_indicators get_inflation_indicators get_event_calendar get_weekly_data_releases get_etf_profile score_position_drift get_drift_alerts list_loops get_loop get_chapter run_chapter run_mode get_china_liquidity
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-jawz-jawz)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.