Kashif
REMOTE · KASHIF.BOTTLETECH.NET
Scores a website's online presence 0-100 and lists the top issues to fix. English/Arabic.
Available components
Last scanned (6 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 330 tokens (~330/item across 1 items; 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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 →
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://kashif.bottletech.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kashif.bottletech.net | CN=YR2,O=Let's Encrypt,C=US | 30 Sept 2026 | 29 Dec 2026 | RSA 4096 | SHA256-RSA | 66a2fae89bd8936d1195763d83ec207dcdd |
| SANs: kashif.bottletech.net | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 kashif.bottletech.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| bottletech.net. | 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://kashif.bottletech.net/mcp | Verified | 200 | |
| http (plaintext) | http://kashif.bottletech.net/mcp | HTTPS enforced | 301 | https://kashif.bottletech.net/mcp |
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 →
scan_website Score a business’s online presence ~269
Score how well a business shows up online, out of 100, and name what is hurting it most. Give it a website (and an email to send the full report to) and it runs Kashif's audit of the business's online presence: whether customers can find them in search, whether AI assistants can read and recommend them, how fast the site feels on a phone and the first impression it makes, how trustworthy it looks, and how easy the business is to reach (WhatsApp, phone, a contact form). Returns a 0-100 score with the top issues to fix first. Use it whenever someone asks to audit, check, review, grade or improve a company's website or online presence. This starts a live scan and creates a lead for the Kashif team, who follow up with the full written report by email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | An email address to send the full written report to. Required — this is a lead for the team. | |
| language | string | – | Report language: "en" (default) or "ar" for Arabic. |
| name | string | – | Optional: the person or business name, used to label the lead. |
| url | string | yes | The business’s website, e.g. example.com or https://example.com. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | The top issues to fix first, most urgent first. |
| note | string | yes | Plain-language context about the score and the full report to come. |
| score | – | yes | 0-100 online-presence score, or null until the quick pass finishes. |
| status | string | yes | "ready" = quick score below; "processing" = still running, report follows; "failed" = site could not be checked. |
| website | string | yes | The website that was scanned. |
| string | yes | A WhatsApp link to reach the Kashif team about this business. |
No examples provided.
How do I install the Kashif MCP server?
Kashif is a hosted endpoint at https://kashif.bottletech.net/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 · kashif.bottletech.net
claude mcp add --transport http net-bottletech-kashif-audit 'https://kashif.bottletech.net/mcp'
What is the Kashif MCP server?
Kashif is an MCP server listed in the public MCP registry as net.bottletech.kashif/audit. Scores a website's online presence 0-100 and lists the top issues to fix. English/Arabic. This page covers its hosted endpoint (https://kashif.bottletech.net/mcp).
Is the Kashif MCP server safe to use?
Kashif scores 84 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 Kashif MCP server expose?
Kashif exposes 1 tool: scan_website. Their descriptions and schemas cost roughly 269 tokens of context every time the server is loaded.
Does the Kashif MCP server require authentication?
No. We connected to Kashif without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kashif MCP server still maintained?
Kashif is still listed as active in the MCP registry. We last reached this channel on 5 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 Kashif MCP server?
VerifyMCP ran 13 checks on Kashif, 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.