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.

GroundedKit Marketing Stats Checker

REMOTE · GROUNDEDKIT.COM

Check marketing and influencer stats against primary sources: verdict, source, safe wording.

Available components

−52 this week 25 Trust /100

Last scanned (12 hours ago)

Scores higher than 10% 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 Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

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 yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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 →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Endpoint address

    Registry says
    https://groundedkit.com/mcp
    Package shows
    https://groundedkit.com/login

    The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →

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 −54
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 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.

  • 28 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.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

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://groundedkit.com/login · Declared URL https://groundedkit.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=groundedkit.com CN=YR1,O=Let's Encrypt,C=US 5 Nov 2026 3 Feb 2027 RSA 2048 SHA256-RSA 62ee0dc7d8fa0ac219464e61dbf6fdc3fd3
SANs: groundedkit.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of groundedkit.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
groundedkit.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 405
Header Value
strict-transport-security max-age=63072000

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

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://groundedkit.com/mcp Redirected 307 /login
streamable-http · followed https://groundedkit.com/login HTTP error 405
http (plaintext) http://groundedkit.com/mcp HTTPS enforced 308 https://groundedkit.com/mcp
MCP tools · 5 exposed · ~560 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
check_stat ~153

Paste a marketing or influencer-marketing statistic (a sentence or a whole paragraph), or ask for a reference number (e.g. 'what share of US adults use TikTok'). Returns the best-matching checked claim with its verdict, confidence, primary source, what the source actually says, a safe rephrasing and the claim URL, plus its kind (stat_check or reference_fact), as_of date, last_checked date and stale flag (last checked more than 180 days ago), and close alternatives. Returns match: none when the stat is not in the database.

NameTypeReqDescription
textstringyesThe statistic as you saw it, e.g. 'influencer marketing returns $5.78 per $1'

No output schema declared.

No examples provided.

get_claim ~85

Full record for one checked claim by id (slug) or claim page URL: verdict, confidence, origin, exact quote, method and sample, drift, publisher interest, safe rephrasing and every source we opened.

NameTypeReqDescription
idstringyesClaim id/slug, e.g. 'email-marketing-roi-36-to-1', or its groundedkit.com URL

No output schema declared.

No examples provided.

list_verdicts ~41

The four verdicts (verified, misquoted, outdated, unsourced) with definitions and how many claims carry each, plus confidence levels and dataset info.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_claims ~106

Keyword search over all checked marketing statistics (claim text, common phrasing, origin publisher). Optionally filter by verdict. Returns short summaries; get_claim returns the full record for an id.

NameTypeReqDescription
limitinteger–Maximum results, 1 to 50 (default 10)
querystringyesWords or numbers to search for, e.g. 'email ROI' or 'trust influencers'. Empty string lists everything.
verdictstring–Optional verdict filter

No output schema declared.

No examples provided.

verify_text ~175

Paste a whole draft (up to 20,000 characters: a blog post, deck notes, an email, a social caption). Splits it into sentences, keeps each sentence that contains a number or statistic, and matches each one against the checked claims. Returns one row per statement with the numbers found, the match level, verdict, safe rephrasing and claim URL, or status not_in_database, plus counts by status and verdict. Unmatched statistic text is logged anonymously (date and text only) to guide which stats get checked next.

NameTypeReqDescription
max_statementsinteger–Maximum statements to check, 1 to 60 (default 40)
textstringyesThe draft to check, up to 20,000 characters. Longer input is cut at 20,000 characters and flagged as truncated.

No output schema declared.

No examples provided.

Install

How do I install the GroundedKit Marketing Stats Checker MCP server?

GroundedKit Marketing Stats Checker is a hosted endpoint at https://groundedkit.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 · groundedkit.com

# add to Claude Code
claude mcp add --transport http com-groundedkit-marketing-stats 'https://groundedkit.com/mcp'
Common questions

What is the GroundedKit Marketing Stats Checker MCP server?

GroundedKit Marketing Stats Checker is an MCP server listed in the public MCP registry as com.groundedkit/marketing-stats. Check marketing and influencer stats against primary sources: verdict, source, safe wording. This page covers its hosted endpoint (https://groundedkit.com/mcp).

Is the GroundedKit Marketing Stats Checker MCP server safe to use?

GroundedKit Marketing Stats Checker scores 25 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 GroundedKit Marketing Stats Checker MCP server expose?

GroundedKit Marketing Stats Checker exposes 5 tools: check_stat, verify_text, search_claims, get_claim, list_verdicts. Their descriptions and schemas cost roughly 560 tokens of context every time the server is loaded.

Does the GroundedKit Marketing Stats Checker MCP server require authentication?

Its publisher declares no required credentials for GroundedKit Marketing Stats Checker. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the GroundedKit Marketing Stats Checker MCP server still maintained?

GroundedKit Marketing Stats Checker 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 GroundedKit Marketing Stats Checker MCP server?

VerifyMCP ran 5 checks on GroundedKit Marketing Stats Checker, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about GroundedKit Marketing Stats Checker: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.