Indicateurs TE MCP
by ekimetricsco.huggingface.ekimetrics/mcp_indicators
Serveur MCP — indicateurs territoriaux transition écologique
- Remote endpoint
- 5 tools
- MIT
Uptime
Checked · every day
100%from 4 days of checks
Up without downtime on 3 of 3 days with data.
- No downtime
- Degraded
- Down over 5 minutes
- No data
- Not checked yet
Response time
Median 1045 ms, slowest 5% 1193 ms for the handshake and the tool list, over 30 days.
How far each check got
- Reached the address 100%
- Completed the handshake 100%
- Listed its tools 100%
5 tools at the last answer.
Every day
| Day | Result | Checks | Median |
|---|---|---|---|
| 3 Nov (today) | No verdict yet | 0 | – |
| 2 Nov | No downtime | 1of 1 | 1002 ms |
| 1 Nov | No downtime | 1of 1 | 1156 ms |
| 31 Oct | No downtime | 2 | 1105 ms |
A failure counts as down time only when a second check five minutes later fails too. How we check
Connect to the publisher's own endpoint
Paste into Settings › Connectors › Add custom connector:
https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse Run in a terminal:
claude mcp add --transport sse mcp_indicators https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse Add to ~/.cursor/mcp.json:
Add to ~/.config/devin/mcp_config.json:
Add to mcp.json (Program › Install › Edit mcp.json):
Add to ~/.gemini/settings.json:
Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):
Add to ~/.config/eca/config.json (global) or .eca/config.json in the project:
{
"mcpServers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} Add to .vscode/mcp.json:
{
"servers": {
"mcp_indicators": {
"type": "sse",
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.config/zed/settings.json:
{
"context_servers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):
Add to anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:
Add to Augment Settings Panel – MCP section – Import from JSON (VS Code extension):
{
"mcpServers": {
"mcp_indicators": {
"type": "sse",
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} Add to ~/.continue/config.yaml:
mcpServers:
- name: "mcp_indicators"
type: sse
url: "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse" Add to ~/.config/goose/config.yaml:
extensions:
"mcp_indicators":
type: streamable_http
name: "mcp_indicators"
enabled: true
uri: "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
headers: {}
env_keys: []
envs: {}
timeout: 300 This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Run in a terminal:
codex mcp add mcp_indicators --url https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.llm/config.json:
Add to resources/assets/config/mcp.json in the installed app:
Add to ~/.boltai/mcp.json:
Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
Add to ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace):
{
"mcpServers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/agenvoy/mcp.json:
{
"servers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
Add to ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
{
"amp.mcpServers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
} For agents: the install prompt
Every step above as one Markdown text, for an assistant installing it for you.
# Install the MCP server Indicateurs TE MCP (`co.huggingface.ekimetrics/mcp_indicators`)
Its page: https://plug.directory/servers/co.huggingface.ekimetrics/mcp_indicators
It runs on the publisher's servers; the client connects to its URL.
Use the section for the person's client.
## Claude Desktop
Paste into Settings › Connectors › Add custom connector:
```text
https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse
```
## Claude Code
Run in a terminal:
```sh
claude mcp add --transport sse mcp_indicators https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse
```
## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA
Merge into the place for the person's client:
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
```json
{
"mcpServers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
}
```
## VS Code
Merge into .vscode/mcp.json:
```json
{
"servers": {
"mcp_indicators": {
"type": "sse",
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Zed
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Cline, AnythingLLM, Augment Code
Merge into the place for the person's client:
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
```json
{
"mcpServers": {
"mcp_indicators": {
"type": "sse",
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
}
```
## Continue
Merge into ~/.continue/config.yaml:
```yaml
mcpServers:
- name: "mcp_indicators"
type: sse
url: "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
```
## Goose
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Codex
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Agenvoy
This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.
## Amp
Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):
```json
{
"amp.mcpServers": {
"mcp_indicators": {
"url": "https://ekimetrics-mcp-indicators.hf.space/gradio_api/mcp/sse"
}
}
}
```
Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.
Tools 5
MCP_indicators_find_territoryFind the official code of a French territory from (part of) its name, e.g. "Lyon", "Bouches-du-Rhône", "Grand Paris". Use it before query_indicator_data when the code is unknown (EPCI SIREN and commune INSEE codes are hard to guess). Regions are resolved locally; other levels are looked up in the indicators API. Returns: JSON: name, total_count, territories [{geographic_level, geocode, libelle}] (max 20 per level).MCP_indicators_get_indicator_detailsFull metadata of one indicator: definition, calculation method, available years and geographic levels, data completeness, sources. Returns: JSON: metadata {id, libelle, unite, description, methode_calcul, annees_disponibles [..], mailles_disponibles [..], couverture_geographique, completion {level: ratio 0-1}}, sources [..], available_cubes {level: cube}.MCP_indicators_list_indicatorsList the catalogue of French territorial ecological indicators (~170), optionally filtered. Prefer search_indicators for a topic; use this tool to browse a theme or to know what exists at a given geographic level. Returns: JSON: count, indicators [{id, libelle, unite, mailles, thematique}], filters_applied, themes (distinct values, to refine).MCP_indicators_query_indicator_dataGet the values of an indicator for territories (one territory, or all territories of a level). Without geographic_code, returns every territory of the level (use `year` and `limit` to keep it small: there are 13 regions, ~100 départements, ~1 250 EPCI, ~35 000 communes). Without year, returns all available years. Use find_territory to get a code from a name. Returns: JSON: indicator_id, indicator_name, unite, geographic_level, total_count, truncated, data [{geocode, libelle, annee, valeur}], annees_disponibles, cube.MCP_indicators_search_indicatorsFind indicators by keywords (French), e.g. "émissions gaz effet de serre", "surface bio", "artificialisation". Accent-, case- and plural-insensitive; all words must match (in the name, description or theme). Best matches first. Then call get_indicator_details(id) or query_indicator_data. Returns: JSON: query, total_count, indicators [{id, libelle, unite, mailles, thematique}] (max 30), truncated flag.
From Hugging Face Spaces. Report a problem