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.

jwatte.com website tools

REMOTE · JWATTE.COM

Website tool catalog, browser run links, article search and book catalog details from jwatte.com.

Available components

+3 this week 80 Trust /100

Last scanned (13 hours ago)

Scores higher than 77% of remote servers

Reachable. Last reached 21 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 Security80
  • 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability87
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 889 tokens (~148/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management33
  • Stability check failed: schema churn in the 15 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.

  • 8 Nov 26 0
    • Stability: 0.03 → fail ▼ security
    • Tool “audit_url” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “find_tool” rewrote its description, which is the text the model reads security
    • Tool “list_audit_tools” rewrote its description, which is the text the model reads security
    • Tool “search_blog” rewrote its description, which is the text the model reads security
    • Schema quality: 188 → 148 ▲ functional
    • Server version: 1.0.5 → 1.1.0 functional
    • New tool “get_audit_link” functional
    • “list_audit_tools” reworded the description of “category” cosmetic
    • “list_audit_tools” reworded the description of “offset” cosmetic
    • Tool “find_tool” changed its title: Find the right tool → Find matching website tools cosmetic
    • Tool “list_audit_tools” changed its title: List the free tools → List website tools cosmetic
  • 7 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “audit_url” rewrote its description, which is the text the model reads security
    • Tool “get_book_info” rewrote its description, which is the text the model reads security
    • Tool “list_audit_tools” rewrote its description, which is the text the model reads security
    • Tool “recommend_book” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.1 → 1.0.5 functional
    • “list_audit_tools” reworded the description of “limit” cosmetic
  • 6 Nov 26 75

    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://jwatte.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jwatte.com CN=YE2,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA384 6b76b5491aa905a76e6bbaf9de70b4f8fd9
SANs: *.jwatte.com, jwatte.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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 jwatte.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
jwatte.com. 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
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jwatte.com/mcp Verified 200
http (plaintext) http://jwatte.com/mcp HTTPS enforced 301 https://jwatte.com/mcp
MCP tools · 6 exposed · ~747 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
find_tool ~112

Matches a website-checking or creation need against the jwatte.com catalog using weighted words, related terms and phrase matches. Returns up to 10 matching tools with titles, descriptions, source links and takes_url flags indicating support for browser run links.

NameTypeReqDescription
categorystring–Optional: only audits, generators or utilities.
limitinteger–How many tools at most (1 to 10, default 5).
needstringyesWhat the person wants to check or build, in their words.
NameTypeReqDescription
directorystringyes–
needstringyes–
resultsarrayyes–
{"need":"check my website for accessibility problems"}
get_audit_link ~141

Creates a browser run link for a catalog tool that supports website addresses. Opening the link fills in the address and starts that tool, which may fetch the target through the site hosting function and configured proxies. The MCP call itself never fetches or audits the target and returns no audit findings. Accepts public HTTP or HTTPS addresses only; rejects private addresses, internal names, credentials and non-standard ports.

NameTypeReqDescription
toolstringyesTool slug, e.g. "mega-analyzer", "wcag-accessibility-audit", "agent-ready-audit".
urlstringyesThe public page or site to audit. A bare host name uses HTTPS.
NameTypeReqDescription
autorunbooleanyes–
fetched_by_serverbooleanyes–
notestringyes–
run_urlstringyes–
targetstringyes–
toolobjectyes–
{"tool":"mega-analyzer","url":"https://example.com"}
get_book_info ~147

Catalog details for one of J.A. Watte's six books by slug: title, subtitle, page count, format, listed price, a short factual summary, Amazon link and companion website. Slugs: w2trap, condotrap, resaletrap, 97launch, 20agency, 100network. Prices are catalog values, not a live retailer lookup.

NameTypeReqDescription
slugstringyesw2trap (The W-2 Trap), condotrap (The Condo Trap), resaletrap (The Resale Trap), 97launch (The $97 Launch), 20agency (The $20 Dollar Agency), 100network (The $100 Network).
NameTypeReqDescription
bookobjectyes–
books_pagestringyes–
{"slug":"97launch"}
list_audit_tools ~170

Returns a page from the jwatte.com website-tool catalog in directory order, filtered by category or matching keywords. Each entry has a slug, title, category, description, source link and takes_url flag indicating whether it supports a browser run link. Includes the total count and next offset; 1 to 20 entries per page.

NameTypeReqDescription
categorystring–Optional category: audits, generators or utilities; absent means all categories.
limitinteger–Tools per page (1 to 20, default 10). More results are available using next_offset.
offsetinteger–Number of entries before this page, matching the previous next_offset value.
searchstring–Keywords that must all appear in the title, slug, tags or description, e.g. "schema".
NameTypeReqDescription
categorystring|nullyes–
countintegeryes–
directorystringyes–
next_offsetinteger|nullyes–
offsetintegeryes–
searchstring|nullyes–
toolsarrayyes–
totalintegeryes–
{"category":"audits","limit":10}
recommend_book ~92

Matches a reading topic against subject phrases and related-word rules for J.A. Watte's six-book catalog. A match returns a title, a topic-based reason, and links. Only a clearly matched subject receives a book. An unmatched topic returns no book and no Amazon link. This searches only the publisher's own catalog.

NameTypeReqDescription
topicstringyesThe reader's situation, goal or topic, in their words.
NameTypeReqDescription
books_pagestringyes–
matchedbooleanyes–
primary–yes–
reasonstringyes–
rulestring|nullyes–
secondary–yes–
topicstringyes–
{"topic":"books about website building"}
search_blog ~85

Searches the jwatte.com article catalog by keyword and returns up to 25 matches ranked by relevance, each with a title, publication date, source link and summary.

NameTypeReqDescription
limitinteger–How many articles at most (1 to 25, default 10).
querystringyesKeywords, e.g. "llms.txt" or "condo special assessment".
NameTypeReqDescription
blogstringyes–
countintegeryes–
querystringyes–
resultsarrayyes–
total_matchesintegeryes–
{"limit":5,"query":"llms.txt"}
Install

How do I install the jwatte.com website tools MCP server?

jwatte.com website tools is a hosted endpoint at https://jwatte.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 · jwatte.com

# add to Claude Code
claude mcp add --transport http com-jwatte-site 'https://jwatte.com/mcp'
Common questions

What is the jwatte.com website tools MCP server?

jwatte.com website tools is an MCP server listed in the public MCP registry as com.jwatte/site. Website tool catalog, browser run links, article search and book catalog details from jwatte.com. This page covers its hosted endpoint (https://jwatte.com/mcp).

Is the jwatte.com website tools MCP server safe to use?

jwatte.com website tools scores 80 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 jwatte.com website tools MCP server expose?

jwatte.com website tools exposes 6 tools: list_audit_tools, find_tool, get_audit_link, search_blog, get_book_info, recommend_book. Their descriptions and schemas cost roughly 747 tokens of context every time the server is loaded.

Does the jwatte.com website tools MCP server require authentication?

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

Is the jwatte.com website tools MCP server still maintained?

jwatte.com website tools 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 jwatte.com website tools MCP server?

VerifyMCP ran 13 checks on jwatte.com website tools, 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.