IntegrityPulse FinOps
Stop your AI agents from hallucinating cloud costs. Get real pricing forecasts inside the conversation.
Power your agent
URL ของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
https://openclaw-finops.marywomack.workers.dev/mcpปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
claude mcp add --transport http io.github.maryadawson-code-openclaw-finops https://openclaw-finops.marywomack.workers.dev/mcpRun in a terminal.
{ "mcpServers": { "io.github.maryadawson-code-openclaw-finops": { "command": "npx", "args": [ "-y", "mcp-remote", "https://openclaw-finops.marywomack.workers.dev/mcp" ] } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดเซิร์ฟเวอร์นี้จะให้คุณลงชื่อเข้าใช้ตอนเชื่อมต่อ เอเจนต์ของคุณจะจัดการขั้นตอนนี้ให้
IntegrityPulse FinOps is a remote MCP server that gives AI coding agents accurate, real-time cloud deployment cost forecasts. Instead of your agent guessing that "an EC2 instance costs around $50/month," it calls a tool backed by a verified pricing matrix and returns a line-item breakdown.
One tool. Three providers. Zero hallucinations.
User: "What would it cost to run our API on AWS with an m5.large, a managed Postgres, and Redis?"
Agent (via IntegrityPulse FinOps):
| Service | Category | Hours | Est. Cost |
|----------------------------|----------|-------|-----------|
| m5.large | Compute | 730 | $70.08 |
| rds.postgres.db.m5.large | Database | 730 | $204.40 |
| elasticache.redis.t3.micro | Cache | 730 | $11.68 |
Total Estimated Monthly Cost: $286.16
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"integritypulse": {
"type": "streamable-http",
"url": "https://integritypulse.marywomack.workers.dev/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}
Add to your .cursor/mcp.json:
{
"mcpServers": {
"integritypulse": {
"type": "streamable-http",
"url": "https://integritypulse.marywomack.workers.dev/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}
curl -X POST https://integritypulse.marywomack.workers.dev/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "x-api-key: YOUR_API_KEY" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "forecast_deployment_cost",
"arguments": {
"provider": "AWS",
"services_to_add": [
{"service_name": "m5.large", "estimated_usage_hours": 730}
]
}
}
}'
forecast_deployment_costSupported services:
AI agents are moving from "write me code" to "deploy this for me." When an agent provisions infrastructure, cost accuracy isn't a nice-to-have -- it's a financial control.
The problem: LLMs hallucinate pricing. They confidently tell you an RDS instance costs "$15/month" when the real number is $204. When agents start executing deployments autonomously, these hallucinations become real invoices.
The solution: IntegrityPulse FinOps is a grounded pricing oracle that agents call as a tool. The pricing matrix is maintained, versioned, and deterministic. No generation, no guessing.
This server is also a reference implementation of Revenue-Gated MCP -- a pattern for monetizing MCP tools without breaking the agent experience.
Here's how it works:
x-api-key header.tier and monthly_usage_count in Supabase.isError: true:{
"jsonrpc": "2.0",
"id": 1,
"result": {
"content": [{
"type": "text",
"text": "IntegrityPulse FinOps Alert: Your free monthly tier (25/25 operations) has been exhausted. To generate this architectural cost forecast, please upgrade to the Pro tier here: https://billing.openclaw.com/upgrade. Once upgraded, ask me to retry."
}],
"isError": true
}
}
Why isError: true instead of HTTP 402/429?
Because the consumer is an LLM, not a browser. An HTTP error gets swallowed by the MCP transport layer and the user never sees it. By returning a tool result with isError: true, the upgrade CTA lands directly in the conversation where the user is already engaged. The agent reads it, surfaces it, and the user can act on it immediately. This is commerce at the point of intent.
When a user upgrades via the billing link, Stripe fires a checkout.session.completed webhook to /api/webhook/stripe. The server automatically:
FREE to PRO +-----------------+
Claude / Cursor | Cloudflare | +------------+
(MCP Client) -------->| Worker (Hono) |------>| Supabase |
POST | | | (users) |
/mcp | Revenue Gate | +------------+
| MCP Server |
| Stripe Webhook |------> Stripe API
+-----------------+
@modelcontextprotocol/sdk with Streamable HTTP transportx-api-key or Authorization: Bearer headergit clone https://github.com/maryadawson-code/integritypulse.git
cd integritypulse
npm install
# Configure secrets
cp .env.example .env
# Edit .env with your Supabase and Stripe credentials
# Local development
npx wrangler dev
# Deploy to Cloudflare Workers
npx wrangler secret put SUPABASE_URL
npx wrangler secret put SUPABASE_SERVICE_KEY
npx wrangler secret put STRIPE_SECRET_KEY
npx wrangler secret put STRIPE_WEBHOOK_SECRET
npx wrangler deploy
MIT
Verified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix.
{ "mcpServers": { "io.github.maryadawson-code-openclaw-finops": { "url": "https://openclaw-finops.marywomack.workers.dev/mcp", "headers": {} } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก http สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
OpenClaw FinOps เข้าถึงได้ผ่าน HTTP
ตรวจสอบล่าสุดเมื่อ 2026-11-09 Verified cloud cost forecasting for AI agents. AWS, GCP, Azure pricing matrix.