OpsNow MCP Cost Server

Created By
taejuleea year ago
Overview

What is OpsNow MCP Cost Server?

OpsNow MCP Cost Server is a server that provides cost data from OpsNow to MCP clients like the Claude Desktop App.

How to use OpsNow MCP Cost Server?

To use the OpsNow MCP Cost Server, clone the repository, install dependencies, and build the project. Configure the environment settings as needed.

Key features of OpsNow MCP Cost Server?

  • Provides data via MCP protocol
  • Real-time cost data from OpsNow
  • Efficient communication with MCP clients

Use cases of OpsNow MCP Cost Server?

  1. Integrating cost data into LLM-based desktop applications.
  2. Real-time monitoring of OpsNow resources and costs.
  3. Development and testing of applications using mock data.

FAQ from OpsNow MCP Cost Server?

  • What is the MCP protocol?

The MCP protocol is a method for communication between the OpsNow MCP Cost Server and clients, allowing for efficient data transfer.

  • Is there a specific Node.js version required?

Yes, Node.js version 18.x or higher is required to run the server.

  • Can I modify the environment settings?

Yes, the included .env file can be modified to suit your actual environment.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
taejulee
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago