macroindex
Registry code: c8e078e85c1ef225
Macro Index is a neutral, cited reference of central-bank policy rates, decision calendars and the issuer pages that publish each decision. It covers 21 central banks (Banco Central do Brasil, Bank Indonesia, Bank of Canada, Bank of England, Bank of Japan, Bank of Korea, Bank of Mexico, Central Bank of the Republic of Türkiye, Czech National Bank, European Central Bank, Federal Reserve (Federal Open Market Committee), Magyar Nemzeti Bank, Narodowy Bank Polski, Norges Bank, People's Bank of China, Reserve Bank of Australia, Reserve Bank of India, Reserve Bank of New Zealand, South African…
- endpoint
- https://macroindex.org/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is macroindex live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is macroindex free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does macroindex have?
- 7 tools: dataset_health, check_question, resolution_sources, submit_correction, bank_status, upcoming_auctions, upcoming_decisions.
- Is macroindex safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
upcoming_auctions open 1h ago
Government bond auctions in a date window, soonest first: US Treasury, the German Finanzagentur and the Italian Treasury, calendar and results. Each has the auction day, closeAt (the bidding deadline in UTC), instrument, tenor, CUSIP/ISIN and size once known, status (scheduled, announced, held, cancelled), the issuer's result page and its format, and the result (yield, bid-to-cover, allotted) only once the issuer has published it. Facts only, no forecasts.
{ "type": "object", "properties": { "to": { "type": "string", "description": "End date YYYY-MM-DD; default from + 60 days" }, "from": { "type": "string", "description": "Start date YYYY-MM-DD; default today" }, "issuer": { "type": "string", "description": "us-treasury, de-finanzagentur or it-mef (or a name: \"Treasury\", \"Germany\", \"Italy\"); default all" } } }arguments 17 linesupcoming_decisions open 1h ago
Policy-rate decisions in a date window, soonest first: decision day (local to the bank), announcement time in UTC where the bank publishes one, whether the date is on the bank's calendar, moved or unscheduled, the rate going in, and the decision once observed. Covers 21 central banks (Banco Central do Brasil, Bank Indonesia, Bank of Canada, Bank of England, Bank of Japan, Bank of Korea, Bank of Mexico, Central Bank of the Republic of Türkiye, Czech National Bank, European Central Bank, Federal Reserve (Federal Open Market Committee), Magyar Nemzeti Bank, Narodowy Bank Polski, Norges Bank, People's Bank of China, Reserve Bank of Australia, Reserve Bank of India, Reserve Bank of New Zealand, South African Reserve Bank, Sveriges Riksbank, Swiss National Bank) and 2 inflation release series.
{ "type": "object", "properties": { "to": { "type": "string", "description": "End date YYYY-MM-DD; default from + 60 days" }, "from": { "type": "string", "description": "Start date YYYY-MM-DD; default today" }, "banks": { "type": "array", "items": { "type": "string", "description": "Bank id (e.g. \"reserve-bank-of-india\", \"ecb\", \"cbrt\"), name, common abbreviation (RBI, SNB, BoJ) or country" }, "description": "Only these banks; default all" } } }arguments 21 linesdataset_health unknown never probed
Freshness per bank (last observed decision, next meeting, days to it, whether its decision statement is resolvable) and the publisher-gate warnings. Use to judge how far to trust an answer.
{ "type": "object", "properties": {} }arguments 4 linescheck_question unknown never probed
Is a question about a rate decision or a government bond auction settleable, when, and on which source? Finds the bank (or the auction issuer, tenor) and the date in the text. Refuses a decision or auction that has not been observed: a decision settles only after its statement is observed on the bank's own page, an auction only once the issuer's result is recorded (it says when bidding closes, closeAt in UTC, and on which result page). Also says when the source has not yet met the reads bar (5 right, 0 wrong).
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "The question, e.g. \"Will the RBI raise its repo rate on 7 Oct 2026?\" or \"Will the German 30-year Bund auction on 14 Oct 2026 have a bid-to-cover above 1.5?\"" } } }arguments 12 linesresolution_sources unknown never probed
The kinds of page a bank publishes (decision statement, calendar, rate history, press feed): where each URL is found, its pattern (for recognising a page, never for building one), a real example, the reads recorded on it, and whether it is resolvable.
{ "type": "object", "required": [ "bank" ], "properties": { "bank": { "type": "string", "description": "Bank id (e.g. \"reserve-bank-of-india\", \"ecb\", \"cbrt\"), name, common abbreviation (RBI, SNB, BoJ) or country" }, "resolvable_only": { "type": "boolean", "description": "Only sources that meet the reads bar" } } }arguments 16 linessubmit_correction unknown never probed
Report a mistake with the URL of the bank's own page that proves it. The report is public and is checked like any other claim; it never changes the data by itself. Returns the report id and where to follow it.
{ "type": "object", "required": [ "url", "evidence" ], "properties": { "url": { "type": "string", "description": "https URL of the page that proves the correction (ideally the bank's own)" }, "bank": { "type": "string", "description": "Bank id, if the report is about a covered bank" }, "evidence": { "type": "string", "description": "What is wrong and what is right, 10 to 2000 characters" } } }arguments 21 linesbank_status unknown 1h ago
One bank: the policy rate in force and since when, the last observed decision with its statement, the next meeting, past facts computed from observed decisions only (days since the last change, consecutive holds, counts of past move sizes), freshness and data warnings.
{ "type": "object", "required": [ "bank" ], "properties": { "bank": { "type": "string", "description": "Bank id (e.g. \"reserve-bank-of-india\", \"ecb\", \"cbrt\"), name, common abbreviation (RBI, SNB, BoJ) or country" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc8e078e85c1ef225.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c8e078e85c1ef225/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c8e078e85c1ef225?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.