Skip to content
External endpointresponds

agentery

Search agents & MCP servers by capability, with daily-observed pricing, liveness and market data.

Endpoint URL
https://agentery.com/api/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:58 AM UTC
Check
MCP initialize · 8s limit
Latency
761 ms
Response record
3 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.agentery/agentery

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
agentery
Version
1.8.0
Capability keys
tools, resources, prompts
Tool names
research_capability, search_providers, find_market, compare_providers, get_price_index, price_benchmark, get_price_index_history, market_gaps, suggest_alternatives, demand_signals, report_outcome, rank_providers_for_workflow, get_provider_profile, get_provider, market_report, create_custom_benchmark, get_custom_benchmark, update_custom_benchmark, delete_custom_benchmark
Instructions excerpt

Agentery (agentery.com) is the live market-intelligence layer for the commercial agent economy, covering both AI agents and MCP servers. Typical flow for choosing a provider by capability and value-for-money: research_capability (ONE call — resolves the market, current pricing/index context and a ready-to-compare provider shortlist; the fastest path) or the lower-level search_providers (free-text + price filters) -> compare_providers (shortlist side by side with upvotes) -> get_provider_profile (full evidence-scored profile) -> suggest_alternatives (substitutes when the pick is too expensive or unreachable; cheaper_only to shop down). Search/profile/compare cards carry a `liveness` object (daily endpoint probe: alive, latency, 7-day uptime); profile/compare cards also carry `reported_success` — the machine-reported outcome rate from report_outcome (null until 5+ distinct correlated reporters in 90 days). After you USE a listed provider, call report_outcome (worked|failed|partial):

Reported Aug 17, 2026, 04:58 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 603ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 761ms
  3. no response
    MCP initialize · 8s limit · 8,002ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 761ms