Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Idescat MCP Server

REMOTE · API.IDESCAT.CAT · SCANNED SEP 20

Query official statistics of Catalonia (Idescat): tables, metadata and JSON-stat data via MCP.

Available components

+3 this week 73 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability76
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4920 tokens (~492/item across 10 items; 7 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the Idescat MCP Server server?

Idescat MCP Server is a hosted endpoint at https://api.idescat.cat/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.idescat.cat

# add to Claude Code
claude mcp add --transport http cat-idescat-mcp 'https://api.idescat.cat/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cat-idescat-mcp": {
      "url": "https://api.idescat.cat/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cat-idescat-mcp": {
      "type": "http",
      "url": "https://api.idescat.cat/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cat-idescat-mcp]
url = "https://api.idescat.cat/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cat-idescat-mcp": {
      "type": "remote",
      "url": "https://api.idescat.cat/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cat-idescat-mcp --url 'https://api.idescat.cat/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cat-idescat-mcp:
    url: "https://api.idescat.cat/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cat-idescat-mcp": {
      "Transport": "http",
      "Url": "https://api.idescat.cat/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cat-idescat-mcp -t streamable-http -u 'https://api.idescat.cat/mcp'
// mcp.json
{
  "mcpServers": {
    "cat-idescat-mcp": {
      "type": "http",
      "url": "https://api.idescat.cat/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 0
    • The server changed its declared name: idescat-tools → cat.idescat/mcp security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://api.idescat.cat/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.idescat.cat,O=Generalitat de Catalunya,ST=Barcelona,C=ES CN=Sectigo Public Server Authentication CA OV R36,O=Sectigo Limited,C=GB 24 Feb 2026 24 Feb 2027 RSA 2048 SHA256-RSA 43a79315a50910ea2ef38627d7d4c3d2
SANs: api.idescat.cat, www.api.idescat.cat
CN=Sectigo Public Server Authentication CA OV R36,O=Sectigo Limited,C=GB (CA) CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB 22 Mar 2021 21 Mar 2036 RSA 3072 SHA384-RSA 2c1a3c76e943ddddff191b31890aed71
CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US 22 Mar 2021 18 Jan 2038 RSA 4096 SHA384-RSA d27fbbc1de359e5216ad6149586099c4
CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US 1 Feb 2010 18 Jan 2038 RSA 4096 SHA384-RSA 1fd6d30fca3ca51a81bbc640e35032d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.idescat.cat. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cat. present 58737 10 Verified
idescat.cat. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.idescat.cat/mcp Verified 200
http (plaintext) http://api.idescat.cat/mcp HTTPS enforced 301 https://api.idescat.cat/mcp
MCP tools · 7 exposed · ~3,175 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_idescat_stat ~366

Obtains information about an Idescat (Statistical Institute of Catalonia) statistic given its acronym. Use it when the user asks about a specific statistic identified by its acronym (for example, CENSPH, EPA, PIBC, AFI, etc.). The 'datasets' field is a key boolean: if true, the statistic is normalized and therefore available in get_idescat_stat_tables and the rest of the table-level tools (metadata, data, divisions, etc.); if false, the statistic is NOT normalized and get_idescat_stat_tables will not recognize it (it would return an identifier error), so the only information available is what this same tool returns ('url', 'time_ref', 'update_date', 'update_title', 'update_text'). To know if a statistic has queryable tables, this tool is enough, without calling get_idescat_stat_tables. The 'url' field is a relative address to https://www.idescat.cat. The 'geo' field is an array with the available geographical disaggregation levels (e.g., 'cat', 'prov', 'at', 'com', 'mun', 'dis', 'sec'). POPULATION FIGURES: when population data is requested, the main and richest source is CENSPH (population and housing census, annual); for semi-annual estimates there is EP (population estimates, semi-annual); and there is also PMH (municipal register of inhabitants, annual). By default, choose CENSPH (or EP if semi-annual data is requested) and NEVER use PMH for population data unless the user explicitly asks for it.

NameTypeReqDescription
statstringyesStatistic acronym in lowercase (for example, 'afi', 'censph')

No output schema declared.

No examples provided.

get_idescat_stat_tables ~120

Obtains the list of tables for an Idescat statistic given its official acronym. Use it when the user asks what tables or information a statistic has. The response contains a 'tables' array where each element has 'id' (numerical identifier) and 'name' (table title). Present each table as: name (id). Inform the user that they can request more details about a table by indicating its identifier.

NameTypeReqDescription
statstringyesStatistic acronym in lowercase (for example, 'censph', 'piba')

No output schema declared.

No examples provided.

get_idescat_stats ~446

Obtains the complete list of Idescat statistics (all, normalized and non-normalized). It has no parameters. The response contains a 'statistics' array where each element has: 'acronym' (lowercase acronym, e.g., 'censph', to be used as the 'stat' argument of the other tools), 'name' (title), 'description' (summary), 'datasets' (boolean), 'geo' (array of available territorial disaggregations), and 'url' (initial web address, relative to https://www.idescat.cat). Use it when the user asks what statistics are available or when a statistic needs to be found by name or territorial disaggregation. THREE KEY FIELDS to decide the flow: (1) 'datasets' — if true, the statistic is normalized and you can use the rest of the tools (get_idescat_stat_tables, get_table_metadata, get_table_data, get_table_geo, render_table); if false, ONLY the information from this tool and get_idescat_stat is available. (2) 'geo' — available levels of geographical disaggregation (e.g., 'cat'=Catalonia, 'prov'=provinces, 'at'=territorial plan areas, 'com'=counties and Aran, 'mun'=municipalities, 'dis'=districts, 'sec'=census sections). ALWAYS CHECK 'geo' before choosing a statistic for a territorial query: if the user asks for county data, choose a statistic that includes 'com' in 'geo'. (3) 'url' — home page of the statistic on the Idescat website. POPULATION FIGURES: when population data is requested, there are several sources: the main and richest is CENSPH (population and housing census, annual); for semi-annual estimates there is EP (population estimates, semi-annual); and there is also PMH (municipal register of inhabitants, annual). By default, choose CENSPH (or EP if semi-annual data is requested) and NEVER use PMH for population data unless the user explicitly asks for it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_table_data ~886

Retrieves the data (values) of an Idescat table in JSON-stat format for a territorial division. You can retrieve the ENTIRE table (without filters) or only a SUBSET by passing the OPTIONAL parameters 'filters' (specific categories per dimension) and/or 'last' (number of last time periods); filtering returns smaller responses and allows querying tables that as a whole would exceed the limit. The filters use the dimension identifiers and category codes (category.index) returned by get_table_metadata (with the same 'geo'). IMPORTANT: the 20,000 cell limit is checked AFTER applying the filters; if it exceeds it, it returns a 'Dataset too large' error and you must add more filters (filters, last). You can call get_table_metadata beforehand to know the dimensions, periods, and category codes. The result contains: 'id' (dimension names in order), 'size' (number of categories per dimension), 'value' (flat array of values), 'dimension' (details per dimension: codes in category.index, labels in category.label, units in category.unit), 'role' (which dimensions are time, geo, or metric), 'status' (marks special values). HOW TO READ 'value' (row-major order): the array is FLAT; the LAST dimension of 'id' varies fastest and the first slowest. To get the value of a combination of categories (one per dimension) follow these 4 steps: (1) for each dimension, look for the POSITION (0-based) of the chosen category in dimension.{nom}.category.index — this 'index' can be a code→position object or a list of codes (the position is the index within the list); ALWAYS use this index, DO NOT assume alphabetical order or by label; (2) the stride of each dimension = product of the 'size' of the SUBSEQUENT dimensions (the last dimension has stride 1); (3) offset = sum of (position × stride) of all dimensions; (4) the searched value is value[offset]. Use the order of the 'id' array in all steps (NOT the order of keys in 'dimension'). EXAMPLE: id=['territory','sex'], size=[3,2], territory.index={B…

NameTypeReqDescription
filtersobjectOPTIONAL filter by dimension: the keys are dimension identifiers (for example, 'SEX', 'COM', 'YEAR') and the values are category codes separated by commas (for example, {"SEX": "F", "COM": "01,TOTAL"…
geostringTerritorial division code (optional, defaults to 'cat' = Catalonia as a whole). Other values: 'prov', 'at', 'com', 'mun', 'dis', 'sec'. It must match the 'geo' checked in get_table_metadata. Division…
lastintegerOPTIONAL. Number of last time periods to retrieve (for example, 2 = the two most recent years). Do not combine it with an explicit filter on the time dimension
statstringyesStatistic acronym in lowercase (for example, 'censph', 'piba')
tablestringyesNumerical identifier of the table, obtained from get_idescat_stat_tables (for example, '21654', '8607')

No output schema declared.

No examples provided.

get_table_geo ~228

Obtains the list of territorial divisions available for an Idescat table (for example: cat=Catalonia, com=counties and Aran, mun=municipalities, prov=provinces, at=territorial plan areas). The response contains a 'divisions' array where each element has 'id' (division code) and 'name' (label). Often it is NOT necessary to call it because get_table_metadata already returns these divisions in 'link.related'. Use it only if you need the list of divisions without having called the metadata. The 'id' code is the value to pass to the 'geo' parameter of get_table_metadata, get_table_data, or render_table. If not specified, these tools use the 'cat' division (Catalonia as a whole) by default.

NameTypeReqDescription
statstringyesStatistic acronym in lowercase (for example, 'censph', 'piba')
tablestringyesNumerical identifier of the table, obtained from get_idescat_stat_tables (for example, '21654', '8607')

No output schema declared.

No examples provided.

get_table_metadata ~523

Obtains the metadata for a specific Idescat table in JSON-stat format, given the statistic acronym (stat) and the table identifier (table). Use it when the user wants to know the details of a table: dimensions, categories available for each dimension (time periods, territorial scopes, sex, etc.), date of last update, units, etc. The acronym and identifier are previously obtained with get_idescat_stat_tables. At the end of the response, always include this Markdown link (substituting {stat} and {table} in lowercase): [See the results in this table](https://www.idescat.cat/pub/?id={stat}&n={table}). TERRITORIAL DIVISIONS: the response includes 'link.related', an array with other available territorial divisions (provinces, counties, municipalities, etc.); therefore it is often NOT necessary to call get_table_geo. If you pass the 'geo' parameter (for example geo='com' or geo='mun'), you get the metadata for that division, which includes the codes and labels (category.index / category.label) for the geographical dimension and the rest of the dimensions; use these codes directly to build the 'filters' parameter of get_table_data or render_table, without having to test and correct. SIZE CONTROL: check the 'size' field (array): the product of all its elements is the total number of cells. If it exceeds 20,000 (common case for municipal data), DO NOT retrieve the entire table; use get_table_data with filters (filters, last) to reduce the selection. If it is equal to or less than 20,000, you can retrieve it entirely with get_table_data.

NameTypeReqDescription
geostringTerritorial division code (optional, defaults to 'cat' = Catalonia as a whole). Other common values: 'prov' (provinces), 'at' (territorial plan areas), 'com' (counties and Aran), 'mun' (municipalitie…
statstringyesStatistic acronym in lowercase (for example, 'censph', 'piba')
tablestringyesNumerical identifier of the table, obtained from get_idescat_stat_tables (for example, '21654', '8607')

No output schema declared.

No examples provided.

render_table ~606

Returns a Markdown table already built with the filtered data from an Idescat table, ready to be shown to the user without having to interpret the JSON-stat. It includes the title, units, the table with category labels, status notes (e.g., provisional data), and ALWAYS a final link to the table on the Idescat website that must be kept in the response to the user. By default, it puts the time dimension in rows and the first dimension with more than one category in columns; this can be changed with the 'rows' and 'cols' parameters. All other dimensions with more than one category must be reduced to a single category with 'filters'. IMPORTANT (error self-correction): if the tool returns the error with 'pending_dimensions', DO NOT change tools: call render_table again adding the 'filters' parameter with a single category for each pending dimension (you can start from the 'suggested_filters' field that comes in the same error response, but choose the appropriate category for the user's question according to 'categories'). If it then returns the size error (maximum 40 rows × 15 columns), follow the 'how_to_fix' field: if the time dimension has too many columns, add the 'last' parameter (e.g., last: 12), and if the rows dimension is too large, filter it with 'filters' or swap 'rows'/'cols'. You can chain 'filters' and 'last' in the same call. The values '..' indicate data not available.

NameTypeReqDescription
colsstringIdentifier of the dimension that should go in the columns (for example, 'SEX'). Default: the first dimension with more than one category that is not the row one
filtersobjectFilters by dimension: the keys are dimension identifiers (for example, 'SEX', 'COM', 'YEAR') and the values are category codes separated by commas (for example, {"SEX": "F", "COM": "01,TOTAL"}). The…
geostringTerritorial division code, obtained from get_table_geo or from 'link.related' (per example, 'cat', 'com', 'mun', 'prov'). Default: 'cat' (Catalonia as a whole)
lastintegerNumber of last time periods to retrieve (for example, 2 = the two most recent years). Do not combine it with an explicit filter on the time dimension
rowsstringIdentifier of the dimension that should go in the rows (for example, 'YEAR'). Default: the time dimension (more periods fit in the rows than in the columns)
statstringyesStatistic acronym in lowercase (for example, 'censph', 'piba')
tablestringyesNumerical identifier of the table, obtained from get_idescat_stat_tables (for example, '21654', '8607')

No output schema declared.

No examples provided.

Common questions

What is the Idescat MCP Server server?

Idescat MCP Server is listed in the public MCP registry as cat.idescat/mcp. Query official statistics of Catalonia (Idescat): tables, metadata and JSON-stat data via MCP. This page covers its hosted endpoint (https://api.idescat.cat/mcp).

Is the Idescat MCP Server server safe to use?

Idescat MCP Server scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Idescat MCP Server server expose?

Idescat MCP Server exposes 7 tools: get_idescat_stats, get_idescat_stat, get_idescat_stat_tables, get_table_metadata, get_table_data, and 2 more. Their descriptions and schemas cost roughly 3,175 tokens of context every time the server is loaded.

Does the Idescat MCP Server server require authentication?

No. We connected to Idescat MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Idescat MCP Server server still maintained?

Idescat MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.