4,500+ servers built on MCP Fusion
Vinkius

Arweave MCP. Query, check, and update data on the permaweb.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Arweave MCP on Cursor AI Code Editor MCP Client Arweave MCP on Claude Desktop App MCP Integration Arweave MCP on OpenAI Agents SDK MCP Compatible Arweave MCP on Visual Studio Code MCP Extension Client Arweave MCP on GitHub Copilot AI Agent MCP Integration Arweave MCP on Google Gemini AI MCP Integration Arweave MCP on Lovable AI Development MCP Client Arweave MCP on Mistral AI Agents MCP Compatible Arweave MCP on Amazon AWS Bedrock MCP Support

Just plug in your AI agents and start using Vinkius.

Arweave connects your AI agent directly to the permaweb network. It lets you check wallet balances, calculate storage costs in Winstons, inspect transaction statuses, and execute complex GraphQL queries against permanent data records.

You can read network info (like height and peers) or submit new transactions without leaving your IDE.

What your AI agents can do

Get block by hash

Retrieves a specific block record using its unique hash identifier.

Get block by height

Pulls all data for a block based on its sequential height number.

Get network info

Gathers the current operational status and metadata of the entire Arweave network.

+ 10 more capabilities included
Monitor Network Status

Get real-time metrics like network height, block hashes, and a list of connected peers using get_network_info and get_peers.

Inspect Transaction Lifecycles

Retrieve transaction details by ID, check its current status (pending/confirmed), or get the raw data associated with it.

Check Wallet Balances and History

Query a wallet's current balance in Winstons or pull the ID of its most recent transaction using get_wallet_balance.

Calculate Storage Costs

Determine the cost, measured in Winstons, required to permanently store a specific amount of data on Arweave via get_storage_price.

Execute Deep Data Searches

Run complex GraphQL queries to search for structured data or tags across the entire permaweb dataset using query_graphql.

Write and Submit Records

Initiate state changes by submitting a brand new transaction to the network via submit_transaction.

Supported MCP Clients

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients
Free for Subscribers

Waiting for input…

AI Agent

Arweave MCP Server: 13 Tools for Ledger Access

These tools allow your AI agent to perform every major action on the Arweave network, from reading block hashes to submitting new transactions.

get019ea5e0

get block by hash

Retrieves a specific block record using its unique hash identifier.

get019ea5e0

get block by height

Pulls all data for a block based on its sequential height number.

get019ea5e0

get network info

Gathers the current operational status and metadata of the entire Arweave network.

get019ea5e0

get peers

Lists all peer addresses that the connected node knows about, useful for debugging connections.

get019ea5e0

get storage price

Calculates and returns the specific cost in Winstons required to store a given amount of data.

get019ea5e0

get transaction

Retrieves all metadata about a transaction using its unique ID.

get019ea5e0

get transaction data

Extracts and returns the actual content payload associated with a specific transaction.

get019ea5e0

get transaction offset

Gets the precise byte offset and size of the data contained within a transaction record.

get019ea5e0

get transaction status

Checks and reports the current state of a transaction (e.g., pending, confirmed).

get019ea5e0

get wallet balance

Provides the current balance for any given wallet address in Winstons.

get019ea5e0

get wallet last tx

Finds and returns the ID of the last transaction ever sent by a specific wallet address.

query019ea5e0

query graphql

Executes any custom GraphQL query against the Arweave network endpoint to pull targeted data.

submit019ea5e0

submit transaction

Creates and sends a new state-changing transaction record onto the live network.

Choose How to Get Started

Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.

Build Your Own

Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.

  • Import from OpenAPI, Swagger, or YAML specs
  • Create Agent Skills with progressive disclosure
  • Deploy to edge with MCPFusion framework
  • Built in DLP, auth, and compliance on every call
  • Real time usage dashboard and cost metering
  • Publish to catalog or keep private
Start building

Make Your AI Do More

Start with Arweave, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.

  • Use this MCP plus 4,700+ others, all in one place
  • Add new capabilities to your AI anytime you want
  • Every connection is secured and compliant automatically
  • Track usage and costs across all your servers
  • Works with Claude, ChatGPT, Cursor, and more
  • New servers added to the catalog every week

What you can do with this MCP connector

You hook your AI agent right into the Arweave permaweb network using this MCP Server. It lets you talk to permanent data records, checking everything from wallet balances and storage costs to deep transaction histories—all without leaving your chat window or IDE. You're getting direct, programmatic access to the whole blockweave ecosystem.

