ShellWire
REMOTE · SHELLWIRE.COM
Discover and compare software, read chatbot news, and submit applications for private review.
Available components
Last scanned (3 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Search and Retrieval
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. 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 Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 841 tokens (~105/item across 8 items; 8 tools + 0 resources), lean.Pass
- 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 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Oct 26 67
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 18 Oct 2026 · Probed https://shellwire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=shellwire.com | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f92f348b216a20df0e6cc61bd6d75bf1 |
| SANs: shellwire.com, *.shellwire.com | ||||||
| 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 shellwire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| shellwire.com. | 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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shellwire.com/mcp | Verified | 200 | |
| http (plaintext) | http://shellwire.com/mcp | HTTPS enforced | 301 | https://shellwire.com/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 →
compare_tools Compare chatbots and tools ~39
Compare one to four distinct public tool IDs. Preserves unknown facts, source evidence and checked dates; no generated ratings.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
fetch Read a public record ~39
Fetch one public record ID returned by search. Includes citable text and dated facts. Unpublished and unknown IDs are unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | yes | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_chatbot_brief Read the chatbot brief ~46
Read the same source-reviewed brief shown on the homepage, with at most four labeled stories and related public tools. An empty brief remains empty.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
get_submission_instructions Read builder submission instructions ~42
Anonymous, credential-free instructions for authenticated private submissions. Includes exact first-party OTP HTTP endpoints, bounded submission fields and binary screenshot uploads. No OAuth authentication is offered.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| authentication | object | yes | – |
| builderWritesEnabled | boolean | yes | – |
| media | object | yes | – |
| submission | object | yes | – |
| workflow | array | yes | – |
No examples provided.
list_my_submissions ~54
Requires a current verified builder token. Return only this builder account's private submission statuses, optional published tool URL and image previews. Empty means no owned records. Never returns another builder's submission, operator notes or contact email.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No examples provided.
search Search ShellWire ~38
Search public applications, chatbot catalog and labeled news. Returns at most 24 stable IDs, titles and canonical citation URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
submit_application ~116
Requires email OTP authentication and a verified root homepage backlink. Submit an app or personal agent for private operator review, with optional images uploaded separately by authenticated HTTP. Email must match the verified account. Does not publish. Repeated pending normalized URLs are acknowledged without overwriting. On outcome_unknown inspect list_my_submissions before retrying.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| details | object | – | – |
| string | – | – | |
| images | array | – | – |
| name | string | yes | – |
| officialUrl | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| reference | string | yes | – |
| status | string | yes | – |
No examples provided.
verify_homepage_backlink ~65
Requires a verified builder Bearer token. Check a visible anchor to https://shellwire.com/ on the root homepage of your public HTTPS site. Authenticated bounded network check, cached for five minutes. No publication. Rate limited.
| Name | Type | Req | Description |
|---|---|---|---|
| officialUrl | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | string | yes | – |
| expiresIn | integer | yes | – |
| homepage | string | yes | – |
| verified | boolean | yes | – |
No examples provided.
How do I install the ShellWire MCP server?
ShellWire is a hosted endpoint at https://shellwire.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 · shellwire.com
claude mcp add --transport http kiragu-maina-shellwire 'https://shellwire.com/mcp'
What is the ShellWire MCP server?
ShellWire is an MCP server listed in the public MCP registry as io.github.Kiragu-Maina/shellwire. Discover and compare software, read chatbot news, and submit applications for private review. This page covers its hosted endpoint (https://shellwire.com/mcp).
Is the ShellWire MCP server safe to use?
ShellWire scores 68 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 ShellWire MCP server expose?
ShellWire exposes 8 tools: search, fetch, compare_tools, get_chatbot_brief, get_submission_instructions, and 3 more. Their descriptions and schemas cost roughly 439 tokens of context every time the server is loaded.
Does the ShellWire MCP server require authentication?
No. We connected to ShellWire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ShellWire MCP server still maintained?
ShellWire is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.