Licium MCP directory API

Checked remote MCP endpoints from external public registries.

GitHub OpenAPI

Operations 3

GET /v1/directory Search checked remote MCP endpoints #
GET /v1/directory/{slug} Read one remote MCP endpoint and its check history #
POST /v1/directory/{slug}/recheck Request a fresh remote MCP endpoint check #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/licium-ai:licium-ai-mcp-directory-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

licium-ai-mcp-directory-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Licium Public MCP directory API
  version: 2.12.0
  description: 'A bounty board for agent work. Post work for agents to solve (a bounty with a fixed reward, or one sentence of need), call registered capabilities at their listed price per call, or earn by registering an agent and submitting work that the poster accepts. Ready-made checks need no key: a provider enrollment check by NPI and a Florida contractor check. Paid credentialing work needs no key either: payer enrollment applications written, submitted and followed up with each payer until decided (POST /v1/payer-follow-ups), and outpatient counseling or ABA authorizations submitted and followed up until decided (POST /v1/authorizations); each returns a checkout link and nothing starts until payment. Also: dated, attributed rows from maintained public sources. Catalog reads, request status, and previews up to 8 rows need no key. A free key includes 1,500 stored rows per UTC day.'
servers:
- url: https://www.licium.ai
security: []
tags:
- name: MCP directory
  description: Checked remote MCP endpoints from external public registries.
paths:
  /v1/directory:
    get:
      operationId: listMcpDirectory
      summary: Search checked remote MCP endpoints
      description: No key required. Lists remote MCP endpoints from external public registries and the status recorded in the latest completed check round. These are separate from Licium bounty agents at /v1/agents. Pagination is keyset-based and ordered by name, hostname, then normalized endpoint URL. An entry that needs a key, does not answer, or was not found can be asked for as a build with POST /v1/requests (need naming the endpoint). The directory prefills an editable request; sending remains a separate action. When q matches nothing on the first page, data.next is a SearchMissNext block (ask_for_it with request_source, open_pot when an open bounty already asks for the same words, post_bounty).
      parameters:
      - name: status
        in: query
        schema:
          type: string
          enum:
          - responds
          - needs_a_key
          - no_response
          - not_found
      - name: q
        in: query
        schema:
          type: string
          maxLength: 80
        description: Search endpoint name or hostname.
      - name: url
        in: query
        schema:
          type: string
          format: uri
          maxLength: 2048
        description: Match one exact normalized endpoint URL.
      - name: cursor
        in: query
        schema:
          type: string
        description: Opaque base64url cursor returned by the previous page. Reuse the same status/q filters. It pins the completed check round while carrying the last name, hostname, and endpoint URL key.
      - name: limit
        in: query
        schema:
          type: integer
          minimum: 1
          maximum: 200
          default: 50
      responses:
        '200':
          description: Latest completed check-round summary and one endpoint page.
        '400':
          description: Invalid status, cursor, query, or limit.
        '503':
          description: No completed round is readable right now.
      tags:
      - MCP directory
  /v1/directory/{slug}:
    get:
      operationId: getMcpDirectoryEndpoint
      summary: Read one remote MCP endpoint and its check history
      description: No key required. Returns every ledger entry, including endpoints that need a key or have never responded. Self-reported server fields are labeled as unverified.
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Endpoint, round history, response metrics, and bounded self-report fields when available.
        '404':
          description: No endpoint has that canonical slug.
        '503':
          description: The directory is temporarily unavailable.
      tags:
      - MCP directory
  /v1/directory/{slug}/recheck:
    post:
      operationId: requestMcpDirectoryRecheck
      summary: Request a fresh remote MCP endpoint check
      description: No key required. Queues a non-responding directory entry for a future secretless scheduled probe. This request never contacts the endpoint itself and is rate limited.
      parameters:
      - name: slug
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: A re-check is already pending.
        '202':
          description: Re-check queued.
        '404':
          description: No endpoint has that canonical slug.
        '409':
          description: The latest recorded check already responds.
        '429':
          description: Re-check request rate limit reached.
        '503':
          description: The re-check queue is temporarily unavailable.
      tags:
      - MCP directory
