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.

KitScout

REMOTE · MCP.KITSCOUT.DEV

Check MCP servers, skills and plugins before installing: maker, upkeep, live status. 90k tools.

Available components

72 Trust /100

Last scanned (19 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 896 tokens (~224/item across 4 items; 4 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 Management20
  • Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_tools” rewrote its description, which is the text the model reads security
    • Tool “get_tool” rewrote its description, which is the text the model reads security
    • Tool “list_categories” rewrote its description, which is the text the model reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
    • Schema quality: 169 → 224 ▼ functional
    • Schema quality: good → excellent functional
  • 19 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Tool “check_tools” rewrote its description, which is the text the model reads security
    • Tool “get_tool” rewrote its description, which is the text the model reads security
    • Tool “search_tools” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +1

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

  • 16 Nov 26 0
    • Tool “check_tools” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.0.2 functional
  • 15 Nov 26 70

    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 21 Nov 2026 · Probed https://mcp.kitscout.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kitscout.dev CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 cfb925dd11dec88113c06f9c136ff507
SANs: kitscout.dev, mcp.kitscout.dev, *.mcp.kitscout.dev
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 mcp.kitscout.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
kitscout.dev. No DS 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.kitscout.dev/mcp Verified 200
http (plaintext) http://mcp.kitscout.dev/mcp HTTPS enforced 301 https://mcp.kitscout.dev/mcp
MCP tools · 4 exposed · ~570 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_tools ~175

Checks MCP servers, skills or plugins found elsewhere (web search, a README, a blog, an installed list) before they are installed or recommended: made by the product's maker or not, maintained (last code change, archived, deprecated), adopted (stars), whether a remote server answers right now and where data goes. Returns a verdict (ok / caution / avoid; not a security review), the new name for renamed tools and better-adopted alternatives. A repo holding several skills or plugins is answered as one collection with its count and examples. Takes up to 5 GitHub URLs, package ids (npm/pypi), remote MCP URLs or names per call.

NameTypeReqDescription
toolsarrayyese.g. https://github.com/owner/repo, @scope/package, https://mcp.example.com/mcp

No output schema declared.

No examples provided.

get_tool ~88

Details and install or connect lines for one tool, by its exact name from search_tools: description, badges, stars, repo, how to install or connect (Claude Code command, Claude app connector steps), and for remote MCP servers the tools the server exposes (from the daily live check). An unknown name returns close matches.

NameTypeReqDescription
namestringyesExact tool name as listed in KitScout

No output schema declared.

No examples provided.

list_categories ~31

Lists all KitScout categories (id, name, group, tool count), to see what kinds of tools exist.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tools ~276

Finds MCP servers, connectors, Agent Skills and Claude Code plugins for a product or task among ~92k AI agent tools. Returns ranked matches with type, category, GitHub stars, badges (first_party = made by the product's own maker, verified_publisher, live, free_to_try), install line and KitScout page. Works best with short keywords: product + action, e.g. 'postgres', 'slack post message', 'pdf extract tables'. Also finds ready-made tools for single steps of a program or automation being planned (e.g. 'sap gui scripting', 'youtube upload', 'pdf invoice extract').

NameTypeReqDescription
limitinteger–Max results (default 10)
only_free_to_tryboolean–Only remote MCP servers that worked without an API key
only_liveboolean–Only remote MCP servers that answered our latest daily check (including ones that answer with a sign-in/OAuth request)
only_officialboolean–Deprecated alias of only_verified
only_verifiedboolean–Only verified publishers (domain-verified registry namespace, Anthropic marketplace). Does not mean made by the product's vendor; see the first_party badge
querystringyesKeywords (product names and actions work best)
typestring–Only this kind of tool

No output schema declared.

No examples provided.

Install

How do I install the KitScout MCP server?

KitScout is a hosted endpoint at https://mcp.kitscout.dev/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 · mcp.kitscout.dev

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

What is the KitScout MCP server?

KitScout is an MCP server listed in the public MCP registry as dev.kitscout/kitscout. Check MCP servers, skills and plugins before installing: maker, upkeep, live status. 90k tools. This page covers its hosted endpoint (https://mcp.kitscout.dev/mcp).

Is the KitScout MCP server safe to use?

KitScout scores 72 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 KitScout MCP server expose?

KitScout exposes 4 tools: search_tools, get_tool, check_tools, list_categories. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.

Does the KitScout MCP server require authentication?

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

Is the KitScout MCP server still maintained?

KitScout is still listed as active in the MCP registry. We last reached this channel on 21 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 KitScout MCP server?

VerifyMCP ran 13 checks on KitScout, 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.