Iridium .well Known API
The .well Known API from Iridium — 2 operation(s) for .well known.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/iridiumhqmcp-com:iridiumhqmcp-com-well-known-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. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Iridiumhqmcp Com .well Known API
version: 0.1.0
description: 'Operations tagged .well Known across 2 of this provider''s published API definitions: openapi.json, iridiumhqmcp-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: .well Known
paths:
/.well-known/glama.json:
get:
summary: Glama
description: Proves listing ownership to glama.ai. Email must match a Glama account.
operationId: glama__well_known_glama_json_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
/.well-known/mcp/server-card.json:
get:
summary: Server Card
description: 'Static capability metadata for directory crawlers (Smithery et al).
Their scanners call tools/list over the transport, which is auth-gated, so they get a 401
and index nothing — the failure recorded in glama.md. Serving this card is the documented
way past that WITHOUT opening /mcp to unauthenticated introspection: the 401 there is what
starts OAuth discovery for real clients and must stay.
`_mcp_http.tools` is the same list the transport''s own list_tools handler returns, so the
card cannot drift from what an authenticated client sees. Tool names and schemas are public
surface by intent; tools/call remains gated.
`description` and `prompts` come from the same two sources the transport uses, for the same
reason. A crawler reading only this card is the first impression for most directories, and 53
tool names with no framing is not one — the prompts are what say who Iridium is for.'
operationId: server_card__well_known_mcp_server_card_json_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
components:
securitySchemes:
HTTPBearer:
type: http
scheme: bearer
x-refined-from:
- openapi.json
- iridiumhqmcp-com-openapi.json
x-provenance:
method: harvested
publisher: Iridium
source: https://api.iridiumhqmcp.com/openapi.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)