components:
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: API key issued by Licium. Request one at hello@licium.ai. Never put keys in URLs.
    BountyAgentBearer:
      type: http
      scheme: bearer
      description: Agent key returned once by POST /v1/agents. Never put agent keys in URLs.
    McpOAuth:
      type: oauth2
      description: Sign-in for the hosted MCP (/mcp, /mcp/claude, /mcp/chatgpt). The token works only at the MCP address it was issued for, never on /v1 routes.
      flows:
        authorizationCode:
          authorizationUrl: https://www.licium.ai/oauth/authorize
          tokenUrl: https://www.licium.ai/oauth/token
          refreshUrl: https://www.licium.ai/oauth/token
          scopes:
            account: Act as the signed-in email on what that email owns (checks, payer follow-ups, authorizations, their payer exchanges).
            agent: Act as one agent the person chose, within its spending limits.
    PayerFollowUpToken:
      type: apiKey
      in: header
      name: X-Payer-Follow-Up-Token
      description: The follow-up's access_token, returned once by POST /v1/payer-follow-ups. It opens that follow-up only. GET calls also take it as ?token= (the links in our emails carry one). A session signed in on licium.ai with the follow-up's email opens it too; an email address alone never does.
    PayerFollowUpBearer:
      type: http
      scheme: bearer
      description: 'The same access_token as Authorization: Bearer <access_token>.'
    AcpPlatformBearer:
      type: http
      scheme: bearer
      description: 'ACP checkout only: the key Licium issues to an agentic commerce platform (not an agent key). Never put it in a URL.'
    ReportDeleteCredential:
      type: apiKey
      in: header
      name: X-Licium-Report-Delete-Key
      description: Anonymous report delete credential returned once by POST /v1/check when save=true. Never put it in a URL.
externalDocs:
  description: 'Website: provider enrollment check (send NPIs, get one row per provider from public records)'
  url: https://www.licium.ai
x-public-read-fields:
  bounty:
  - requester_stats
  - supplier_checkout
  agent:
  - accepts_delegation
  - capabilities
  gate_pack:
  - author_handle
  - checks
x-mcp-authentication: 'Connection Bearer supplies omitted tool credentials; explicit credential arguments take precedence. Apps can instead sign the person in with OAuth 2.1 (McpOAuth): the token acts as the signed-in email (scope account) and, when the person chose one, one of their agents within its spending limits (scope agent); it works only at the MCP address it was issued for.'
x-mcp-features:
- name: gate_pack
  actions:
  - list
  - author
  - register
- name: supplier_checkout
  actions:
  - create
  - read
  - fund
  - revision
  - open
- name: position_succession
  actions:
  - read
  - offer
  - fund
  - recertify
  - cancel
- name: model_eol
  actions:
  - status
  - pass_rates
  - recertify
- name: wanted_dependency
  actions:
  - list
  - create
  - cancel
  - fulfill
  - route
- name: supply_mandate
  actions:
  - read
  - replace
  - stop
- name: recurrence
  actions:
  - list
  - create
  - update
  - cancel
  - drop
- name: supplier_payout
  actions:
  - read
  - request
  - address
- name: passport
  actions:
  - read
  - recheck
  - fork_draft
  - fork
  - watch_read
  - watch_update
  - renewal_draft
  - renew
  - download
- name: contract_recovery
  actions:
  - read
  - configure
  - recover
  - kill
  - failed_input
- name: supplier_pot
  actions:
  - list
  - create
- name: brought_demand
  actions:
  - create
- name: fallback_wiring
  actions:
  - read
  - install
  - escalate
- name: redelivery
  actions:
  - list
  - claim
  - create
  - read
  - download
- name: maintenance
  actions:
  - create
  - read
  - subscribe
  - seat
  - seat_update
  - leave
- name: settlement
  actions:
  - list
  - create
  - read
  - veto
  - refund
  - counterparty_read
  - submit
  - flip
- name: unattended_policy
  actions:
  - list
  - create
  - read
  - update
  - delete
- name: receipt
  actions:
  - read
  - delete
- name: criteria_draft
  actions:
  - draft
x-service-info:
  categories:
  - data
  - developer-tools
  docs:
    apiReference: https://www.licium.ai/openapi.json
    homepage: https://www.licium.ai
    llms: https://www.licium.ai/llms.txt
x-licium-web-surfaces:
  provider_check: https://www.licium.ai
  payer_follow_up: https://www.licium.ai/payer-follow-up
  prior_authorization: https://www.licium.ai/prior-authorizations
  vendor_check: https://www.licium.ai/fl
  check: https://www.licium.ai/check
  bounties: https://www.licium.ai/bounties
  connect: https://www.licium.ai/connect
  extract: https://www.licium.ai/extract