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.

Footprint

REMOTE · 34-180-4-88.SSLIP.IO

India building growth, govt. land rates and price outlook per ~0.7 sq km area. Read-only.

+3 this week 73 Trust /100

Last scanned (18 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

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
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1121 tokens (~280/item across 4 items; 4 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 Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 82% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Tool “footprint_get_area” rewrote its description, which is the text the model reads security
    • Tool “footprint_top_areas” rewrote its description, which is the text the model reads security
  • 19 Nov 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.

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 26 +1

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

  • 12 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 11 Nov 26 69

    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 21 Nov 2026 · Probed https://34-180-4-88.sslip.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=34-180-4-88.sslip.io CN=YE1,O=Let's Encrypt,C=US 14 Oct 2026 12 Jan 2027 ECDSA 256 ECDSA-SHA384 6cb8d9e26a3081047bdde61d300025259bb
SANs: 34-180-4-88.sslip.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 34-180-4-88.sslip.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
sslip.io. No DS 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://34-180-4-88.sslip.io/mcp Verified 200
http (plaintext) http://34-180-4-88.sslip.io/mcp HTTPS enforced 308 https://34-180-4-88.sslip.io/mcp
MCP tools · 4 exposed · ~907 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
footprint_compare_areas ~169

Compare 2 to 4 areas in India side by side: price today, price outlook, building growth, how built-up, govt. rates. Use for "Whitefield vs Gachibowli", "compare these three villages". Returns a table with one column per area and a link to each area's page. Prices are labelled by kind; a city-wide average is marked and is not comparable with a govt. rate. Names take the best search match: for villages with common names, find coordinates with footprint_search_places first and pass 'lat,lon'.

NameTypeReqDescription
placesarrayyes2 to 4 places. Each is a name ('Whitefield Bengaluru') or coordinates as 'lat,lon' ('12.9698,77.7499').

No output schema declared.

No examples provided.

footprint_get_area ~278

Report on the ~0.7 sq km area at a point in India: what price figures are published, how fast it is being built on, and the price outlook. Use for questions like "how fast is Whitefield growing", "what is the govt. land rate in Karumuru", "is this locality built out". Give `place` or both `lat` and `lon` (coordinates are exact; a name takes the best match). One area only: a city's name gives the area at its centre point, and a state or district is refused (use footprint_top_areas). Returns: the latest published price with its kind and date (NHB city-wide average, govt. plot rate, or none), price outlook per year with a 5-year range, share of ground built on, building growth over 5 years, building count and height, the state's govt. plot and farmland rates with their year, nearby asking prices where listed, a reliability grade, and a link to the area's page with the charts. Covers India only.

NameTypeReqDescription
lat–––
lon–––
place––A place name, e.g. 'Whitefield Bengaluru'. Used when lat/lon are not given; takes the best match and says so if the name is ambiguous.

No output schema declared.

No examples provided.

footprint_search_places ~200

Find places in India by name and get their coordinates, to use with the other Footprint tools. Searches about 1.2 million places down to villages. Indian village names repeat heavily (dozens of Rampurs), so each match gives its kind (city, town, village, locality, district, state), its state and, for villages and localities, the nearest town ("near Zaidpur"). Returns name, kind, state, near, lat, lon for each match, best first. A pasted "lat, lon" also works.

NameTypeReqDescription
limitinteger–How many matches to return.
near_lat––Optional: rank matches near this latitude first.
near_lon––Optional: rank matches near this longitude first.
querystringyesPlace name: village, locality, town, city, district or state. E.g. 'Whitefield', 'Karumuru', 'Rampur'.

No output schema declared.

No examples provided.

footprint_top_areas ~260

List the top ~0.7 sq km areas in an Indian state or district, ranked by building growth, building count, height or price outlook. Use for "where is building fastest in Karnataka", "fastest-growing areas near Pune", "tallest neighbourhoods in Goa". Only areas with enough buildings to measure are ranked, one row per village or locality. A district is ranked as the area within about 40 km of its centre point, since district boundaries are not available. Each row gives the place, its nearest town, the ranked figure, the share of ground built on five years ago and now, and coordinates for footprint_get_area (which gives prices). A ranking, not advice.

NameTypeReqDescription
limitinteger–How many areas to return.
regionstringyesAn Indian state, union territory or district, e.g. 'Karnataka', 'Goa', 'Pune'.
sorted_bystring–building_growth: fastest built-area growth over 5 years (the default and the most informative). most_buildings: building count. tallest: average building height. price_outlook: forecast price growth…

No output schema declared.

No examples provided.

Install

How do I install the Footprint MCP server?

Footprint is a hosted endpoint at https://34-180-4-88.sslip.io/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 · 34-180-4-88.sslip.io

# add to Claude Code
claude mcp add --transport http tigermanonfire-footprint 'https://34-180-4-88.sslip.io/mcp'
Common questions

What is the Footprint MCP server?

Footprint is an MCP server listed in the public MCP registry as io.github.TigerManOnFire/footprint. India building growth, govt. land rates and price outlook per ~0.7 sq km area. Read-only. This page covers its hosted endpoint (https://34-180-4-88.sslip.io/mcp).

Is the Footprint MCP server safe to use?

Footprint 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 Footprint MCP server expose?

Footprint exposes 4 tools: footprint_search_places, footprint_get_area, footprint_top_areas, footprint_compare_areas. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.

Does the Footprint MCP server require authentication?

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

Is the Footprint MCP server still maintained?

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

What did VerifyMCP test on the Footprint MCP server?

VerifyMCP ran 13 checks on Footprint, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.