Monitoring Network Status: Need to know what the network’s doing? Use get_network_info to grab current operational metadata like the total network height. If you want a deeper look, get_peers lists every connected node address your agent knows about, which is clutch for debugging connectivity issues. You can also nail down specific block records by calling get_block_by_height or pinpointing one using its unique hash with get_block_by_hash.

These tools keep you totally current on the network's real-time state.

Handling Wallet Accounts: Wanna check where your crypto is? Run get_wallet_balance to see the current Winston balance for any address. If you just wanna know what that wallet did last, get_wallet_last_tx pulls the ID of its most recent transaction. These checks give you a quick pulse on an account's activity.

Inspecting Transactions: When tracking down transactions, your agent can grab all the high-level details using get_transaction by its unique ID. It also lets you check if that deal went through by calling get_transaction_status, which reports whether it’s pending or confirmed. Need to see what data was actually moved? Use get_transaction_data for the payload, or get_transaction_offset to get the precise byte location and size of the record within the transaction.

Calculating Costs: Storing data permanently ain't cheap, so you gotta know the price tag. Run get_storage_price to calculate exactly how many Winstons it’ll cost to store a specific amount of data on Arweave. It keeps your budget locked down before you commit.

Deep Data Searches and Writes: For complex research, don't waste time digging through dashboards; just run query_graphql. This lets your agent execute any custom GraphQL query across the entire permaweb dataset, pulling structured data or specific tags from anywhere on the network. When it’s time to make a change—you gotta write something new—submit_transaction sends that brand-new state-changing record live onto the chain.

You can also retrieve all metadata about a transaction using get_transaction, making sure you've got every piece of info before submitting or checking on anything.

