Usage-based monetization gateway for MCP servers using MNEE.
Meter makes payment a first-class primitive for MCP. It allows tool providers to charge agents per tool call and receive settlement automatically in MNEE, without building custom billing, auth, or accounting systems.
While building agent systems, I kept running into the same failure point: agents can call tools easily, but the moment money is involved, everything breaks.
Tool developers are forced to build custom billing logic, access control and retries, accounting and reconciliation, and payment verification. Agents have no reliable way to know pricing or whether payment is enforced fairly.
Meter bridges this gap by making monetization native to MCP instead of something bolted on later.
Meter turns any MCP server into a paid endpoint with a simple, enforceable flow:
- Register an MCP server with Meter
- Define per-tool pricing in cents
- Provide a public wallet address
- Agents include payment proof with each tool call
- Meter verifies payment first, then routes the request
- Settlement goes directly to the provider wallet in MNEE
No custody. No billing stack. No MCP changes required.
Meter acts as a lightweight gateway in front of existing MCP servers. The MCP server itself remains unchanged. Meter enforces proof-gated execution: payments are verified before tool execution, and all payment events are recorded and analyzable.
Core components:
- Gateway API for MCP routing
- Payment verification using MNEE SDK
- Persistent payment and usage storage
- Analytics dashboard for providers
Payment model:
- Pricing defined per tool
- Agents pay per tool call in MNEE
- Verification happens before execution
- Settlement is non-custodial and direct
The rule is intentionally simple: pay first, then execute. This makes agent behavior predictable and easy to reason about.
Meter includes a real-time analytics dashboard showing per-tool usage, revenue over time, success and failure rates, and live wallet balance fetched from chain data. All numbers are derived from real payment and execution events.
Frontend: Next.js, Tailwind CSS, TypeScript
Backend: Node.js, Express, Prisma ORM, PostgreSQL
Agent and MCP: LangChain MCP tooling, MCP protocol-compatible routing
Payments: MNEE SDK, Ethereum-based settlement
backend/ Gateway API and payment enforcement
frontend/my-app/ Provider dashboard and analytics UI
langchain-agent/ Demo agent showing paid tool calls
mcp-server/ Example MCP server used for demo
Prerequisites: Node.js 18+, PostgreSQL, MNEE wallet and testnet funds
# Install dependencies
npm install
# Setup environment
cp .env.example .env
# Fill in database and wallet configuration
# Run backend
cd backend
npm run dev
# Run frontend
cd frontend/my-app
npm run devA working demo video is included in the Devpost submission showing MCP server registration, tool pricing configuration, agent payment and execution, and live analytics updating after calls.
- Paid MCP tools and APIs
- Agent-to-agent commerce
- Usage-based AI infrastructure
- Data and compute marketplaces
- Autonomous service monetization
This is an early prototype built during a hackathon with intentional tradeoffs to keep the core payment primitive correct:
- Single provider focus
- Limited pricing models
- Manual deployment steps
Planned improvements include multi-provider support, richer agent-level analytics, exportable usage and billing data, on-chain verification hooks, and fully self-service onboarding.
Long term, I see Meter as core infrastructure for agent-to-agent commerce.
MIT License