_ registry / mcp + a2a streamable-http · checked 1h ago

klag-docs

https://klag.dev

Registry code: a5e5140440ccde5d

api record

Read-only documentation for Klag, the Kafka consumer lag exporter. Search or read klag.dev pages, look up configuration keys and exported metrics. This server does not read any Kafka cluster — a self-hosted Klag instance exposes its own /mcp for that.

endpoint
https://klag.dev/mcp
door code
5c928b66e0a4e5e7
protocol
streamable-http ·2025-11-25
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is klag-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is klag-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does klag-docs have?
4 tools: search_klag_docs, get_klag_doc, get_klag_metric, get_klag_config.
Is klag-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.6%

latency
68ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1116 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search kafka lag exporter documentation
  • look up configuration variables
  • look up exported metrics
  • read a documentation page
takes → gives
text → text, data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
3 open 1 never probed 3 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_klag_doc reads open 11h ago

    Return the full markdown of a single klag.dev page by its URL path, e.g. "/metrics/lag-velocity/" or "/deployment/kubernetes/". Use after search_klag_docs when an excerpt is not enough. Call with no path to list every available page.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "path": {
          "type": "string",
          "description": "Page path such as \"/getting-started/quick-start/\". Omit to list all pages."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_klag_metric reads open 11h ago

    Look up the metrics Klag exports (klag.consumer.lag, klag.consumer.lag.velocity, klag.consumer.commit.staleness_seconds, klag.partition.under_replicated, ...), with their meaning and tags. Use when writing PromQL, dashboards, or alert rules against Klag. Call with no name to list every metric.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Metric name or fragment, e.g. \"lag.velocity\" or \"klag_consumer_lag\"."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • get_klag_config reads open 11h ago

    Look up Klag environment variables: name, default value, and what they do (KAFKA_BOOTSTRAP_SERVERS, METRICS_REPORTER, MCP_ENABLED, HOT_PARTITION_*, ...). Use when configuring or deploying Klag. Call with no name to list every key.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "name": {
          "type": "string",
          "description": "Env var name or prefix, e.g. \"METRICS_\" or \"KAFKA_CHUNK_COUNT\"."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • search_klag_docs reads unknown 9h ago

    Full-text search across klag.dev, the documentation for Klag (the Kafka consumer lag exporter). Use it to answer questions about how Klag works, how to deploy it, what a metric means, or how it compares to Burrow, KMinion, AKHQ, Redpanda Console, Cruise Control, Grafana, or Confluent Control Center. Returns ranked page excerpts with their URLs. This searches documentation only; it does not read any Kafka cluster.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 5,
          "maximum": 20,
          "minimum": 1,
          "description": "Maximum number of pages to return (1-20)."
        },
        "query": {
          "type": "string",
          "description": "Search terms, e.g. \"lag velocity\", \"helm values\", \"ACL permissions\"."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a5e5140440ccde5d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a5e5140440ccde5d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a5e5140440ccde5d/badge.svg)](https://brick.blue/agent/a5e5140440ccde5d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.