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.

UpGrow Instagram Growth

REMOTE · WWW.UPGROW.COM

UpGrow Instagram growth MCP server: plans, one-time shop, free Instagram tools and blog search.

Available components

74 Trust /100

Last scanned (14 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 6 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 Security83
  • 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 303 tokens (~50/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 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
  • 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 6 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

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.

  • 6 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 5 Nov 26 74

    First indexed and scored.

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 6 Nov 2026 · Probed https://www.upgrow.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=upgrow.com CN=YE1,O=Let's Encrypt,C=US 12 Sept 2026 11 Dec 2026 ECDSA 256 ECDSA-SHA384 67525ca77375ee8b40737a66b03beed0239
SANs: *.upgrow.com, email.growth.upgrow.com, upgrow.com
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 secure

Validation of www.upgrow.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
upgrow.com. DS published 2371 13 Verified
www.upgrow.com. Verified address RRset verified with the apex keys
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
content-security-policy default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https: blob: data:; style-src 'self' 'unsafe-inline' https:; img-src * blob: data:; media-src 'self' https: blob: data:; connect-src 'self' https: wss:; font-src 'self' data: https:; frame-src 'self' https:; worker-src 'self' blob: data:; object-src 'none'; base-uri 'self'; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options DENY
referrer-policy 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://www.upgrow.com/mcp Verified 200
http (plaintext) http://www.upgrow.com/mcp HTTPS enforced 301 https://www.upgrow.com/mcp
MCP tools · 6 exposed · ~252 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
get_company_facts ~37

What UpGrow is and how it works: the service in plain words, how to start, guarantees, support contacts and countries served.

Input schema present but exposes no named parameters.

NameTypeReqDescription
namestringyes–
summarystringyes–

No examples provided.

get_signup_link ~32

Get the link where a user starts with UpGrow (sign-up and setup), plus the pricing and shop pages.

Input schema present but exposes no named parameters.

NameTypeReqDescription
signupUrlstringyes–

No examples provided.

list_free_tools ~33

List the free UpGrow Instagram tools with a one-line description and link for each. No sign-up or password needed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
toolsarrayyes–

No examples provided.

list_plans ~37

List the UpGrow growth plans (Basic, Pro, Turbo) with the first-month price, what each includes and the sign-up link.

Input schema present but exposes no named parameters.

NameTypeReqDescription
plansarrayyes–

No examples provided.

list_products ~56

List the one-time UpGrow shop products (Instagram and TikTok followers, likes, views, comments) with starting prices, tiers and product page links. No subscription.

NameTypeReqDescription
platformstring–Optional: only products for this platform.
NameTypeReqDescription
productsarrayyes–

No examples provided.

search_blog ~57

Search UpGrow blog posts about Instagram growth, returning titles, links and descriptions.

NameTypeReqDescription
limitinteger–Maximum results, 1-10 (default 5).
qstringyesSearch text, 2-100 characters.
NameTypeReqDescription
countintegeryes–
querystringyes–
resultsarrayyes–

No examples provided.

Install

How do I install the UpGrow Instagram Growth MCP server?

UpGrow Instagram Growth is a hosted endpoint at https://www.upgrow.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 · www.upgrow.com

# add to Claude Code
claude mcp add --transport http com-upgrow-instagram-growth 'https://www.upgrow.com/mcp'
Common questions

What is the UpGrow Instagram Growth MCP server?

UpGrow Instagram Growth is an MCP server listed in the public MCP registry as com.upgrow/instagram-growth. UpGrow Instagram growth MCP server: plans, one-time shop, free Instagram tools and blog search. This page covers its hosted endpoint (https://www.upgrow.com/mcp).

Is the UpGrow Instagram Growth MCP server safe to use?

UpGrow Instagram Growth 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 UpGrow Instagram Growth MCP server expose?

UpGrow Instagram Growth exposes 6 tools: list_plans, list_products, list_free_tools, search_blog, get_company_facts, get_signup_link. Their descriptions and schemas cost roughly 252 tokens of context every time the server is loaded.

Does the UpGrow Instagram Growth MCP server require authentication?

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

Is the UpGrow Instagram Growth MCP server still maintained?

UpGrow Instagram Growth 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 UpGrow Instagram Growth MCP server?

VerifyMCP ran 13 checks on UpGrow Instagram Growth, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.