Selah: Brand Deal Rates
REMOTE · WWW.SELAH.FYI
Free creator rate benchmarks and brand-offer checks, with sources. No login, no API key.
Available components
Last scanned (9 hours ago)
Scores higher than 89% 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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 871 tokens (~435/item across 2 items; 2 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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.
- 5 Nov 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.
- 3 Nov 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.
- 1 Nov 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.
- 30 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.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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://www.selah.fyi/api/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=selah.fyi | CN=YE2,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 64493cc39ffff54824ea904600f0c255801 |
| SANs: *.selah.fyi, selah.fyi | ||||||
| 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 www.selah.fyi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fyi. | present | 6839, 24340 | 8, 8 | Verified |
| selah.fyi. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.selah.fyi/api/mcp/public | Verified | 200 | |
| http (plaintext) | http://www.selah.fyi/api/mcp/public | HTTPS enforced | 308 | https://www.selah.fyi/api/mcp/public |
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 →
selah_check_offer Check a brand offer ~439
Is this brand offer fair? Give what the brand wants (deliverable, the creator's audience size, any usage rights, exclusivity or rush) and the amount they offered, and get where the offer sits against Selah's rate for that whole scope, how it compares with published rates, and a suggested counter-offer. Use for 'a brand offered me $400 for a Reel, is that fair', 'should I accept this offer', 'what should I counter with'. Needs a deliverable, an audience size and the offered amount: ask the creator for any that are missing rather than guessing. Does not review contracts, give legal or tax advice, find brands, or price UGC, affiliate or commission-only work. Amounts are in US dollars. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_size | integer | yes | The creator's audience on the platform the deliverable is for: followers, subscribers or listeners |
| deliverable | string | yes | What the brand wants: instagram_reel, instagram_post, instagram_story (a set), tiktok_video, youtube_integration (a mention inside a video), youtube_dedicated, podcast_mention, blog_post or newslette… |
| exclusivity_months | integer | – | Months the creator may not work with competitors. 0 or omitted = none |
| offered_amount | number | yes | The total the brand offered for everything they're asking for, in US dollars |
| perpetual | boolean | – | The brand wants usage forever / in perpetuity |
| rush | boolean | – | The brand needs it faster than a normal turnaround |
| usage_months | number | – | How long the usage lasts, in months (30 days = 1, 90 days = 3). Defaults to 3 when usage_type is set and the brand named no term |
| usage_type | string | – | Usage rights the brand wants, if any. organic = the brand reposts it on their own pages; paid = the brand runs it as ads from their own account; whitelisting = ads run from the creator's handle (incl… |
No output schema declared.
No examples provided.
selah_rate_benchmark Rate benchmark ~432
What should a creator charge for a sponsored post or brand deal? Give the deliverable and the creator's audience size (and, if the brand asks for them, usage rights, exclusivity or rush) and get Selah's rate, the range published creator-rate guides give for the same thing, the add-ons priced on top, and a link to how the numbers are sourced. Use for 'how much should I charge for an Instagram Reel with 50K followers', 'how much to charge for usage rights', 'what is a fair rate for a TikTok at 25K'. Needs a deliverable and an audience size: ask the creator for them rather than guessing. Does not review contracts, give legal or tax advice, find brands, or price UGC, affiliate or commission-only work. Figures are in US dollars. No account needed.
| Name | Type | Req | Description |
|---|---|---|---|
| audience_size | integer | yes | The creator's audience on the platform the deliverable is for: followers, subscribers or listeners |
| deliverable | string | yes | What the brand wants: instagram_reel, instagram_post, instagram_story (a set), tiktok_video, youtube_integration (a mention inside a video), youtube_dedicated, podcast_mention, blog_post or newslette… |
| exclusivity_months | integer | – | Months the creator may not work with competitors. 0 or omitted = none |
| perpetual | boolean | – | The brand wants usage forever / in perpetuity |
| rush | boolean | – | The brand needs it faster than a normal turnaround |
| usage_months | number | – | How long the usage lasts, in months (30 days = 1, 90 days = 3). Defaults to 3 when usage_type is set and the brand named no term |
| usage_type | string | – | Usage rights the brand wants, if any. organic = the brand reposts it on their own pages; paid = the brand runs it as ads from their own account; whitelisting = ads run from the creator's handle (incl… |
No output schema declared.
No examples provided.
How do I install the Selah: Brand Deal Rates MCP server?
Selah: Brand Deal Rates is a hosted endpoint at https://www.selah.fyi/api/mcp/public, 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 · www.selah.fyi
claude mcp add --transport http fyi-selah-rates 'https://www.selah.fyi/api/mcp/public'
What is the Selah: Brand Deal Rates MCP server?
Selah: Brand Deal Rates is an MCP server listed in the public MCP registry as fyi.selah/rates. Free creator rate benchmarks and brand-offer checks, with sources. No login, no API key. This page covers its hosted endpoint (https://www.selah.fyi/api/mcp/public).
Is the Selah: Brand Deal Rates MCP server safe to use?
Selah: Brand Deal Rates scores 84 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 Selah: Brand Deal Rates MCP server expose?
Selah: Brand Deal Rates exposes 2 tools: selah_rate_benchmark, selah_check_offer. Their descriptions and schemas cost roughly 871 tokens of context every time the server is loaded.
Does the Selah: Brand Deal Rates MCP server require authentication?
No. We connected to Selah: Brand Deal Rates without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Selah: Brand Deal Rates MCP server still maintained?
Selah: Brand Deal Rates 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.