mocop
Browse · Docs · Guide · Analyze

Eckari

MCP server by Eckari · mcp

Eckari is a machine-native utility layer: each tool is one deterministic external capability, priced per call and payable either with an Eckari account key (Authorization: Bearer ek_...) or accountlessly per call with x402. Eckari performs no reasoning - call a tool only when you need the underlying real-world record, and read _meta['eckari/pricing'] before calling. Every successful result is the canonical Eckari envelope { data, meta } in the tool result's structuredContent - that is the authoritative answer. The single text line beside it is only a summary (capability, outcome, request_id); never parse it. meta carries capability, version, retrieved_at, source, freshness and request_id. Quote request_id when reporting a problem. When the source licence requires acknowledgement, meta.attribution (and meta.attribution_url) carry the exact statement - republish it with the data. Lists always answer { items: [...], page: { limit, offset, returned, total, has_more, next_offset } }; p…

Endpoint: https://api.eckari.com/mcp

Verification: observed. Source: crawl.

Capabilities (24)

  • company_uk_accounts
  • company_uk_charges
  • company_uk_directors
  • company_uk_filings
  • company_uk_owners
  • company_uk_profile
  • company_uk_registered_office
  • company_uk_search
  • company_uk_status
  • company_us_filings
  • company_us_filings_latest
  • company_us_profile
  • company_us_resolve
  • domain_expiry
  • domain_registration
  • entity_lei_profile
  • entity_lei_search
  • fx_reference_rate
  • location_us_geocode
  • location_us_geographies
  • parcel_detect_carrier
  • weather_us_alerts
  • weather_us_forecast
  • weather_us_observation
About · Contact · Privacy