kpi-depot
Registry code: 8414160337220091
KPI Depot provides definitions, formulas, and industry benchmark data for 20,000+ corporate KPIs. Workflow: search_kpis to find a KPI's kpi_id (slug), get_kpi for full detail, get_benchmarks for benchmark data. Each benchmark response includes a citation URL.
- endpoint
- https://kpidepot.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is kpi-depot live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is kpi-depot free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does kpi-depot have?
- 3 tools: get_kpi, search_kpis, get_benchmarks.
- Is kpi-depot 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.
90 days 99%· all time 99%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search corporate kpis
- get a kpi definition and formula
- get industry benchmarks for a kpi
- takes → gives
- text → data
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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_benchmarks reads auth-required 17h ago
Benchmark data for a single KPI (one kpi_id per call): benchmark values with descriptive metadata (industry, geography, time period, sample size) and full source attribution (source name, URL, excerpt, and comments). Each response includes a citation URL.
{ "type": "object", "required": [ "kpi_id" ], "properties": { "kpi_id": { "type": "string", "description": "The KPI slug from search_kpis. Single value only — no arrays or wildcards." } } }arguments 12 linesget_kpi reads unknown 17h ago
Full intelligence for a single KPI: definition, standard formula, common pitfalls, improvement levers, related KPIs, the KPI groups it belongs to, and metadata about its available benchmarks (benchmark values themselves come from get_benchmarks). Takes the kpi_id (slug) returned by search_kpis.
{ "type": "object", "required": [ "kpi_id" ], "properties": { "kpi_id": { "type": "string", "description": "The KPI slug from search_kpis, e.g. \"asset-maintenance-ratio\"." } } }arguments 12 linessearch_kpis reads unknown 17h ago
Search KPI Depot's library of 20,000+ corporate KPIs by keyword, with optional corporate-function and industry filters. Returns up to 10 relevance-ranked matches, each with a one-line definition, its benchmark count, and the KPI's page URL. When no KPI matches the full query, the response also includes close_matches (nearest KPIs, with which query words each missed) and related_groups (KPI groups whose names match the query, with their top KPIs). Use this first to find the kpi_id (slug) required by get_kpi and get_benchmarks.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Free-text search term, e.g. \"maintenance\", \"customer churn\", \"days sales outstanding\"." }, "function": { "enum": [ "Corporate Finance", "Corporate Marketing", "Corporate Strategy", "Customer Service", "Data Management & Analytics", "General Counsel", "Human Resources", "Industry-specific", "Information Technology", "Innovation Management", "Legal", "Operations Management", "Product Management", "Regulatory Compliance", "Sales Management", "Supply Chain Management" ], "type": "string", "description": "Optional corporate function filter." }, "industry": { "enum": [ "Business & Professional Services", "Consumer, Food, & Leisure", "Energy, Utilities, & Natural Resources", "Financial Services", "Healthcare & Life Sciences", "Industrials & Manufacturing", "Other, Cross-Industry, & Standards", "Public & Social Sector", "Real Estate, Infrastructure, & Built Environment", "Technology", "Telecommunications & Media", "Transportation, Mobility, & Logistics" ], "type": "string", "description": "Optional industry sector filter." } } }arguments 52 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8414160337220091.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8414160337220091/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8414160337220091?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.