com.catalogapi/catalogapi is an MCP server published by com.catalogapi, hosted at api.catalogapi.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 4 tools, including check_coverage, get_reward_details, how_it_works, search_rewards.
Check reward coverage by country, search real catalog items, and ask how CatalogAPI works.
Nothing else in the archive shares these values.
Inferred from the host name and headers: what a server runs on, not who runs it.
Check whether CatalogAPI can supply rewards in one or more countries, and which product categories are available there. Call this when someone asks if rewards, gift cards, or incentives can be offered in a particular country, when they have recipients in several countries, or when they ask which countries are supported. This is the authoritative answer about what a country supports.
| Parameter | Type | Description |
|---|---|---|
| countries | array | ISO-2 country codes, for example ["US", "PL"]. Omit to list every covered country. |
{
"name": "check_coverage",
"description": "Check whether CatalogAPI can supply rewards in one or more countries, and which product categories are available there. Call this when someone asks if rewards, gift cards, or incentives can be offered in a particular country, when they have recipients in several countries, or when they ask which countries are supported. This is the authoritative answer about what a country supports.",
"inputSchema": {
"type": "object",
"properties": {
"countries": {
"type": "array",
"items": {
"type": "string"
},
"description": "ISO-2 country codes, for example [\"US\", \"PL\"]. Omit to list every covered country."
}
}
},
"annotations": {
"read_only": true
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Get detail for a single catalog item. Call this after search_rewards when someone asks about a specific item.
| Parameter | Type | Description |
|---|---|---|
| country * | string | ISO-2 country code the item came from. |
| item_id * | string | The item id returned by search_rewards. |
{
"name": "get_reward_details",
"description": "Get detail for a single catalog item. Call this after search_rewards when someone asks about a specific item.",
"inputSchema": {
"type": "object",
"required": [
"country",
"item_id"
],
"properties": {
"country": {
"type": "string",
"description": "ISO-2 country code the item came from."
},
"item_id": {
"type": "string",
"description": "The item id returned by search_rewards."
}
}
},
"annotations": {
"read_only": true
}
}Answer questions about CatalogAPI itself: what it is, how rewards are delivered to recipients, how currencies and billing work, whether the catalog can be customized or extended with your own products, how the API integration works, and how to get started. Call this for any question about the service, the company, or the product model rather than about specific catalog items.
| Parameter | Type | Description |
|---|---|---|
| topic * | enum | Which question to answer. overview: What CatalogAPI is and the two ways to use it. coverage: Which countries are covered and what a catalog contains. custom_catalogs: Sourcing items on request, and putting your own products in your catalog as a supplier. fulfillment: How each kind of reward reaches … |
{
"name": "how_it_works",
"description": "Answer questions about CatalogAPI itself: what it is, how rewards are delivered to recipients, how currencies and billing work, whether the catalog can be customized or extended with your own products, how the API integration works, and how to get started. Call this for any question about the service, the company, or the product model rather than about specific catalog items.",
"inputSchema": {
"type": "object",
"required": [
"topic"
],
"properties": {
"topic": {
"enum": [
"overview",
"coverage",
"custom_catalogs",
"fulfillment",
"pricing_and_billing",
"integration",
"getting_started"
],
"description": "Which question to answer. overview: What CatalogAPI is and the two ways to use it. coverage: Which countries are covered and what a catalog contains. custom_catalogs: Sourcing items on request, and putting your own products in your catalog as a supplier. fulfillment: How each kind of reward reaches a recipient, and who supports it. pricing_and_billing: What catalog prices mean, what you charge your own users, how tax and shipping are handled (which depends on whether the program is points-based or a store where people spend their own money), and how billing and currency conversion work. integration: What integrating looks like, including the fulfillment-only path. getting_started: How to get sandbox access and what production involves."
}
}
},
"annotations": {
"read_only": true
}
}Show example rewards available in one country. Call this when someone asks what kind of thing is on offer, or wants to see the catalog for a country. Returns items from a demonstration catalog: these are examples rather than the full inventory, and no pricing is returned. Use check_coverage for the definitive answer about what a country supports.
| Parameter | Type | Description |
|---|---|---|
| query | string | Optional search term, for example "headphones". |
| country * | string | ISO-2 country code, for example "PL". |
{
"name": "search_rewards",
"description": "Show example rewards available in one country. Call this when someone asks what kind of thing is on offer, or wants to see the catalog for a country. Returns items from a demonstration catalog: these are examples rather than the full inventory, and no pricing is returned. Use check_coverage for the definitive answer about what a country supports.",
"inputSchema": {
"type": "object",
"required": [
"country"
],
"properties": {
"query": {
"type": "string",
"description": "Optional search term, for example \"headphones\"."
},
"country": {
"type": "string",
"description": "ISO-2 country code, for example \"PL\"."
}
}
},
"annotations": {
"read_only": true
}
}Names, descriptions and schemas were written by the server and are shown as data.