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.

Satelo

REMOTE · SATELO.IO

Websites promote each other: Quality Score checks, partner discovery and article placement.

Available components

+3 this week 74 Trust /100

Last scanned (23 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Marketing and SEO

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 Security63
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1291 tokens (~117/item across 11 items; 11 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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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.

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “satelo_add_site” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 46% → 53% ▲ functional
    • “satelo_add_site” added an optional parameter “ghost_admin_key” cosmetic
    • “satelo_add_site” added an optional parameter “ghost_admin_url” cosmetic
    • “satelo_add_site” added an optional parameter “ghost_drafts” cosmetic
    • “satelo_add_site” added an optional parameter “platform” cosmetic
    • “satelo_add_site” reworded the description of “method” cosmetic
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 4 Nov 2026 · Probed https://satelo.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=satelo.io CN=YE1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA384 596b4f8fc38105f0a11f412329747975267
SANs: satelo.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 satelo.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
satelo.io. 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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://satelo.io/mcp Verified 200
http (plaintext) http://satelo.io/mcp HTTPS enforced 308 https://satelo.io/mcp
MCP tools · 11 exposed · ~1,173 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
satelo_about ~60

Explains Satelo: websites promote each other with partner articles exchanged in circles (A→B→C→A), an internal currency (satellites ◉), pricing and how an AI agent can enrol a site. Call this first if unsure.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

satelo_account ~32

Requires API key. Balance in satellites, sites with status/Quality Score/prices, recent incoming and outgoing articles.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

satelo_add_site ~386

Requires API key. Adds a website to the account. Methods: "wp" = WordPress plugin (returns the connection key and steps); "ghost" = Ghost, no plugin: pass the owner's Ghost Admin API URL and Admin API key (Ghost Admin → Settings → Integrations → custom integration), Satelo verifies them and the site is active at once; "api" = any other site renders the Satelo feed (static site generators such as Hugo, Astro, Jekyll, Eleventy or Next.js use this). Drupal 10/11 and Joomla 4.4/5 sites use "wp" with platform "drupal" or "joomla": the owner installs the Satelo module (https://satelo.io/downloads/satelo-drupal.zip) or system plugin (https://satelo.io/downloads/satelo-joomla.zip) and pastes the same connection key; both are first releases. The site joins the exchange once ownership is verified; its first article (about Satelo) earns satellites.

NameTypeReqDescription
domainstringyesDomain
ghost_admin_keystring–Ghost only: Admin API key "id:secret" (secret: never publish it)
ghost_admin_urlstring–Ghost only: Admin API URL, e.g. https://blog.example.com
ghost_draftsboolean–Ghost only: create posts as drafts for the owner to publish in Ghost (default: publish)
langstring––
methodstring–wp = WordPress plugin (also Drupal module / Joomla plugin, see platform), ghost = Ghost Admin API key, api = any site renders the feed
nichestring––
platformstring–method "wp" only: which CMS the push connector runs on (default wordpress); selects the install steps

No output schema declared.

No examples provided.

satelo_check_site ~65

Free Quality Score (0–100) for any domain from open data: popularity, link graphs (Majestic, Common Crawl), domain age, content and technical health. Brand-new sites score 0.

NameTypeReqDescription
domainstringyesDomain, e.g. example.com

No output schema declared.

No examples provided.

satelo_find_hosts ~80

Requires API key. Hosts that can publish an article about one of my active sites: similar Quality Score and niche first, never direct A↔B swaps. Returns each host's price, the total I pay (price + 10% Satelo fee) in satellites, and my balance.

NameTypeReqDescription
domainstringyesMy site to promote

No output schema declared.

No examples provided.

satelo_find_sites ~93

Lists active sites in the Satelo network that accept partner articles, optionally filtered by niche, language and Quality Score range. Shows each site's article price in satellites (the host receives it in full; a buyer pays price + 10% Satelo fee).

NameTypeReqDescription
langstring––
max_qsinteger––
min_qsinteger––
nichestring––

No output schema declared.

No examples provided.

satelo_place_article ~202

Requires API key. Orders publication of an article about my site on a host from satelo_find_hosts (or the best match if host is omitted). The agent writes the article: original, useful to the host's readers, 1,500+ characters, 1–2 natural links to my site. Markup: blank line = paragraph, "## " = subheading, "- " = list, [text](https://url) = link. Spends the host's price + 10% Satelo fee in satellites; refunded automatically if not published.

NameTypeReqDescription
domainstringyesMy site to promote
hoststring–Host domain from satelo_find_hosts (optional: best match)
linkstringyesURL on my site to link to
textstringyesArticle body, 1,500–30,000 chars
titlestringyesArticle title, 10–120 chars

No output schema declared.

No examples provided.

satelo_review_article ~54

Requires API key. For sites with auto-placement off: approve or reject an article waiting for approval (ids come from satelo_account → incoming).

NameTypeReqDescription
decisionstringyes–
order_idintegeryes–

No output schema declared.

No examples provided.

satelo_signup ~67

Sends a sign-in link to the site owner's email (no password). After signing in they can create an API key for this MCP server in the dashboard. Only use with the owner's own email and consent.

NameTypeReqDescription
emailstringyesSite owner's email
langstring––

No output schema declared.

No examples provided.

satelo_site_settings ~94

Requires API key. Set auto-placement (publish incoming articles automatically), whether the site accepts articles, niche, language, or the owner's own article price in satellites (null = use Satelo's recommendation).

NameTypeReqDescription
acceptsboolean––
autoboolean––
domainstringyesDomain
langstring––
nichestring––
pricenumber|null––

No output schema declared.

No examples provided.

satelo_verify_site ~40

Requires API key. Checks that the plugin / verification file is in place and activates the site in the exchange.

NameTypeReqDescription
domainstringyesDomain

No output schema declared.

No examples provided.

Install

How do I install the Satelo MCP server?

Satelo is a hosted endpoint at https://satelo.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 · satelo.io

# add to Claude Code
claude mcp add --transport http io-satelo-satelo 'https://satelo.io/mcp'
Common questions

What is the Satelo MCP server?

Satelo is an MCP server listed in the public MCP registry as io.satelo/satelo. Websites promote each other: Quality Score checks, partner discovery and article placement. This page covers its hosted endpoint (https://satelo.io/mcp).

Is the Satelo MCP server safe to use?

Satelo scores 74 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 Satelo MCP server expose?

Satelo exposes 11 tools: satelo_about, satelo_check_site, satelo_find_sites, satelo_signup, satelo_account, and 6 more. Their descriptions and schemas cost roughly 1,173 tokens of context every time the server is loaded.

Does the Satelo MCP server require authentication?

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

Is the Satelo MCP server still maintained?

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