Kashif
REMOTE · KASHIF.BOTTLETECH.NET · SCANNED AUG 17
Scores a website's online presence 0-100 and lists the top issues to fix. English/Arabic.
Available components
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 →
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Management7
- Stability observed for 2 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · kashif.bottletech.net
claude mcp add --transport http net-bottletech-kashif-audit https://kashif.bottletech.net/mcp
[mcp_servers.net-bottletech-kashif-audit] url = "https://kashif.bottletech.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-bottletech-kashif-audit": {
"type": "remote",
"url": "https://kashif.bottletech.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-bottletech-kashif-audit --url https://kashif.bottletech.net/mcp --transport streamable-http
mcp_servers:
net-bottletech-kashif-audit:
url: "https://kashif.bottletech.net/mcp" {
"mcpServers": {
"net-bottletech-kashif-audit": {
"type": "http",
"url": "https://kashif.bottletech.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Aug 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 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Aug 26 69
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 17 Aug 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=YR1,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | RSA 4096 | SHA256-RSA | 5d33f6981e5f3fc625f6cbb17666142b6b4 |
| SANs: kashif.bottletech.net | ||||||
| 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 |
DNSSEC insecure
Validation of kashif.bottletech.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| bottletech.net. | absent | 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 |
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.
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.