OmniClaw MCP server
Enables autonomous agents to make controlled, policy-governed payments and interact with paid API endpoints using a financial policy engine.
Also known as omnuron/omniclaw
- Stars
- 570
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- May 29, 2026
- License
- MIT
What is OmniClaw MCP?
OmniClaw enables autonomous agents to make controlled, policy-governed payments and interact with paid API endpoints using a financial policy engine.
Summary generated from the project's README
About OmniClaw MCP server
Allowing autonomous agents to pay for services without granting them unrestricted wallet access is the primary function of OmniClaw. It provides a financial policy engine that manages budgets, approvals, and trust checks to ensure software stays within defined limits. Developers can integrate these capabilities into their applications using the Python buyer SDK or manage operations through a dedicated command line interface.
Users can operate the system in hybrid mode or x402-only Gateway mode by configuring environment variables such as OMNICLAW_PRIVATE_KEY and OMNICLAW_AGENT_TOKEN. The infrastructure supports direct transfers via circle_transfer and handles paid API payments through the x402 flow. It includes specific tools like inspect-x402 to examine endpoints and can-pay to verify financial readiness. By utilizing ledger controls and idempotency, the server ensures that agent transactions remain auditable and controlled during execution.
What you can do with it
- 1Verify agent payment capabilityCheck if an agent has the necessary permissions and funds to complete a specific transaction.
- 2Execute controlled API paymentsPay for an external paid endpoint using the standard x402 buyer flow.
- 3Inspect paid service endpointsExamine a recipient URL to understand the requirements for an x402 payment.
- 4Manage agent budgets via codeIntegrate payment logic directly into a Python application using the provided SDK.
Written from the project's README. Every use case is checked against a quote from it.
Configuration
OMNICLAW_SERVER_URLOMNICLAW_TOKEN
| Name | Description | |
|---|---|---|
| OMNICLAW_SERVER_URL | — | |
| OMNICLAW_TOKEN | — |
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableomnuron/omniclaw is public and reachablegithub.com/omnuron/omniclaw ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-05-29github.com/omnuron/omniclaw ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOmniClaw
Policy-controlled payment infrastructure for agent buyers.
OmniClaw core is focused on one job: letting agents and applications pay through controlled, auditable rails without giving software unrestricted wallet authority.
Product Boundary
| Product | Directory | Owns |
|---|---|---|
| OmniClaw core | src/omniclaw |
buyer SDK, policy engine, wallet/payment routing, x402 buyer execution, Gateway buyer readiness |
Core should not include recipient-side paid endpoint hosting or settlement service code.
Core Capabilities
- Financial Policy Engine for budgets, approvals, trust checks, and execution control
- Python buyer SDK via
OmniClaw().pay(...) - Agent buyer CLI via
omniclaw-cli pay,inspect-x402, andcan-pay - Circle Gateway buyer funding/readiness helpers
- Standard x402 buyer flow for paying external paid endpoints
- Ledger, idempotency, simulation, and payment-intent controls
Core Quickstart
Install:
pip install omniclaw
Start the policy engine:
cp .env.example .env
# Hybrid mode (default): leave OMNICLAW_BUYER_MODE=hybrid and fill CIRCLE_API_KEY,
# ENTITY_SECRET, OMNICLAW_PRIVATE_KEY, OMNICLAW_AGENT_TOKEN, OMNICLAW_OWNER_TOKEN,
# OMNICLAW_NETWORK, and OMNICLAW_RPC_URL.
# x402-only Gateway mode: set OMNICLAW_BUYER_MODE=x402, leave CIRCLE_API_KEY and
# ENTITY_SECRET empty unless you need optional Circle Gateway API helpers, and fill
# OMNICLAW_PRIVATE_KEY, OMNICLAW_AGENT_TOKEN, OMNICLAW_OWNER_TOKEN,
# OMNICLAW_NETWORK, and OMNICLAW_RPC_URL.
mkdir -p examples/agent/buyer/runtime
cp examples/agent/buyer/policy.example.json examples/agent/buyer/runtime/policy.json
# Edit examples/agent/buyer/runtime/policy.json so the token matches OMNICLAW_AGENT_TOKEN.
docker compose -f examples/agent/buyer/docker-compose.yml --env-file .env up --build
The policy file is stable configuration. Generated wallet state is written separately
to examples/agent/buyer/runtime/wallet-state.json.
Buyer-facing policy rails are:
circle_transferfor direct Circle Developer Wallet transfers.x402for paid API payments. OmniClaw chooses Gateway nanopayment or the standard x402 payment path internally based on seller accepts, buyer config, and Gateway balance.
Configure the buyer CLI:
set -a; source .env; set +a
export OMNICLAW_SERVER_URL="http://127.0.0.1:9091"
export OMNICLAW_TOKEN="$OMNICLAW_AGENT_TOKEN"
Inspect and pay an x402 endpoint:
omniclaw-cli inspect-x402 --recipient "http://127.0.0.1:4023/compute?size=20"
omniclaw-cli pay --recipient "http://127.0.0.1:4023/compute?size=20" --amount 0.10 --idempotency-key job-123
Development
Run core tests:
uv run pytest
OmniClaw MCP questions
How do I install OmniClaw?
You can install the package using pip with the command pip install omniclaw.
What are the different buyer-facing policy rails?
The rails include circle_transfer for direct Circle Developer Wallet transfers and x402 for paid API payments.