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.

Development Indicators MCP

REMOTE · INDICATORSMCP.IMPACTENGINES.AI · SCANNED OCT 1

Open-source MCP for official development indicators with provenance and citations.

54 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 Security46
Transport & Reachability100
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 530 tokens (~53/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Development Indicators MCP server?

Development Indicators MCP is a hosted endpoint at https://indicatorsmcp.impactengines.ai/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 · indicatorsmcp.impactengines.ai

# add to Claude Code
claude mcp add --transport http lbruce-wq-development-indicators 'https://indicatorsmcp.impactengines.ai/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "lbruce-wq-development-indicators": {
      "url": "https://indicatorsmcp.impactengines.ai/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "lbruce-wq-development-indicators": {
      "type": "http",
      "url": "https://indicatorsmcp.impactengines.ai/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.lbruce-wq-development-indicators]
url = "https://indicatorsmcp.impactengines.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lbruce-wq-development-indicators": {
      "type": "remote",
      "url": "https://indicatorsmcp.impactengines.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add lbruce-wq-development-indicators --url 'https://indicatorsmcp.impactengines.ai/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  lbruce-wq-development-indicators:
    url: "https://indicatorsmcp.impactengines.ai/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "lbruce-wq-development-indicators": {
      "Transport": "http",
      "Url": "https://indicatorsmcp.impactengines.ai/mcp"
    }
  }
}
# add to Vellum
assistant mcp add lbruce-wq-development-indicators -t streamable-http -u 'https://indicatorsmcp.impactengines.ai/mcp'
// mcp.json
{
  "mcpServers": {
    "lbruce-wq-development-indicators": {
      "type": "http",
      "url": "https://indicatorsmcp.impactengines.ai/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.

  • 1 Oct 26 54

    First indexed and scored.

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 1 Oct 2026 · Probed https://indicatorsmcp.impactengines.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=impactengines.ai CN=WE1,O=Google Trust Services,C=US 15 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA256 c4afcf245616cb290ebb9f4b0172c833
SANs: impactengines.ai, indicatorsmcp.impactengines.ai, *.indicatorsmcp.impactengines.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of indicatorsmcp.impactengines.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
impactengines.ai. 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://indicatorsmcp.impactengines.ai/mcp Verified 200
http (plaintext) http://indicatorsmcp.impactengines.ai/mcp Inconclusive 406
MCP tools · 10 exposed · ~454 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
compare_observations ~68

Retrieve series side by side and flag obvious metadata differences without merging them.

NameTypeReqDescription
country_codesarrayyes–
end_year–––
include_originalboolean––
latest_onlyboolean––
series_refsarrayyes–
start_year–––
NameTypeReqDescription
comparability_warningsarray––
seriesarrayyes–
source_errorsarray––

No examples provided.

faostat_list_domains ~59

List live FAOSTAT groups and domains available to build source-qualified series.

NameTypeReqDescription
cursorinteger––
group_code–––
include_archivedboolean––
limitinteger––
status–––
NameTypeReqDescription
cursorinteger––
itemsarrayyes–
next_cursor–––
totalintegeryes–

No examples provided.

faostat_search_dimension ~65

Search a FAOSTAT domain's area, item, element, unit, or other definition table.

NameTypeReqDescription
cursorinteger––
datasetstringyes–
dimensionstringyes–
limitinteger––
querystringyes–
NameTypeReqDescription
cursorinteger––
itemsarrayyes–
next_cursor–––
totalintegeryes–

No examples provided.

find_microdata ~34

Find relevant public microdata catalogues and state their access conditions.

NameTypeReqDescription
country–––
querystringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

get_indicator_metadata ~27

Retrieve authoritative metadata for a source-qualified series reference.

NameTypeReqDescription
series_refstringyes–
NameTypeReqDescription
available_dimensionsarray––
description–––
namestringyes–
series_codestringyes–
series_refstringyes–
source_idstringyes–
source_note–––
source_organization–––
source_unit–––
source_urlstringyes–
topicsarray––
unit–––

No examples provided.

get_observations ~65

Retrieve official observations while retaining metadata, citations and warnings.

NameTypeReqDescription
country_codesarrayyes–
end_year–––
include_originalboolean––
latest_onlyboolean––
series_refstringyes–
start_year–––
NameTypeReqDescription
metadata–yes–
observationsarrayyes–
queryobject––
warningsarray––

No examples provided.

get_source_setup ~26

Explain source access requirements without exposing server secrets.

NameTypeReqDescription
source_idstringyes–
NameTypeReqDescription
credential_policy–––
operator_environment_variablesarray––
registration_url–––
server_configured–––
source–yes–

No examples provided.

list_sources ~25

List supported and planned official data sources and their access characteristics.

NameTypeReqDescription
topic–––
NameTypeReqDescription
sourcesarrayyes–
totalintegeryes–
warningsarray––

No examples provided.

resolve_geographies ~42

Resolve country names or codes to ISO 3166-1 alpha-3 codes such as GHA and KEN.

NameTypeReqDescription
names_or_codesarrayyes–
NameTypeReqDescription
resolvedarray––
unresolvedarray––

No examples provided.

search_indicators ~43

Rank official indicators; returns match evidence, retrieval health and source failures.

NameTypeReqDescription
limitinteger––
querystringyes–
source_ids–––
NameTypeReqDescription
cache_hitboolean––
cached_at–––
failed_sourcesarray––
resultsarrayyes–
totalintegeryes–
warningsarray––

No examples provided.

Common questions

What is the Development Indicators MCP server?

Development Indicators MCP is listed in the public MCP registry as io.github.lbruce-wq/development-indicators. Open-source MCP for official development indicators with provenance and citations. This page covers its hosted endpoint (https://indicatorsmcp.impactengines.ai/mcp).

Is the Development Indicators MCP server safe to use?

Development Indicators MCP scores 54 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 Development Indicators MCP server expose?

Development Indicators MCP exposes 10 tools: list_sources, get_source_setup, find_microdata, search_indicators, faostat_list_domains, and 5 more. Their descriptions and schemas cost roughly 454 tokens of context every time the server is loaded.

Does the Development Indicators MCP server require authentication?

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

Is the Development Indicators MCP server still maintained?

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