Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"integritypulse": {
"url": "https://integritypulse.marywomack.workers.dev/mcp",
"type": "streamable-http",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Stop your AI agents from hallucinating cloud costs. Get real pricing forecasts inside the conversation.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Wrangler affected by OS Command Injection in `wrangler pages deploy`
**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl
Arbitrary remote code execution within `wrangler dev` Workers sandbox
### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability
Arbitrary remote file read in Wrangler dev server
### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr
Cloudflare Wrangler directory traversal vulnerability
### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud / finance
MCP Server for GCP environment for interacting with various Observability APIs.
⚡ A Simple / Speedy / Secure Link Shortener with Analytics, 100% run on Cloudflare.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol server for building an investor agent
MCP Security Weekly
Get CVE alerts and security updates for io.github.maryadawson-code/integritypulse and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Stop your AI agents from hallucinating cloud costs. Get real pricing forecasts inside the conversation.
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_cost| Parameter | Type | Description |
|---|---|---|
provider | "AWS" | "GCP" | "AZURE" | Cloud provider to price against |
services_to_add | Array<{ service_name, estimated_usage_hours }> | Services to include in the forecast |
Supported services:
| AWS | GCP | Azure |
|---|---|---|
| t3.micro, t3.medium, m5.large | e2-micro, e2-medium, n2-standard-2 | B1s, B2s, D2s_v3 |
| rds.postgres.db.t3.micro, rds.postgres.db.m5.large | cloudsql.postgres.db-custom-1-3840, cloudsql.postgres.db-custom-4-15360 | postgresql.flexible.b1ms |
| elasticache.redis.t3.micro | memorystore.redis.1gb | |
| s3.standard.1tb |
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: