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.

Location & Demand Intelligence

REMOTE · API.TIMZININ.COM · SCANNED OCT 12

Pay-per-call where-and-when-to-operate signals from official local statistics.

Available components

0 this week 82 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 Security74
Transport & Reachability100
Schema Quality & AI Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1449 tokens (~207/item across 7 items; 7 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 8 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
Install

How do I install the Location & Demand Intelligence MCP server?

Location & Demand Intelligence is a hosted endpoint at https://api.timzinin.com/mcp/location-demand-intelligence, 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.timzinin.com

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

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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 14 Sept 26 +1
    • Stability: 0.97 → pass security
  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Aug 26 0
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 180 → 207 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Tool “afad-earthquake-operations-router” changed its title: AFAD Earthquake Operations Router cosmetic
    • Tool “ispark-metro-destination-access-scorer” changed its title: İSPARK & Metro Destination Access Scorer cosmetic
    • Tool “mois-neighborhood-age-demand-scorer” changed its title: MOIS Neighborhood Age Demand Scorer cosmetic
    • Tool “mois-solo-household-demand-scorer” changed its title: MOIS Solo Household Demand Scorer cosmetic
    • Tool “pricing_info” changed its title: Pricing — Location & Demand Intelligence cosmetic
    • Tool “sahibindex-property-market-benchmark” changed its title: Sahibindex Property Market Benchmark cosmetic
    • Tool “traffic-index-operating-window-planner” changed its title: İBB Traffic Operating Window Planner cosmetic
  • 15 Aug 26 0

    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 12 Oct 2026 · Probed https://api.timzinin.com/mcp/location-demand-intelligence

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.timzinin.com CN=YE2,O=Let's Encrypt,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA384 6a81be6512ce92fb1cd3c146aae5613dac3
SANs: api.timzinin.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.timzinin.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
timzinin.com. 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.timzinin.com/mcp/location-demand-intelligence Verified 200
http (plaintext) http://api.timzinin.com/mcp/location-demand-intelligence HTTPS enforced 301 https://api.timzinin.com/mcp/location-demand-intelligence
MCP tools · 7 exposed · ~1,266 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
afad-earthquake-operations-router ~298

Turn official AFAD events into distance-based asset and route actions. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
alertRadiusKmnumberyesOnly event–asset pairs within this straight-line distance can become alerts.
assetsarrayyesOne to 100 customer-owned operational points. Use opaque non-PII asset IDs.
inspectMagnitudenumberyesAt or above this magnitude a matching site receives inspect_asset_and_review.
maxAlertsintegeryesReturns the highest-priority matching event–asset pairs, up to this limit.
maxTotalChargeUsdnumberyesHard run cap checked before any alert claim or paid delivery.
maximumDepthKmnumberyesEvents deeper than this are ignored.
maximumEventAgeHoursintegeryesIgnores older rows even if they remain in the last-100 list.
minimumMagnitudenumberyesEvents below this AFAD magnitude are ignored.
pauseDispatchMagnitudenumberyesAt or above this magnitude a matching non-route asset receives pause_dispatch_and_review.
requestIdstringyesUnique non-PII idempotency ID. Reusing it with changed inputs fails.
rerouteMagnitudenumberyesAt or above this magnitude a matching route waypoint receives reroute_for_review.

No output schema declared.

No examples provided.

ispark-metro-destination-access-scorer ~234

Score customer sites against official Metro stations and İSPARK capacity. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
maxTotalChargeUsdnumberyesMaximum accepted total run charge. A 100-site default-price batch needs at least $2.005 including Actor start.
minimumEmptySpacesintegeryesFlags the nearest İSPARK facility when its reported live empty capacity is below this threshold.
parkingReferenceMetersintegeryesParking proximity reaches zero at and beyond this straight-line distance.
railReferenceMetersintegeryesMetro proximity reaches zero at and beyond this straight-line distance.
railWeightnumberyesShare of the final score assigned to metro proximity. Parking receives one minus this value.
requestIdstringyesUnique non-PII idempotency ID. Reusing it with different decision inputs fails.
sitesarrayyesOne to 100 customer-owned site IDs and coordinates inside the bounded Istanbul service area.

No output schema declared.

No examples provided.

mois-neighborhood-age-demand-scorer ~160

Score neighborhoods from official resident age cohorts with customer-defined weights. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
cohortWeightsarrayyesNon-overlapping inclusive age bands; age 110 means 110+.
maxTotalChargeUsdnumberyesMaximum total run charge in addition to the platform cap.
peerAdminCodesarrayyesTwo to 200 official codes; must include every target.
requestIdstringyesStable idempotency key without personal data.
targetAdminCodesarrayyesOne to 20 official 10-digit administrative-neighborhood codes to score.

No output schema declared.

No examples provided.

mois-solo-household-demand-scorer ~160

Rank territories by official one-person-household age composition. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.05/call, x402 (USDC on base).

NameTypeReqDescription
ageWeightsarrayyesNon-overlapping inclusive age bands; age 110 means 110+.
maxTotalChargeUsdnumberyesMaximum total run charge in addition to the platform cap.
peerLegalCodesarrayyesTwo to 200 official codes; must include every target.
requestIdstringyesStable idempotency key without personal data.
targetLegalCodesarrayyesOne to 20 official 10-digit legal-district codes to score.

No output schema declared.

No examples provided.

pricing_info ~45

Free — list every paid tool in the 'location-demand-intelligence' bundle with its price, payTo address and network. Call this first if you don't have a wallet ready yet.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sahibindex-property-market-benchmark ~241

Compare customer-owned property facts with licensed public Sahibindex market reports. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
deviationThresholdPctnumber–Absolute price-per-m² deviation that triggers below/above aggregate review.
maxReportAgeMonthsinteger–Fail if the aggregate reference period is older than this many months.
maxTotalChargeUsdnumberyesHard run cap checked for the entire set of new benchmarks before any claim.
propertiesarrayyesOne to 50 customer-owned fact sets. Do not submit an address, owner name, contact data or listing URL.
reportUrlstring–Optional exact image5.sahibinden.com staticContent PDF. The PDF must identify itself as a public sale-market Sahibindex/BETAM report.
requestIdstringyesUnique non-PII idempotency ID. Reuse is allowed only with identical decision inputs.
slowMarketDaysnumber–Closed-listing age at or above this value is labelled slow.

No output schema declared.

No examples provided.

traffic-index-operating-window-planner ~128

Convert official hourly traffic history into explainable low-congestion operating windows. Unofficial, independent Actor; not affiliated with or endorsed by any named source publisher. — $0.02/call, x402 (USDC on base).

NameTypeReqDescription
maxTotalChargeUsdnumberyesChecked before any decision claim and again by the Apify platform.
requestIdstringyesReuse only for the exact same input. A changed payload with the same key fails closed.
windowsarrayyesOne paid decision at most per new, non-duplicate window plan.

No output schema declared.

No examples provided.

Common questions

What is the Location & Demand Intelligence MCP server?

Location & Demand Intelligence is an MCP server listed in the public MCP registry as com.timzinin.api/location-demand-intelligence. Pay-per-call where-and-when-to-operate signals from official local statistics. This page covers its hosted endpoint (https://api.timzinin.com/mcp/location-demand-intelligence).

Is the Location & Demand Intelligence MCP server safe to use?

Location & Demand Intelligence scores 82 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 Location & Demand Intelligence MCP server expose?

Location & Demand Intelligence exposes 7 tools: pricing_info, afad-earthquake-operations-router, ispark-metro-destination-access-scorer, mois-neighborhood-age-demand-scorer, mois-solo-household-demand-scorer, and 2 more. Their descriptions and schemas cost roughly 1,266 tokens of context every time the server is loaded.

Does the Location & Demand Intelligence MCP server require authentication?

No. We connected to Location & Demand Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Location & Demand Intelligence MCP server still maintained?

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