Searchwire
REMOTE · SEARCHWIRE.DEV
SEO data for AI agents: keyword volume, Google results, App Store keywords, domain and name checks.
Available components
Last scanned (3 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 23 Oct 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. 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 Usability67
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1220 tokens (~122/item across 10 items; 10 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +4
- HTTPS: unverified → pass ▲ security
- 15 Oct 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.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 65
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 23 Oct 2026 · Probed https://searchwire.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=searchwire.dev | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5a35d256ace67ce0e59434d87dfbd21 |
| SANs: searchwire.dev, www.searchwire.dev, *.www.searchwire.dev | ||||||
| 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 searchwire.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| searchwire.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://searchwire.dev/mcp | Verified | 200 | |
| http (plaintext) | http://searchwire.dev/mcp | HTTPS enforced | 301 | https://searchwire.dev/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 →
account Balance and spend ~30
The key's balance, daily budget and today's (UTC) spend, cache hits and misses. Needs a key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
app_competitors Apps competing for the same keywords ~132
The apps that rank for the same store keywords as an app, most shared keywords first, with shared keyword count, average rank and volume (United States, English). $0.02 a call plus $0.002 a competitor.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The number in an App Store link (e.g. "964220645"), or with store "google" the package name (e.g. "org.telegram.messenger"). |
| limit | integer | – | Default 20. |
| store | string | – | "apple" (App Store, default) or "google" (Google Play). |
No output schema declared.
No examples provided.
app_keyword_volume App store search volume ~79
Monthly App Store or Google Play search volume for up to 25 keywords of your choosing (United States, English). A first lookup takes up to a minute. $0.02 a keyword answered.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | yes | – |
| store | string | – | "apple" (App Store, default) or "google" (Google Play). |
No output schema declared.
No examples provided.
app_keywords Keywords an app ranks for ~183
The keywords an app ranks for in App Store or Google Play search, each with monthly store search volume and the app's rank (United States, English). $0.02 a call plus $0.0002 a keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | The number in an App Store link (e.g. "964220645"), or with store "google" the package name (e.g. "org.telegram.messenger"). |
| limit | integer | – | Default 100. |
| max_rank | integer | – | Only keywords where the app ranks this high or higher. |
| min_volume | integer | – | – |
| offset | integer | – | – |
| order | string | – | "volume" highest first (default) or "rank" best first. |
| store | string | – | "apple" (App Store, default) or "google" (Google Play). |
No output schema declared.
No examples provided.
app_search App store search results ~168
The apps a store's search returns for a keyword, in order, with rating and reviews. A first lookup takes 5 to 20 seconds; if it answers with an error saying it is not ready, nothing is charged and the same call a minute later returns it. $0.005 a keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code. Default "us". |
| depth | integer | – | Default 10; up to 100 on the App Store, 30 on Google Play. |
| keyword | string | yes | – |
| language | string | – | Two-letter language code; Chinese is "zh-TW" or "zh-CN". Default "en". |
| store | string | – | "apple" (App Store, default) or "google" (Google Play). |
No output schema declared.
No examples provided.
buy_credit Get a key or add credit ~63
Starts a purchase of prepaid credit and returns checkout_url, where a person pays, and claim_url, which returns the key once paid. With a key, the credit is added to that key. Nothing is charged by this call.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_usd | integer | yes | – |
No output schema declared.
No examples provided.
check_domains Domain registration status ~63
Whether up to 50 domain names are registered, from the registries (RDAP and WHOIS); registered ones come with registrar, creation and expiry dates. Free. Not registered does not guarantee the standard price (reserved or premium names).
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | – |
No output schema declared.
No examples provided.
check_name Product name availability ~97
One check of a product or brand name: its domain per TLD, the GitHub account, the npm package, and with a key the name's search volume. Free without the volume.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code. Default "us". |
| name | string | yes | Letters, digits and inner hyphens. |
| tlds | array | – | Default com, dev, ai, io, app, co. |
No output schema declared.
No examples provided.
google_results Google results for a keyword ~145
The organic Google results for a keyword: rank, url, domain and title, with the time they were observed. $0.002 when collected earlier, $0.005 fetched live.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code. Default "us". |
| depth | integer | – | How many results. Default 10. |
| keyword | string | yes | – |
| language | string | – | Two-letter language code; Chinese is "zh-TW" or "zh-CN". Default "en". |
| source | string | – | "index" = results collected earlier, "live" = fetched now, "any" (default) = collected first, live if none. |
No output schema declared.
No examples provided.
keyword_volume Keyword search volume ~111
Monthly Google search volume, CPC, ad competition (0-1, not ranking difficulty) and 12 months of history for up to 1,000 keywords in one country and language. $0.02 a call plus $0.0002 a keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter country code. Default "us". |
| keywords | array | yes | – |
| language | string | – | Two-letter language code; Chinese is "zh-TW" or "zh-CN". Default "en". |
No output schema declared.
No examples provided.
How do I install the Searchwire MCP server?
Searchwire is a hosted endpoint at https://searchwire.dev/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 · searchwire.dev
claude mcp add --transport http lambdalabshq-searchwire 'https://searchwire.dev/mcp'
What is the Searchwire MCP server?
Searchwire is an MCP server listed in the public MCP registry as io.github.LambdaLabsHQ/searchwire. SEO data for AI agents: keyword volume, Google results, App Store keywords, domain and name checks. This page covers its hosted endpoint (https://searchwire.dev/mcp).
Is the Searchwire MCP server safe to use?
Searchwire scores 74 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 Searchwire MCP server expose?
Searchwire exposes 10 tools: keyword_volume, google_results, check_domains, check_name, app_keywords, and 5 more. Their descriptions and schemas cost roughly 1,071 tokens of context every time the server is loaded.
Does the Searchwire MCP server require authentication?
No. We connected to Searchwire without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Searchwire MCP server still maintained?
Searchwire is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.