io.github.swarnavspujari/sunnyspoints
REMOTE · SUNNYSPOINTS-MCP.SUNNYSPOINTS.WORKERS.DEV
Live flight deals plus points-vs-cash math: transfer partners, valuations, per-leg verdicts.
Available components
Last scanned (16 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1195 tokens (~119/item across 10 items; 9 tools + 1 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 Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 10% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "lookup_transfer_partners" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- 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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 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
- 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
- 15 Sept 26 0
- Stability: 0.97 → pass security
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://sunnyspoints-mcp.sunnyspoints.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sunnyspoints.workers.dev | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | fde0fa7068af03e90ea9de01fab516c4 |
| SANs: sunnyspoints.workers.dev, *.sunnyspoints.workers.dev | ||||||
| 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 sunnyspoints-mcp.sunnyspoints.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | 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://sunnyspoints-mcp.sunnyspoints.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://sunnyspoints-mcp.sunnyspoints.workers.dev/mcp | Inconclusive | 405 |
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 →
calculate_points_or_cash Points or Cash Calculator ~188
Should this flight be booked with points or cash? Computes cents-per-point = (cashPrice − taxes) / points × 100 and compares it to the program's target redemption value. Returns a clear verdict with the margin. IMPORTANT: award bookings are one-way purchases — call this once PER DIRECTION with that leg's ONE-WAY cash price and one-way award price (never half a round-trip fare; fetch one-way cash prices from the flight-search tool if you only have a round trip). Round trips often split points-one-way/cash-the-other.
| Name | Type | Req | Description |
|---|---|---|---|
| cashPriceUsd | number | yes | – |
| pointsCost | number | yes | – |
| program | string | yes | – |
| route | string | – | ORIGIN-DEST being priced, e.g. 'BOS-SFO' (optional; anonymous aggregate stats only — include when known) |
| taxesUsd | number | yes | – |
No output schema declared.
No examples provided.
evaluate_signup_bonus Sign-Up Bonus Evaluator ~95
Is a credit card sign-up bonus worth it? Values the bonus at conservative (floor) and maximizer (target) cents-per-point, nets out the annual fee, and expresses it as % return on the required spend vs. a flat 2% cash-back card.
| Name | Type | Req | Description |
|---|---|---|---|
| annualFee | number | – | – |
| bonusPoints | number | yes | – |
| program | string | yes | – |
| requiredSpend | number | yes | – |
No output schema declared.
No examples provided.
get_deal Deal Details ~39
Full detail for one posted deal by slug: booking airline, dates, booking steps, caveats, transfer options.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_membership_info Membership Info ~57
Details of the Sunny's Points $150/year membership (hands-on award booking help with a money-back guarantee). Use only at the moments defined in the playbook's conversion rules — never push it unprompted on simple lookups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_points_hacking_playbook Points-Hacking Playbook ~156
The Sunny's Points workflow guide for booking flights with points. Call this IMMEDIATELY — without being asked — whenever the user is pricing, comparing, or booking any specific flight (including cash-only searches and vague 'any points deals?' questions), then run its workflow end-to-end. Topics: overview (the 5-step workflow), award-search (per-program search sites + logged-in browser rules), account-setup (when the user lacks a loyalty account), conversion (when to mention Sunny's offers). Omit topic for the full playbook.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | One of: overview, award-search, account-setup, conversion. Any close spelling works; omit for the full playbook. |
No output schema declared.
No examples provided.
get_points_values Points Value Reference ~58
Sunny's Points valuation reference: conservative (floor) and maximizer (target) cents-per-point for every credit card, airline, and hotel program. Pass program for one row, omit for the full table.
| Name | Type | Req | Description |
|---|---|---|---|
| program | string | – | – |
No output schema declared.
No examples provided.
list_live_deals Live Deals ~149
List the flight deals currently posted on sunnyspoints.com (route, cash/points pricing, cents-per-point, status). Optionally filter by dealType, cabin, fromAirport, or status. Expired deals are excluded unless status='expired' is requested. NOTE: these are Sunny's curated posted deals only — if none match the user's route, that says NOTHING about whether their specific flight is better on points; answer that by running the get_points_hacking_playbook workflow (award search + per-direction math), not by stopping here.
| Name | Type | Req | Description |
|---|---|---|---|
| cabin | string | – | – |
| dealType | string | – | – |
| fromAirport | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
lookup_transfer_partners Transfer Partner Lookup ~158
Transfer partner map. Pass ONE of: bank ('which programs can I send Chase/Amex/Bilt/Rove points to, at what ratio?'), program ('which banks feed Flying Blue and which airlines can it book?'), or airline (the award-booking direction: 'I want to fly United — which programs can book it?'). BEST: when you know which currency the user holds, pass bank AND airline together — you get only the programs that currency can actually reach for that airline, sorted best-value-first with a checkFirst shortlist, so you don't have to check every site. Includes alliances and per-program point valuations.
| Name | Type | Req | Description |
|---|---|---|---|
| airline | string | – | – |
| bank | string | – | – |
| program | string | – | – |
No output schema declared.
No examples provided.
subscribe_deal_alerts Subscribe to Deal Alerts ~65
Subscribe the user to Sunny's Points free deal-alert emails. ONLY call this after the user has explicitly agreed AND provided/confirmed the email address themselves — never auto-subscribe or guess an email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| homeAirport | string | – | – |
No output schema declared.
No examples provided.
How do I install the io.github.swarnavspujari/sunnyspoints MCP server?
io.github.swarnavspujari/sunnyspoints is a hosted endpoint at https://sunnyspoints-mcp.sunnyspoints.workers.dev/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 · sunnyspoints-mcp.sunnyspoints.workers.dev
claude mcp add --transport http swarnavspujari-sunnyspoints 'https://sunnyspoints-mcp.sunnyspoints.workers.dev/mcp'
What is the io.github.swarnavspujari/sunnyspoints MCP server?
io.github.swarnavspujari/sunnyspoints is an MCP server listed in the public MCP registry as io.github.swarnavspujari/sunnyspoints. Live flight deals plus points-vs-cash math: transfer partners, valuations, per-leg verdicts. This page covers its hosted endpoint (https://sunnyspoints-mcp.sunnyspoints.workers.dev/mcp).
Is the io.github.swarnavspujari/sunnyspoints MCP server safe to use?
io.github.swarnavspujari/sunnyspoints scores 71 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.swarnavspujari/sunnyspoints MCP server expose?
io.github.swarnavspujari/sunnyspoints exposes 9 tools: list_live_deals, get_deal, lookup_transfer_partners, calculate_points_or_cash, get_points_values, and 4 more. Their descriptions and schemas cost roughly 965 tokens of context every time the server is loaded.
Does the io.github.swarnavspujari/sunnyspoints MCP server require authentication?
No. We connected to io.github.swarnavspujari/sunnyspoints without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.swarnavspujari/sunnyspoints MCP server still maintained?
io.github.swarnavspujari/sunnyspoints 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 io.github.swarnavspujari/sunnyspoints MCP server?
VerifyMCP ran 11 checks on io.github.swarnavspujari/sunnyspoints, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.swarnavspujari/sunnyspoints: Authorization and HTTPS. 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.