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.

Smarty-Pants AI

REMOTE · SMARTY-PANTS.IO

Agentic cybersecurity tool: URL phishing/malware scanning and more.

Available components

69 Trust /100

Last scanned (22 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

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 Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 380 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 20 Nov 26 +1

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

  • 19 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “get_usage” changed its title: Get Usage cosmetic
    • Tool “scan_url” changed its title: Scan URL cosmetic
    • Tool “scan_urls” changed its title: Scan Multiple URLs cosmetic
  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 61

    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://smarty-pants.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=smarty-pants.io CN=YE1,O=Let's Encrypt,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA384 5c6af9ea075a95b806782655a9b56fb69ba
SANs: smarty-pants.io, www.smarty-pants.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 smarty-pants.io. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
io. DS published 38690 8 Verified
smarty-pants.io. 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://smarty-pants.io/mcp Verified 200
http (plaintext) http://smarty-pants.io/mcp HTTPS enforced 301 https://smarty-pants.io/mcp
MCP tools · 3 exposed · ~210 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_usage ~65

Return this account's monthly usage and remaining plan allowance. Args: year: Four-digit UTC year; defaults to the current year. month: UTC month from 1 to 12; defaults to the current month.

NameTypeReqDescription
month–––
year–––

Structured output declared, but exposes no named fields.

No examples provided.

scan_url ~74

Scan a single URL for phishing or malware risk. Args: url: The URL to scan. temperature: Optional decision threshold from 0.0 to 1.0. Higher is stricter; when omitted the service default is used.

NameTypeReqDescription
temperature–––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

scan_urls ~71

Scan several URLs in one request. Args: urls: The URLs to scan. temperature: Optional decision threshold from 0.0 to 1.0. Higher is stricter; when omitted the service default is used.

NameTypeReqDescription
temperature–––
urlsarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Smarty-Pants AI MCP server?

Smarty-Pants AI is a hosted endpoint at https://smarty-pants.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 · smarty-pants.io

# add to Claude Code
claude mcp add --transport http randallshanephd-smartypantsapi 'https://smarty-pants.io/mcp'
Common questions

What is the Smarty-Pants AI MCP server?

Smarty-Pants AI is an MCP server listed in the public MCP registry as io.github.RandallShanePhD/SmartyPantsAPI. Agentic cybersecurity tool: URL phishing/malware scanning and more. This page covers its hosted endpoint (https://smarty-pants.io/mcp).

Is the Smarty-Pants AI MCP server safe to use?

Smarty-Pants AI scores 69 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 Smarty-Pants AI MCP server expose?

Smarty-Pants AI exposes 3 tools: scan_url, scan_urls, get_usage. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.

Does the Smarty-Pants AI MCP server require authentication?

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

Is the Smarty-Pants AI MCP server still maintained?

Smarty-Pants AI 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 Smarty-Pants AI MCP server?

VerifyMCP ran 13 checks on Smarty-Pants AI, 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.