DFin MCP

1.0 Overview

This product uses the FRED® API but is not endorsed or certified by the Federal Reserve Bank of St. Louis. Use of FRED data through DFin is subject to the FRED® API Terms of Use.

World Bank data is provided under the applicable World Bank Dataset Terms and Conditions. Dataset and indicator metadata may identify additional attribution, licensing, or third-party permission requirements.

BLS data is provided under the BLS Public Data API Terms of Service. BLS requires retrieval-date attribution and this notice with redistributed results: “BLS.gov cannot vouch for the data or analyses derived from these data after the data have been retrieved from BLS.gov.”

EIA data is provided under the EIA API Terms of Service. When reusing EIA data, retain its source acknowledgment and review the EIA reuse policy.

U.S. Census Bureau data is a U.S. Government work in the public domain, provided under the Census Bureau API Terms of Service. Cite the U.S. Census Bureau as the source, and do not use the Census Bureau's name or logo in any way that implies endorsement.

U.S. Bureau of Economic Analysis data is a U.S. Government work in the public domain, provided under the BEA API Terms of Service. Cite the U.S. Bureau of Economic Analysis as the source, and do not present results in a way that implies BEA endorsement.

OECD terms permit data to be used, copied, adapted, distributed, shared, and embedded for any purpose, including commercial use, subject to any dataset-specific restrictions. Cite the OECD as the source, and do not present results in a way that implies OECD endorsement. See the OECD's terms and conditions.

Eurostat data is reused under the European Commission's Decision 2011/833/EU, which permits commercial and non-commercial reuse provided the source is acknowledged. Cite Eurostat as the source, and do not present results in a way that implies Eurostat or European Commission endorsement. See Eurostat's copyright and licence policy.

ECB data is reused under the ECB's copyright notice, which permits free use provided the information is reproduced accurately and the ECB is cited as the source. dfin.pro provides ECB macro data free of charge, and the same information may be obtained free of charge directly from the ECB. Any modification must be stated explicitly; dfin.pro returns the ECB's own observations unchanged. Do not present results in a way that implies ECB endorsement.

Japan Statistics Dashboard data is subject to its copyright policy. Indicator and linked survey metadata may contain separate rights or redistribution restrictions; when an explicit notice is detected, DFin requires the user's permission decision before retrieving observations. No detected notice is not legal clearance. Required credit: “This service uses the API feature of Statistics Dashboard, but the contents of this service are not guaranteed by the Statistics Bureau of Japan.”

The MCP interface is currently unversioned. Connected clients should use the live tool schemas as the source of truth for tool arguments and return contracts.

2.0 Connect

OAuth 2.0 is recommended for Claude, ChatGPT, and other interactive MCP clients. Add https://www.dfin.pro/mcp as the server URL. If you are not signed in to dfin.pro, the connection flow asks you to authenticate and then returns you to the consent screen for the dfin:mcp scope. No API key needs to be pasted into the client.

Verified dfin.pro accounts can connect with OAuth when it is available, or create an API key from Account for compatible clients. The monthly free allowance applies before prepaid billing.

Email/password accounts must be verified before they can sign in. If you need to verify your email address, complete verification and then restart the connection from your MCP client.

Existing API-key integrations continue to work. Send the API key in the Authorization header as Authorization: Bearer <api_key>.

The legacy https://www.dfin.pro/mcp/<api_key> URL remains available for clients that cannot use OAuth or send headers. Because it places the API key in the URL, it is less secure and should not be used for Claude or ChatGPT. Do not combine it with an Authorization header.

For setup walkthroughs, use the examples for Claude, Claude Code, Codex, and Grok. ChatGPT should also be configured with https://www.dfin.pro/mcp; its connection flow discovers the same OAuth service and requires no pasted API key.

3.0 Rate Limits

Every account receives 250 free core REST and MCP data requests per UTC calendar month. Help, contract-discovery, and control calls do not use that allowance. The allowance is shared across API keys and connected OAuth clients. The starter limits remain 60 requests per minute and 5,000 requests per rolling 24 hours; bulk document searches also share a 10-per-minute account limit.

4.0 Billing

Call get_credit_balance to inspect the current billing mode, wallet balance, monthly free-request usage and reset, Notebook access, and rate limits. The first 250 core REST and MCP requests each UTC month are free. After that, eligible PAYG calls cost $0.0100 for durably retrievable accepted output. Pending polls and failed attempts create no additional charge. A pending response can follow an uncertain committed charge, and a failed task can retain a charge for earlier accepted partial output; reconcile the operation receipt and wallet before retrying. Identical successful requests replay for 90 seconds from completion without extending expiry or using another allowance request or charge. Polling the same processing task returns fresh progress and counts as one request throughout that task generation. A successful partial result can be charged once; later results from that task do not create another charge. Notebook tools require an active Base or higher research subscription. Notebook tools never consume credits and retain their existing allowance behavior; Notebook writes do not automatically replay. Operator-managed trial access waives per-call debits through both REST and MCP. Research-subscription trials remain separate and do not waive ordinary core PAYG charges.

5.0 After Connecting

Start with agent_help(topic="agent_guide") for shared safeguards and focused-methodology routing. Load only the focused methodology topics relevant to the work being done. Live MCP tool descriptions and schemas own self-contained tool usage and argument details; use the REST API reference only when a direct HTTP contract is needed.