How Arweave MCP Works

  1. 1 Your AI client sends a request (e.g., 'What's the balance for 3pD7...x9A?') specifying the desired tool.
  2. 2 The MCP Server executes that tool call, interacts with the Arweave network endpoint, and pulls back the raw data.
  3. 3 We format the result and give it back to your client in plain text. You just read it.

The bottom line is you talk to your agent like a teammate and it handles all the complex API calls to Arweave for you.

Who Is Arweave MCP For?

This is for developers, researchers, and crypto users who need constant, verified access to permanent ledger data. If you're tired of switching between a terminal CLI, an explorer website, and your IDE just to check one status code, this saves time.

Web3 Developer

Building applications that need to verify transaction confirmations or read network state without writing boilerplate API wrapper code.

Data Analyst (Blockchain)

Extracting specific, structured insights from the permaweb using GraphQL queries and analyzing data tags.

Crypto Researcher

Monitoring wallet activity or calculating storage costs for large-scale permanent file deployments.

What Changes When You Connect

  • See real-time network status with get_network_info. You instantly know if the node is up or what height it's at. No more checking multiple explorer dashboards just to confirm basic operational health.
  • Manage transaction lifecycles end-to-end. Need to debug a failed write? Use get_transaction_status first, then check the raw data with get_transaction_data before assuming anything went wrong.
  • Keep track of finances without context switching. You can query any wallet's balance (get_wallet_balance) and see its last activity (get_wallet_last_tx), all in one chat prompt. It’s fast.
  • Know your costs upfront. Before you commit to storing data, use get_storage_price. It calculates the exact Winston cost for a given byte size—no guesswork involved.
  • Access deep network insights with query_graphql. This lets you run highly specific searches across permanent tags and records that simple balance checks can't touch.
  • Execute state changes safely. Use submit_transaction to write new data, knowing the system validated the environment first by checking the network status.

Real-World Use Cases

01

Debugging a failed deployment

A developer deployed an NFT but it didn't appear in the explorer. Instead of spending time jumping between logs and APIs, they ask their agent: 'What is the status and data for transaction 0xABC...' The agent runs get_transaction then get_transaction_status, confirming if the TX was pending or failed outright.

02

Auditing historical records

A researcher needs to find all permanent documents tagged 'Q3-2025' that mention a specific ID. They don't run multiple queries; they use query_graphql with the exact search parameters, getting a targeted list of results immediately.

03

Pre-calculating storage budget

A startup is planning to upload 1GB of archival data. They ask their agent: 'How much does 1,073,741,824 bytes cost on Arweave?' The server runs get_storage_price and gives an immediate Winston figure, letting the team budget accurately.

04

Verifying a new record submission

A system needs to write a signed agreement. It first checks current network health using get_network_info, then uses submit_transaction to send the data, and finally runs get_transaction_status to confirm it went through successfully.

The Tradeoffs

Treating GraphQL as a replacement for status checks

Asking only 'Give me all transaction details' using a vague query. This overloads the query and misses simple, critical state info like whether it was confirmed or not.

Always check the basics first. Use get_network_info to confirm the environment is stable. Then, run get_transaction_status on the ID before using query_graphql for deep data dives.

Guessing transaction IDs

Simply asking 'What happened with my wallet?' without specifying a timeframe or target address. The agent can't read your mind.

Be precise. Start by getting the last activity ID using get_wallet_last_tx. Then pass that ID to get_transaction for full details.

Ignoring required data size

Assuming you can store any data without knowing the cost. You just type 'Store this massive file.' and get an error.

Always run get_storage_price first, providing the exact byte count. This gives you the hard number of Winstons needed to proceed.

When It Fits, When It Doesn't

Use this server if your job requires interacting with verifiable, permanent ledger data (the permaweb). Specifically, if you need to read transaction state (get_transaction_status), calculate storage economics (get_storage_price), or query structured records via GraphQL. It's built for the full lifecycle: check environment -> read state -> write change.

Don't use this server if all you need is ephemeral data, like a basic REST API call to fetch an item by simple ID that doesn't relate to blockchain permanence. For those cases, another specialized tool might be better. But for anything touching the ledger—balances, storage costs, transaction history—this is your primary source of truth.

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Arweave. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

VINKIUS INFRASTRUCTURE

Cloud Hosted

Managed infra

V8 Isolated

Sandboxed per request

Zero-Trust Proxy

No stored credentials

DLP Enforced

Policy on every call

GDPR Compliant

EU data residency

Token Compression

~60% cost reduction

How we secure it →

Works with Claude, ChatGPT, Cursor, and more

The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.

This server provides 13 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.

Available Capabilities

get_block_by_hash get_block_by_height get_network_info get_peers get_storage_price get_transaction get_transaction_data get_transaction_offset get_transaction_status get_wallet_balance get_wallet_last_tx query_graphql submit_transaction

Checking a node's status used to mean 5 tabs and 3 different APIs.

Today, if you need to know the Arweave network height or check the list of active peers, you’re usually forced into an explorer site. You click 'Network Info,' then maybe a second pop-up for 'Peers.' It's slow, it requires context switching, and you end up copying data just to paste it somewhere else.

With this MCP server, you tell your agent: 'What is the current network status?' The agent runs `get_network_info` and gives you the height, hash, and node version instantly. You get the answer in one clean paragraph. Period.

Arweave MCP Server lets you manage your data lifecycle with simple commands.

Before this tool, figuring out if a transaction was successful meant running several separate checks: first `get_transaction` to get the metadata, then checking an external site for confirmation. It was guesswork and manual verification every time.

Now you just ask your agent about the TX ID. It runs `get_transaction_status`, gives you 'Confirmed,' and if needed, it pulls the full content with `get_transaction_data`. You get a definitive answer in one go.

Common Questions About Arweave MCP

How do I check my Arweave wallet balance using get_wallet_balance? +

You provide the target address. The server uses get_wallet_balance and returns your current holdings in Winstons, usually with an AR equivalent for comparison.

Is query_graphql better than getting transaction data? +

They serve different purposes. Use query_graphql when you need to search or pull structured metadata across many records. Use get_transaction_data when you know the specific TX ID and just want its raw payload.

What if I submit a transaction that fails? +

If submit_transaction sends data but it fails, run get_transaction_status immediately afterward using the returned ID. This confirms the failure and helps diagnose why it didn't process.

How do I check the cost of storing a file? +

Simply ask for the storage price, specifying the size in bytes or MB. The server uses get_storage_price to calculate the exact Winston fee before you commit.

How do I check the current operational status of the network using `get_network_info`? +

It fetches real-time details about the Arweave network. This tool gives you the current height, block hash, and overall node version so you know if the system is running normally.

What data can I retrieve for a specific block using `get_block_by_hash`? +

You get the full metadata package for that exact block. It pulls structured details—like all included transactions and timestamps—that you can't find through just querying general network information.

How do I check a wallet’s recent activity using `get_wallet_last_tx`? +

It returns the ID of the most recent transaction associated with that address. This lets you track history quickly without having to query every single past movement.

What are the necessary steps when I use `submit_transaction`? +

The tool requires sufficient Winstons and all necessary payload data before submission. Once called, it sends your permanent record request directly to the network queue.

More in this category

You might also like

Built & Managed by Vinkius 30s setup 13 tools

We've already built the connector for Arweave. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 13 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.