io.github.gustavoatar/instafan
REMOTE · INSTAFAN.APP
Plan trips with friends: mood search, live briefs, top spots with photos, day-by-day itineraries.
Available components
Last scanned (11 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Maps and Location
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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
- Tool/resource definitions use about 567 tokens (~94/item across 6 items; 5 tools + 1 resources), lean.Pass
- 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
- 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
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 →
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.
- 6 Nov 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
- 3 Oct 26 0
- Stability: 0.97 → pass security
- 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
- 17 Sept 26 0
- Authorization: unverified → partial ▲ security
- HSTS header: unverified → pass ▲ security
- 16 Sept 26 0
- Authorization: partial → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- 4 Sept 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 78 → 94 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “build_itinerary” now declares an output schema ▲ functional
- Tool “destination_brief” now declares an output schema ▲ functional
- Tool “find_destinations” now declares an output schema ▲ functional
- Tool “spot_photos” now declares an output schema ▲ functional
- Tool “top_spots” now declares an output schema ▲ functional
- The server now declares the “resources” capability functional
- First check of Capabilities: pass functional
- First check of Schema quality: 100 functional
- First check of Tool coverage: 100 functional
- New resource “Instafan trip card” functional
- 3 Sept 26 0
First indexed and scored.
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 6 Nov 2026 · Probed https://instafan.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=instafan.app | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ec8f940097d41bf10eae3a5b31d04479 |
| SANs: instafan.app | ||||||
| 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 instafan.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| instafan.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://instafan.app/mcp | Verified | 200 | |
| http (plaintext) | http://instafan.app/mcp | HTTPS enforced | 301 | https://instafan.app/mcp |
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 →
build_itinerary ~67
Build a day-by-day itinerary for a destination from its strongest real places. Returns the plan plus links to run it as a group trip on Instafan.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | yes | Trip length in days, 1-7 |
| destination | string | yes | City or place name |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full answer, ready to show the traveller |
| links | object | – | Instafan continuation links — include them in the reply |
| photo_urls | array | – | Public photo URLs mentioned in the answer, when any |
No examples provided.
destination_brief ~56
A short brief on one destination: what it is like, typical weather now, official safety verdict. Use before or instead of a full itinerary.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | City or place name, e.g. "Lisbon" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full answer, ready to show the traveller |
| links | object | – | Instafan continuation links — include them in the reply |
| photo_urls | array | – | Public photo URLs mentioned in the answer, when any |
No examples provided.
find_destinations ~64
Suggest 3-5 destinations for a trip mood or constraint set, e.g. "somewhere warm in November, food-first". Use when the traveller has not settled on a place yet.
| Name | Type | Req | Description |
|---|---|---|---|
| mood | string | yes | The trip mood or constraints, in plain words |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full answer, ready to show the traveller |
| links | object | – | Instafan continuation links — include them in the reply |
| photo_urls | array | – | Public photo URLs mentioned in the answer, when any |
No examples provided.
spot_photos ~77
Real photos of one spot — up to two shown inline plus direct photo links. Name a specific place ("Belém Tower") or leave spot empty for a postcard of the destination itself.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | City or place name |
| spot | string | – | Optional: one specific place, e.g. "Belém Tower" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full answer, ready to show the traveller |
| links | object | – | Instafan continuation links — include them in the reply |
| photo_urls | array | – | Public photo URLs mentioned in the answer, when any |
No examples provided.
top_spots ~79
The strongest real places in a destination — top attractions by default, or a specific ask like "specialty coffee" or "rooftop bars". Real Google-rated places, never invented.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | City or place name |
| query | string | – | Optional: what kind of spots, e.g. "seafood dinner" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | The full answer, ready to show the traveller |
| links | object | – | Instafan continuation links — include them in the reply |
| photo_urls | array | – | Public photo URLs mentioned in the answer, when any |
No examples provided.
How do I install the io.github.gustavoatar/instafan MCP server?
io.github.gustavoatar/instafan is a hosted endpoint at https://instafan.app/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 · instafan.app
claude mcp add --transport http gustavoatar-instafan 'https://instafan.app/mcp'
What is the io.github.gustavoatar/instafan MCP server?
io.github.gustavoatar/instafan is an MCP server listed in the public MCP registry as io.github.gustavoatar/instafan. Plan trips with friends: mood search, live briefs, top spots with photos, day-by-day itineraries. This page covers its hosted endpoint (https://instafan.app/mcp).
Is the io.github.gustavoatar/instafan MCP server safe to use?
io.github.gustavoatar/instafan scores 88 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 io.github.gustavoatar/instafan MCP server expose?
io.github.gustavoatar/instafan exposes 5 tools: find_destinations, destination_brief, top_spots, build_itinerary, spot_photos. Their descriptions and schemas cost roughly 343 tokens of context every time the server is loaded.
Does the io.github.gustavoatar/instafan MCP server require authentication?
No. We connected to io.github.gustavoatar/instafan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.gustavoatar/instafan MCP server still maintained?
io.github.gustavoatar/instafan is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.gustavoatar/instafan MCP server?
VerifyMCP ran 14 checks on io.github.gustavoatar/instafan, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.