pmcp

Created By
yshngga year ago
🚀 A MCP server for Prometheus.
Overview

what is pmcp?

pmcp is a MCP (Metric Collection Protocol) server designed for Prometheus, enabling efficient collection and management of metrics.

how to use pmcp?

To use pmcp, set up the server by following the installation instructions on the GitHub repository, and configure your Prometheus instance to scrape metrics from the pmcp server.

key features of pmcp?

  • Supports Metric Collection Protocol for seamless integration with Prometheus.
  • Easy setup and configuration for metric collection.
  • Provides a robust solution for monitoring applications and services.

use cases of pmcp?

  1. Collecting metrics from various applications for performance monitoring.
  2. Integrating with Prometheus for real-time data visualization.
  3. Enhancing observability in microservices architectures.

FAQ from pmcp?

  • What is the purpose of pmcp?

pmcp serves as a server for collecting metrics using the Metric Collection Protocol, specifically designed for use with Prometheus.

  • Is pmcp open source?

Yes! pmcp is open source and available under the Apache-2.0 license.

  • How can I contribute to pmcp?

Contributions are welcome! You can submit issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yshngg
Star
0
Language
-
License
Apache-2.0 license
Category
monitoring

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