How do AI agents use Blockfrost through Open Connector?

Your user connects Blockfrost once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Blockfrost tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a Blockfrost MCP server?

Yes. Open Connector can serve Blockfrost as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Blockfrost actions with credentials injected server-side.

Where do Blockfrost credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Blockfrost integration

Blockfrost integration for AI agents.

Blockfrost integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Blockfrost tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real Blockfrost actions, managed and audited.

Your user connects Blockfrost once; your agent can then query Cardano blockchain, IPFS, network, governance, transaction, asset, pool, and account data through Blockfrost — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants Blockfrost access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported Blockfrost tools.

122 tools are generated from the published Blockfrost catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 122 tools. All published catalog entries are included in this page's server-rendered HTML.

Root endpoint: Root endpoint has no other function than to point end users to documentation.; Health
Specific account address: Obtain information about a specific stake account.; Cardano » Accounts
Account associated addresses: Obtain information about the addresses of a specific account. Be careful, as an account could be part of a mangled address and does not necessarily mean the addresses are owned by user as the account.; Cardano » Accounts
Assets associated with the account addresses: Obtain information about assets associated with addresses of a specific account. Be careful, as an account could be part of a mangled address and does not necessarily mean the addresses are owned by user as the account.; Cardano » Accounts
Detailed information about account associated addresses: Obtain summed details about all addresses associated with a given account. Be careful, as an account could be part of a mangled address and does not necessarily mean the addresses are owned by user as the account.; Cardano » Accounts
Account delegation history: Obtain information about the delegation of a specific account.; Cardano » Accounts
Account history: Obtain information about the history of a specific account.; Cardano » Accounts
Account MIR history: Obtain information about the MIRs of a specific account.; Cardano » Accounts
Account registration history: Obtain information about the registrations and deregistrations of a specific account.; Cardano » Accounts
Account reward history: Obtain information about the reward history of a specific account.; Cardano » Accounts
Account transactions: Transactions associated with the stake address.; Cardano » Accounts
Account UTXOs: UTXOs associated with the account.; Cardano » Accounts
Account withdrawal history: Obtain information about the withdrawals of a specific account.; Cardano » Accounts
Specific address: Obtain information about a specific address.; Cardano » Addresses
Extended information of a specific address: Obtain extended information about a specific address.; Cardano » Addresses
Address details: Obtain details about an address.; Cardano » Addresses
Address transactions: Transactions on the address.; Cardano » Addresses
Address txs: Transactions on the address.; Cardano » Addresses
Address UTXOs: UTXOs of the address.; Cardano » Addresses
Address UTXOs of a given asset: UTXOs of the address.; Cardano » Addresses
Assets: List of assets. If an asset is completely burned, it will stay on the list with quantity 0 (order of assets is immutable).; Cardano » Assets
Specific asset: Information about a specific asset; Cardano » Assets
Asset addresses: List of a addresses containing a specific asset; Cardano » Assets
Asset history: History of a specific asset; Cardano » Assets
Asset transactions: List of a specific asset transactions; Cardano » Assets
Asset txs: List of a specific asset transactions; Cardano » Assets
Assets of a specific policy: List of asset minted under a specific policy; Cardano » Assets
Specific block in a slot in an epoch: Return the content of a requested block for a specific slot in an epoch.; Cardano » Blocks
Specific block: Return the content of a requested block.; Cardano » Blocks
Addresses affected in a specific block: Return list of addresses affected in the specified block with additional information, sorted by the bech32 address, ascending.; Cardano » Blocks
Listing of next blocks: Return the list of blocks following a specific block.; Cardano » Blocks
Listing of previous blocks: Return the list of blocks preceding a specific block.; Cardano » Blocks
Block transactions: Return the transactions within the block.; Cardano » Blocks
Block transactions with CBOR data: Return the transactions within the block, including CBOR representations.; Cardano » Blocks
Latest block: Return the latest block available to the backends, also known as the tip of the blockchain.; Cardano » Blocks
Latest block transactions: Return the transactions within the latest block.; Cardano » Blocks
Latest block transactions with CBOR data: Return the transactions within the latest block, including CBOR representations.; Cardano » Blocks
Specific block in a slot: Return the content of a requested block for a specific slot.; Cardano » Blocks
Latest epoch: Return the information about the latest, therefore current, epoch.; Cardano » Epochs
Latest epoch protocol parameters: Return the protocol parameters for the latest epoch.; Cardano » Epochs
Specific epoch: Return the content of the requested epoch.; Cardano » Epochs
Block distribution: Return the blocks minted for the epoch specified.; Cardano » Epochs
Block distribution by pool: Return the block minted for the epoch specified by stake pool.; Cardano » Epochs
Listing of next epochs: Return the list of epochs following a specific epoch.; Cardano » Epochs
Protocol parameters: Return the protocol parameters for the epoch specified.; Cardano » Epochs
Listing of previous epochs: Return the list of epochs preceding a specific epoch.; Cardano » Epochs
Stake distribution: Return the active stake distribution for the specified epoch.; Cardano » Epochs
Stake distribution by pool: Return the active stake distribution for the epoch specified by stake pool.; Cardano » Epochs
Blockchain genesis: Return the information about blockchain genesis.; Cardano » Ledger
Constitutional committee: Information about the currently active constitutional committee When `is_dissolved` is `true`, the committee has been removed by an enacted `NoConfidence` governance action; `quorum` and `members` still describe the last seated committee for historical reference.; Cardano » Governance
Constitutional committee member votes: Votes cast under a given constitutional committee credential. Accepts both the CIP-129 hot bech32 (`cc_hot1...`) and the cold bech32 (`cc_cold1...`). When queried by a cold credential, this returns votes cast by any hot key that the cold key has authorized over time (so the result aggregates across hot-key rotations).; Cardano » Governance
Constitutional committee votes: History of all votes cast by constitutional committee members across all committees (current and past). Not scoped to the currently active committee.; Cardano » Governance
Delegate Representatives (DReps): Return the information about Delegate Representatives (DReps); Cardano » Governance
Specific DRep: DRep information.; Cardano » Governance
DRep delegators: List of Drep delegators.; Cardano » Governance
DRep metadata: DRep metadata information.; Cardano » Governance
DRep updates: List of certificate updates to the DRep.; Cardano » Governance
DRep votes: History of Drep votes.; Cardano » Governance
Proposals: Return the information about Proposals; Cardano » Governance
GovActionID proposal: Proposal information.; Cardano » Governance
GovActionID proposal metadata: Proposal metadata information.; Cardano » Governance
GovActionID Proposal parameters: Parameters proposal details.; Cardano » Governance
GovActionID Proposal votes: History of Proposal votes.; Cardano » Governance
GovActionID Proposal withdrawals: Withdrawal proposal details.; Cardano » Governance
Specific proposal: Proposal information.; Cardano » Governance
Specific proposal metadata: Proposal metadata information. If this endpoint returns `404` or empty metadata for a known proposal, the off-chain metadata could not be fetched (e.g. unreachable URL or hash mismatch). Use the [`/governance/proposals/{gov_action_id}/metadata`](#tag/cardano--governance/GET/governance/proposals/{gov_action_id}/metadata) variant instead — it always returns the anchor `url` and `hash` along with an `error` object describing the fetch failure, so you can retrieve the metadata manually if needed.; Cardano » Governance
Specific parameters proposal: Parameters proposal details.; Cardano » Governance
Proposal votes: History of Proposal votes.; Cardano » Governance
Specific withdrawals proposal: Withdrawal proposal details.; Cardano » Governance
Backend health status: Return backend status as a boolean. Your application should handle situations when backend for the given chain is unavailable.; Health
Current backend time: This endpoint provides the current UNIX time. Your application might use this to verify if the client clock is not out of sync.; Health
Mempool: Return transactions that are currently stored in Blockfrost mempool, waiting to be included in a newly minted block. Shows only transactions submitted via Blockfrost.io. Hosted Endpoint only available for hosted variant. ; Cardano » Mempool
Mempool by address: List of mempool transactions where at least one of the transaction inputs or outputs belongs to the address. Shows only transactions submitted via Blockfrost.io. Hosted Endpoint only available for hosted variant. ; Cardano » Mempool
Specific transaction in the mempool: Return content of the requested transaction. Hosted Endpoint only available for hosted variant. ; Cardano » Mempool
Transaction metadata labels: List of all used transaction metadata labels.; Cardano » Metadata
Transaction metadata content in JSON: Transaction metadata per label.; Cardano » Metadata
Transaction metadata content in CBOR: Transaction metadata per label.; Cardano » Metadata
Blockfrost usage metrics: History of your Blockfrost usage metrics in the past 30 days.; Metrics
Blockfrost endpoint usage metrics: History of your Blockfrost usage metrics per endpoint in the past 30 days.; Metrics
Network information: Return detailed network information.; Cardano » Network
Query summary of blockchain eras: Returns start and end of each era along with parameters that can vary between hard forks.; Cardano » Network
Specific nut.link address: List metadata about specific address; Nut.link
List of tickers of an oracle: List of records of a specific oracle; Nut.link
Specific ticker for an address: List of records of a specific ticker; Nut.link
Specific ticker: List of records of a specific ticker; Nut.link
List of stake pools: List of registered stake pools.; Cardano » Pools
List of stake pools with additional information: List of registered stake pools with additional information.; Cardano » Pools
Specific stake pool: Pool information.; Cardano » Pools
Stake pool blocks: List of stake pools blocks.; Cardano » Pools
Stake pool delegators: List of current stake pools delegators.; Cardano » Pools
Stake pool history: History of stake pool parameters over epochs.; Cardano » Pools
Stake pool metadata: Stake pool registration metadata.; Cardano » Pools
Stake pool relays: Relays of a stake pool.; Cardano » Pools
Stake pool updates: List of certificate updates to the stake pool.; Cardano » Pools
Stake pool votes: History of stake pools votes.; Cardano » Pools
List of retired stake pools: List of already retired pools.; Cardano » Pools
List of retiring stake pools: List of stake pools retiring in the upcoming epochs; Cardano » Pools
Scripts: List of scripts.; Cardano » Scripts
Datum value: Query JSON value of a datum by its hash; Cardano » Scripts
Datum CBOR value: Query CBOR serialised datum by its hash; Cardano » Scripts
Specific script: Information about a specific script; Cardano » Scripts
Script CBOR: CBOR representation of a `plutus` script; Cardano » Scripts
Script JSON: JSON representation of a `timelock` script; Cardano » Scripts
Redeemers of a specific script: List of redeemers of a specific script; Cardano » Scripts
UTXOs holding the script as a reference script: List of UTXOs that hold the given script as a reference script (CIP-33). These outputs can be used as reference inputs (CIP-31) in a transaction to execute the script without including its full bytes. A single script may be held by multiple UTXOs, potentially at different addresses.; Cardano » Scripts
Specific transaction: Return content of the requested transaction.; Cardano » Transactions
Transaction CBOR: Obtain the CBOR serialized transaction; Cardano » Transactions
Transaction delegation certificates: Obtain information about delegation certificates of a specific transaction.; Cardano » Transactions
Transaction metadata: Obtain the transaction metadata.; Cardano » Transactions
Transaction metadata in CBOR: Obtain the transaction metadata in CBOR.; Cardano » Transactions
Transaction MIRs: Obtain information about Move Instantaneous Rewards (MIRs) of a specific transaction.; Cardano » Transactions
Transaction stake pool retirement certificates: Obtain information about stake pool retirements within a specific transaction.; Cardano » Transactions
Transaction stake pool registration and update certificates: Obtain information about stake pool registration and update certificates of a specific transaction.; Cardano » Transactions
Transaction redeemers: Obtain the transaction redeemers.; Cardano » Transactions
Transaction required signers: Obtain the extra transaction witnesses.; Cardano » Transactions
Transaction stake addresses certificates: Obtain information about (de)registration of stake addresses within a transaction.; Cardano » Transactions
Transaction UTXOs: Return the inputs and UTXOs of the specific transaction.; Cardano » Transactions
Transaction withdrawal: Obtain information about withdrawals of a specific transaction.; Cardano » Transactions
Derive an address: Derive Shelley address from an xpub; Cardano » Utilities
Submit a transaction: Submit an already serialized transaction to the network. Hosted Endpoint only available for hosted variant. ; Cardano » Transactions
Submit a transaction for execution units evaluation: Submit an already serialized transaction to evaluate how much execution units it requires. Hosted Endpoint only available for hosted variant. ; Cardano » Utilities
Submit a transaction for execution units evaluation (additional UTXO set): Submit a JSON payload with transaction CBOR and additional UTXO set to evaluate how much execution units it requires. Hosted Endpoint only available for hosted variant. ; Cardano » Utilities

FAQ

Blockfrost integration, answered

How do AI agents use Blockfrost through Open Connector?: Your user connects Blockfrost once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Blockfrost tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a Blockfrost MCP server?: Yes. Open Connector can serve Blockfrost as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Blockfrost actions with credentials injected server-side.
Where do Blockfrost credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents Blockfrost — keep the keys.

Open source, self-hostable, with Blockfrost credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →