Apis Io MCP Server

Full detail for one provider: profile, rating, and the APIs it publishes. The heavy `collections` and `common` sections are omitted by default (their counts are still reported) — pass view=full for the whole document, or fields=["common"] for a section. Narrow for cheap reads: fields=["score"] returns just the rating. Relative artifact URLs are resolved to absolute, fetchable ones.

Every artifact a provider publishes — provider-level (MCP, security, scopes, rules, agentic-access) and per-API (OpenAPI, Arazzo, overlays, reference docs) — grouped by type with counts. by_type_counts is the full summary; pass `type` (e.g. OpenAPI, MCP) to scope the artifacts list to one type, since an unfiltered provider can be 250+ entries.

A getting-started view for a provider — website, portal, signup, docs, authentication, base URLs, and first steps assembled from its registered links.

One provider's full rating breakdown (composite, band, trend, six facets).

PRO — Delete a saved search you own.

PRO — List the saved searches you own (name, criteria, when last run, how many matches are tracked).

PRO — Re-run one of your saved searches against the live catalog and return current matching providers.

PRO — What is NEW for a saved search since you last checked: providers that newly match your criteria. Advances the delta cursor, so each call reports only what changed since the previous call. The agent-native version of the demand report.

START HERE. Federated overview of the APIs.io catalog for a query: the top matching APIs, providers, AND tags in one call, each with its total match count. Filter by tags, artifact types, industry, region, rating band. `limit` is per section. To page/sort the full list of ONE type, use find_apis / find_providers / find_tags; for one entity, get_api / get_provider.

Paginated, sortable list of APIs across providers — filter by tag, provider, artifact type, industry, region, or rating band. Use apis_io_search first for a cross-type overview.

APIs.json indexes across the catalog. The APIs.json discovery documents themselves. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

A company's weakest investment dimensions — where it is thin and a vendor could sell in. Pro.

Browse profiled companies (Fortune 1000) by name; ranked by overall technology-readiness signal. Free discovery.

Full demand-side profile for one company: 40-dimension readiness scores, adopted stack, and per-quarter history. Pro.

One industry: metadata + a top sample of its member providers (ranked, with the total). Use find_providers?industry=slug for the full list, or view=full here.

PRO — Top-rated providers in an industry vertical.

PRO — Valuable artifact types (MCP, Arazzo, Rules, Skills…) commonly missing across a whole industry — where the vertical is under-served.

JSON-LD contexts across the catalog. Linked-data vocabularies. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

JSON Schemas across the catalog. Standalone data schemas. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

JSON Structures across the catalog. Data structures behind an API. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

PRO — The biggest rating movers (up and down) since the previous scoring build.

PRO — A provider's rating movement: current score/band/trend and the implied previous-build point.

The rubric — bands, facet weights, trend thresholds — so an agent can interpret any score.

Full detail for one API by aid (provider:api-slug); set include=["content"] to inline artifact bodies.

One API's artifacts grouped by type (by_type_counts is the full summary); pass `type` to scope the list to one type (synonym-aware: MCP matches MCPServer), include=["content"] to inline the bodies.

One area: metadata, its dedicated site link, and a top sample of member providers (with the total). Use find_providers?area=slug for the full list, or view=full here.

PRO — Top-rated providers in a curated API Evangelist area.

BUSINESS/license tier — the WHOLE dataset in one pull (not a 100-row page): `ratings` (every rated provider with facets, trend, rubric + provenance) or `providers` (the catalog with coverage + score). For media outlets and analysts licensing the data to publish rankings and trends. Attribute to apis.io and cite the rubric.

PRO — Export a designed capability stack as an adoptable APIs.json document (with an Arazzo hint) the team can commit.

PRO — Get a list you own, with each member resolved to its current name, band, and score.

One VC firm: identity, fund facts, and portfolio summary (totals, band distribution, average rating). Pass view=full to inline the whole portfolio. Free.

Services, tools, or standards ranked by how many companies adopt them across the profiled set. Free.

Cross-section ranking of the 40 tracked investment dimensions (AI, cloud, governance, security, …) by how many profiled companies show signal. Free.

One region: metadata + a top sample of its member providers (ranked, with the total). Use find_providers?region=slug for the full list, or view=full here.

PRO — Top-rated providers in a region.

APIs similar to a given one ("more like this") by shared tags.

Providers similar to a given one (alternatives) by shared tags, industry, region, and artifact coverage.

PRO — Add providers/APIs (by slug or aid) to one of your lists.

Arazzo workflows across the catalog. Multi-step API workflows chaining operations. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Browse the API Evangelist areas taxonomy (authentication, webhooks, payments, …) — curated, scored provider indexes. Search by text; sort by provider count.

Find artifacts of ANY one type across the catalog — the cross-type entry point. Each type also has a dedicated find_<type> tool (find_mcp, find_rules, find_scopes, …) with sorts and filters unique to that type; prefer those when you know the type. Types: mcp, skills, rules, arazzo, plans, rate-limits, finops, collections, asyncapis, graphql, json-ld, channels, examples, json-schemas, json-structures, openapis, postman, vocabularies, apis-json. PRO: scopes, security. include=["content"] inlines bodies.

AsyncAPI (event-driven) specifications across the catalog. Event/streaming APIs. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

AsyncAPI event channels across the catalog. Individual event channels (topics/streams). Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Postman / Open collections across the catalog. Runnable request collections. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

PRO — Compare 2+ providers side by side: composite/band, per-facet leaders, and an artifact-coverage matrix.

PRO — Create a named, persistent list (a shortlist / stack you own) of providers or APIs. Requires an apis.io API key.

PRO — Delete a list you own.

One call, pick your field groups — resolves a slug OR any identifier and returns exactly the groups you ask for, instead of chaining get_provider + get_provider_rating + get_provider_artifacts + get_provider_onboarding. Groups: profile, onboarding, artifacts (free); rating, insights (Pro). Free base.

Example payloads across the catalog. Real request/response examples. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

FinOps / billing models across the catalog. How usage is metered and billed. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

PRO — For each provider: high-value artifacts it lacks (MCP, Arazzo, Rules, Skills…), what its peers commonly publish but it lacks, and its score vs the peer median — plus stack-level gaps across the set.

GraphQL schemas across the catalog. GraphQL type systems. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Browse industry verticals; sort by provider/API count.

The reverse portfolio edge — which VC firms in the network back a given provider/company (by slug). Free.

PRO — List the lists/shortlists you own.

The supply↔demand join: apis.io providers whose product appears in a company's adopted stack, ranked by rating. Pro.

MCP servers across the catalog. Model Context Protocol servers a provider offers to agents. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

An API's primary OpenAPI reference (url) — the top agent intent; set include=["content"] to inline the spec body.

OpenAPI specifications across the catalog. The REST contract. get_openapi returns one API's primary spec with optional inlined body. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Pricing plans across the catalog. An API's pricing tiers. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

A VC firm's portfolio companies, each matched to the network and rated. Filter is_provider=true (only API providers), in_network=true, band, or min_score; sort by score (default), api_count, or name. The demand-side view of who a fund has backed. Free.

Postman collections across the catalog. Postman-format collections (by reference). Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Paginated, sortable list of providers — filter by text, tag, artifact type, industry, region, rating band, or access model (pricing/onboarding/try_now/public). Use apis_io_search first for a cross-type overview.

Rate-limit policies across the catalog. Declared throttling policies. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Ranked ratings leaderboard — filter by band, score range, trend, or facet threshold. Sort by composite (default), delta (biggest gainers), or any quality facet (governance, security, …) to rank providers by that dimension.

Design an API stack — the best-rated catalog provider per capability, assembled into a stack. FREE preview = the top pick per capability; PRO = alternatives, per-pick artifact gaps, and an exportable APIs.json + Arazzo hint. Decompose the domain into capabilities first, then pass them here.

Browse geographic regions; sort by provider/API count.

Resolve ANY identifier — website URL, domain (stripe.com), or GitHub org (github.com/stripe) — to the apis.io provider it belongs to. Use this when you have a URL, not a slug. Free.

Spectral governance rulesets across the catalog. API design/linting rulesets. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

PRO — Persist the current search criteria as a named saved search you own, so you can re-run it and get net-new results later. Criteria use the same filters as apis_io_search. Requires an apis.io API key.

OAuth scope catalogs across the catalog. The OAuth scopes an API defines. Pro tier. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Security artifacts across the catalog. Authentication, domain security, VDP, trust center. Pro tier. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

Agent Skills across the catalog. Packaged agent skills. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

OWNER — The weekly "what's worth writing" rollup: ranked story leads from the demand map crossed with rating movement — unmet demand (searched, no result), risers/fallers, and hot-but-thin capabilities. Each lead is a headline, its signal, and a suggested angle. include=["raw"] appends the underlying demand report.

One tag: its metadata, neighbor tags, and a top sample of its providers and APIs (with totals). Use find_apis?tags=slug / find_providers?tags=slug for the full ranked list, or view=full here.

Paginated, sortable list of tags in the taxonomy. Use apis_io_search first for a cross-type overview.

Find venture-capital firms by name, thesis tags, or category. Each carries a network-matched, rated portfolio graph. Sort by portfolio_on_network (default), portfolio_total, portfolio_rating, or name. Free.

API vocabularies across the catalog. Controlled vocabularies a provider publishes. Filter by q / tags / providers; include=["content"] inlines bodies. Use find_artifacts for cross-type search.

PRO — What changed in the catalog since a date: providers added/updated, plus rating movement (up/down) from the latest scoring build.