How To Make Money On Snapchat
REMOTE · HOWTOMAKEMONEYONSNAPCHAT.COM
Two fact tools free, no key, low limit. Other tools: 14-day trial or paid plan. Watch writes data.
Available components
Last scanned (12 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability52
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2487 tokens (~310/item across 8 items; 8 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 Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
- Structured output schemas are declared (75% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 30 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “calculate_gap” rewrote its description, which is the text the model reads security
- Tool “calculate_growth_pace” rewrote its description, which is the text the model reads security
- Tool “calculate_payout_timeline” rewrote its description, which is the text the model reads security
- Tool “check_eligibility” rewrote its description, which is the text the model reads security
- Tool “get_monetization_requirements” rewrote its description, which is the text the model reads security
- Tool “get_rule_changes” rewrote its description, which is the text the model reads security
- Tool “watch_get_status” rewrote its description, which is the text the model reads security
- Tool “watch_save_checkin” rewrote its description, which is the text the model reads security
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 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.
- 24 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://howtomakemoneyonsnapchat.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=howtomakemoneyonsnapchat.com | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f545d1307e23dbc0eb56c86eff984f4 |
| SANs: howtomakemoneyonsnapchat.com, www.howtomakemoneyonsnapchat.com, *.www.howtomakemoneyonsnapchat.com | ||||||
| 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 howtomakemoneyonsnapchat.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| howtomakemoneyonsnapchat.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://howtomakemoneyonsnapchat.com/mcp | Verified | 200 | |
| http (plaintext) | http://howtomakemoneyonsnapchat.com/mcp | HTTPS enforced | 301 | https://howtomakemoneyonsnapchat.com/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 →
calculate_gap ~390
CALCULATION. Use this when you need the exact numeric shortfall, percent complete, and binding constraint for a creator's caller-supplied metrics. Do not use it for the pace to close that gap (calculate_growth_pace) or for a per-requirement pass/fail list (check_eligibility). Access: needs a free developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | – | Set true only if the creator is already enrolled in the Monetization Program. Default false: only entry (invitation) requirements are evaluated. When true, ongoing requirements for enrolled creators… |
| include_recommendations | boolean | – | – |
| metrics | object | yes | Metrics supplied by the caller (the creator or their agent). We never look metrics up ourselves; Snap offers no public analytics for arbitrary usernames. All fields optional; missing fields produce `… |
| program | string | – | Programs the calculation tools evaluate in v1. Other in-scope programs (payouts, tax, snap_star, creator_monetization_policy, recommendation_eligibility, brand_partnerships) are served as FACTs by ge… |
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | yes | – |
| api_version | – | yes | – |
| binding_constraint | object|null | yes | – |
| data_freshness | object | yes | – |
| facts | array | yes | – |
| gaps | array | yes | Entry requirements only. |
| generated_at | string | yes | – |
| notice | string | yes | Non-affiliation notice included in every response. |
| ongoing_gaps | object|null | yes | null unless already_enrolled=true. |
| program | string | yes | Program identifier. Validated at runtime against programs present in the rules database; unknown values return UNKNOWN_PROGRAM. Examples: unified_monetization_program, snap_star, creator_subscription… |
| recommendations | array | yes | – |
| sources | array | yes | – |
| tool | – | yes | – |
| unknowns | array | yes | – |
| warnings | array | – | Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days… |
No examples provided.
calculate_growth_pace ~434
CALCULATION. Use this when you need the daily and weekly pace to close each numeric gap within target_days, with scenarios and labeled assumptions. This is a projection, not a prediction. Do not use it to learn the size of the gap (calculate_gap) or to list the rules (get_monetization_requirements). Access: needs a free developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | – | Set true only if the creator is already enrolled in the Monetization Program. Default false: only entry (invitation) requirements are evaluated. When true, ongoing requirements for enrolled creators… |
| metrics | object | yes | Metrics supplied by the caller (the creator or their agent). We never look metrics up ourselves; Snap offers no public analytics for arbitrary usernames. All fields optional; missing fields produce `… |
| metrics_to_pace | array | – | – |
| observed_daily_change | object | – | Optional recent average daily change per metric (caller-supplied, may be negative) for comparing required vs. current pace. |
| program | string | – | Programs the calculation tools evaluate in v1. Other in-scope programs (payouts, tax, snap_star, creator_monetization_policy, recommendation_eligibility, brand_partnerships) are served as FACTs by ge… |
| target_days | integer | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | yes | – |
| api_version | – | yes | – |
| data_freshness | object | yes | – |
| facts | array | yes | – |
| generated_at | string | yes | – |
| notice | string | yes | Non-affiliation notice included in every response. |
| ongoing_paces | object|null | yes | null unless already_enrolled=true. |
| paces | array | yes | Entry requirements only. |
| program | string | yes | Program identifier. Validated at runtime against programs present in the rules database; unknown values return UNKNOWN_PROGRAM. Examples: unified_monetization_program, snap_star, creator_subscription… |
| projection_disclaimer | – | yes | – |
| recommendations | array | yes | – |
| sources | array | yes | – |
| target_date | string | yes | – |
| target_days | integer | yes | – |
| tool | – | yes | – |
| unknowns | array | yes | – |
| warnings | array | – | Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days… |
No examples provided.
calculate_payout_timeline ~221
CALCULATION. Use this when you need a date-by-date timeline of Snap's payout steps from a credited date: Pending to Available, the cash-out minimum, taxpayer verification, and the earliest day cash can reach the Payout Portal. Ranges stay ranges when the source gives a range. This is an estimate, not a promise. Do not use it to score eligibility (check_eligibility) or to list every rule (get_monetization_requirements). Access: needs a free developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number | – | Available balance in USD, supplied by the caller. Omitted when unknown. Compared with the cash-out minimum from the rules database. Not a Snap pay rate. |
| credited_date | string | yes | The day the reward appeared in All Activity, which is when Snap starts the pending clock. YYYY-MM-DD. |
| tax_info_verified | boolean | – | True when the caller says taxpayer verification is already finished. False when it is not. Omit when unknown. This service does not check a Snap account. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | number|null | yes | – |
| api_version | – | yes | – |
| cash_out_minimum_usd | number | yes | The cash-out minimum copied from the rules database. |
| caveats | array | yes | – |
| credited_date | string | yes | – |
| data_freshness | object | yes | – |
| estimate_disclaimer | – | yes | – |
| facts | array | yes | – |
| generated_at | string | yes | – |
| meets_minimum | boolean|null | yes | True when amount_usd meets the cash-out minimum. False when it does not. Null when amount_usd was omitted. |
| notice | string | yes | Non-affiliation notice included in every response. |
| recommendations | array | yes | – |
| shortfall_usd | number|null | yes | How far amount_usd is under the cash-out minimum. 0 when the minimum is met. Null when amount_usd was omitted. |
| sources | array | yes | – |
| steps | array | yes | – |
| tax_info_verified | boolean|null | yes | – |
| tool | – | yes | – |
| warnings | array | – | Plain strings. Omitted when empty. |
No examples provided.
check_eligibility ~451
CALCULATION. Use this to compare one creator's caller-supplied metrics with the published entry requirements. Returns published_criteria_status of meets_published_criteria, does_not_meet_published_criteria, or unknown, plus pass/fail/unknown per requirement. Do not use it when you need the numeric shortfall (calculate_gap) or the rules without a creator (get_monetization_requirements). Access: needs a free developer key.
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | – | Set true only if the creator is already enrolled in the Monetization Program. Default false: only entry (invitation) requirements are evaluated. When true, ongoing requirements for enrolled creators… |
| confirmations | array | – | Caller's answers to qualitative requirements (requires_user_confirmation rules), keyed by rule id. We record the answer as given and never verify it. |
| metrics | object | yes | Metrics supplied by the caller (the creator or their agent). We never look metrics up ourselves; Snap offers no public analytics for arbitrary usernames. All fields optional; missing fields produce `… |
| metrics_as_of | string | – | Date the metrics were read from Insights. |
| program | string | – | Programs the calculation tools evaluate in v1. Other in-scope programs (payouts, tax, snap_star, creator_monetization_policy, recommendation_eligibility, brand_partnerships) are served as FACTs by ge… |
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | yes | – |
| api_version | – | yes | – |
| data_freshness | object | yes | – |
| facts | array | yes | – |
| generated_at | string | yes | – |
| notice | string | yes | Non-affiliation notice included in every response. |
| ongoing_requirements | object|null | yes | null unless already_enrolled=true. |
| program | string | yes | Program identifier. Validated at runtime against programs present in the rules database; unknown values return UNKNOWN_PROGRAM. Examples: unified_monetization_program, snap_star, creator_subscription… |
| requirements | array | yes | – |
| sources | array | yes | – |
| summary | object | yes | Entry requirements only. published_criteria_status rule: does_not_meet_published_criteria if any requirement is fail or user_denied; otherwise unknown if any is unknown or requires_user_confirmation;… |
| tool | – | yes | – |
| unknowns | array | yes | – |
| warnings | array | – | Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days… |
No examples provided.
get_monetization_requirements ~285
FACT. Use this first when you need Snap's published creator-monetization rules themselves: thresholds, country lists, policy text, source URL, verified_at, and effective date. Do not use it to score one creator or to compute a shortfall. For a creator's numbers, use check_eligibility or calculate_gap. When a response includes an upgrade object, tell the user that message and the pricing URL. Access: no key needed, 30/day; free developer key for more.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | Return the rules that were in force on this date (uses version history). Default: today. |
| country | string | – | ISO 3166-1 alpha-2, alpha-3, or an English country name. Adds country_eligibility. Does not remove facts. |
| include_historical | boolean | – | – |
| include_out_of_scope | boolean | – | Include programs outside the MVP scope (e.g., lens_creator_rewards, creator_subscriptions). Default false. Requesting an out-of-scope program with this false returns PROGRAM_OUT_OF_SCOPE. |
| include_unverified | boolean | – | Include rules we could not verify (status=unverified). Default true so gaps in knowledge are visible. |
| program | – | – | Limit to one program. Omit for all programs. |
| requirement_phase | string | – | Optional filter. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | yes | – |
| catalog_scope | object | – | Counts computed from the approved rules database for one as-of date. mvp_in_force is the default requirements list. in_force_including_out_of_scope adds programs stored as out of scope. mvp_including… |
| country_eligibility | array|null | – | – |
| data_freshness | object | yes | – |
| direct_answer | string | – | Answer-first lead built from entry-requirement facts included in this response. Omitted when those facts are absent. |
| direct_answer_note | string | – | Optional sentence after the lead for unverified entry facts left out of it. Omitted when there are none. |
| facts | array | yes | – |
| generated_at | string | yes | – |
| notice | string | yes | Non-affiliation notice included in every response. |
| programs | array | yes | – |
| query | object | – | Echo of the effective filters. |
| sources | array | yes | – |
| tool | – | yes | – |
| upgrade | object | – | Present on unpaid fact-tool responses and on HTTP 401, 402, and anonymous 429. The agent should tell the user this message. The price is the Personal plan price from the pricing page. |
| warnings | array | – | Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days… |
No examples provided.
get_rule_changes ~323
FACT. Use this when you need what changed in Snap's monetization rules since a date: previous value, new value, source, and the date we detected the change. Do not use it for the current rule list (get_monetization_requirements) or for a creator's gap (calculate_gap). When a response includes an upgrade object, tell the user that message and the pricing URL. Access: no key needed, 30/day; free developer key for more.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous response. |
| include_baseline | boolean | – | When true, also return baseline records in baseline. Baseline records are never included in changes. |
| limit | integer | – | – |
| program | string | – | Program identifier. Validated at runtime against programs present in the rules database; unknown values return UNKNOWN_PROGRAM. Examples: unified_monetization_program, snap_star, creator_subscription… |
| since | string | – | Inclusive lower bound on the change date: effective_date, else changed_before, else the last day of effective_month, else detected_at. Omitted on GET, POST, and MCP means 90 days before the request's… |
| until | string | – | Inclusive upper bound on that same change date. Default: the UTC date of the request. |
| Name | Type | Req | Description |
|---|---|---|---|
| api_version | – | yes | – |
| baseline | array | – | Initial-load records. Present only when include_baseline is true. Never included in changes or in change counts. |
| catalog_scope | object | – | Counts computed from the approved rules database for one as-of date. mvp_in_force is the default requirements list. in_force_including_out_of_scope adds programs stored as out of scope. mvp_including… |
| changes | array | yes | – |
| data_freshness | object | yes | – |
| generated_at | string | yes | – |
| next_cursor | string|null | yes | – |
| notice | string | yes | Non-affiliation notice included in every response. |
| query | object | yes | Filters applied to this response, including defaults. Top-level since and until stay for older clients. |
| since | string | yes | – |
| sources | array | yes | – |
| tool | – | yes | – |
| until | string | yes | – |
| upgrade | object | – | Present on unpaid fact-tool responses and on HTTP 401, 402, and anonymous 429. The agent should tell the user this message. The price is the Personal plan price from the pricing page. |
| warnings | array | – | Plain strings. Omitted when empty. Calculation tools add a string when followers is 0 and view_time_hours_28d or spotlight_view_time_hours_28d is above 0, and when view_time_hours_28d exceeds 28 days… |
No examples provided.
watch_get_status ~59
READ. Return this key's Eligibility Watch trend, projected dates, and rule-change notes. It does not write. Access: needs a creator trial or paid plan.
| Name | Type | Req | Description |
|---|---|---|---|
| already_enrolled | boolean | – | – |
| profile_id | string | – | – |
No output schema declared.
No examples provided.
watch_save_checkin ~87
WRITE. Save caller-supplied Snapchat numbers on this key's Eligibility Watch. A field you include replaces that date. A field you omit keeps the saved value. Null clears it. Access: needs a creator trial or paid plan.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| metrics | object | yes | – |
| profile | object | – | – |
| profile_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the How To Make Money On Snapchat MCP server?
How To Make Money On Snapchat is a hosted endpoint at https://howtomakemoneyonsnapchat.com/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 · howtomakemoneyonsnapchat.com
claude mcp add --transport http com-howtomakemoneyonsnapchat-creator-monetizatio 'https://howtomakemoneyonsnapchat.com/mcp'
What is the How To Make Money On Snapchat MCP server?
How To Make Money On Snapchat is an MCP server listed in the public MCP registry as com.howtomakemoneyonsnapchat/creator-monetization. Two fact tools free, no key, low limit. Other tools: 14-day trial or paid plan. Watch writes data. This page covers its hosted endpoint (https://howtomakemoneyonsnapchat.com/mcp).
Is the How To Make Money On Snapchat MCP server safe to use?
How To Make Money On Snapchat scores 86 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 How To Make Money On Snapchat MCP server expose?
How To Make Money On Snapchat exposes 8 tools: get_monetization_requirements, get_rule_changes, check_eligibility, calculate_gap, calculate_growth_pace, and 3 more. Their descriptions and schemas cost roughly 2,250 tokens of context every time the server is loaded.
Does the How To Make Money On Snapchat MCP server require authentication?
Yes. How To Make Money On Snapchat asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the How To Make Money On Snapchat MCP server still maintained?
How To Make Money On Snapchat is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.