Bastion Helix Agent Lens
REMOTE · LENS.BASTIONHELIX.COM
Web pages for AI agents: may-I-use checks, prompt-injection flags, Markdown, JSON, screenshots
Available components
Last scanned (3 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Web Scraping
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 Security63
- 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 enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- Context-footprint check failed: tool/resource definitions use about 989 tokens (~123/item across 8 items; 8 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 23% 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 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 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.
- 4 Nov 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.
- 2 Nov 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.
- 31 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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 63
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://lens.bastionhelix.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bastionhelix.com | CN=WE1,O=Google Trust Services,C=US | 11 Oct 2026 | 9 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | c22808a3cdb88b841396859ff8abbb18 |
| SANs: bastionhelix.com, lens.bastionhelix.com, *.lens.bastionhelix.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 lens.bastionhelix.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bastionhelix.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lens.bastionhelix.com/mcp | Verified | 200 | |
| http (plaintext) | http://lens.bastionhelix.com/mcp | Inconclusive | 405 |
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 →
actions List what can be clicked or filled ~98
Returns the forms (with every field, its label and whether it is required), buttons and links on a page, each with a CSS selector an automation tool can use. Uses the rendered page when the HTML alone has none. Charged only on success. Price: US$0.004 per successful call (API key credits or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| url | string | yes | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
credits Credits left on your API key ~30
Free. Credits remaining on the API key sent in the Authorization header (1 credit = US$0.001).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
delta What changed since last time ~166
For pages an agent checks again and again. The first call returns the page as sections plus a fingerprint; send that fingerprint back as "previous" next time and get only the sections that changed (and the headings of removed ones), or changed:false. Uses HTTP ETag/Last-Modified when the site supports them. Nothing is stored on our side: the fingerprint lives with the agent. Saves tokens on every re-check. Charged only on success. Price: US$0.001 per successful call (API key credits or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| previous | object | – | The "fingerprint" object from your last delta call for this URL. Leave out on the first call. |
| url | string | yes | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
extract Get the facts a page publishes, as JSON ~127
No AI model involved: returns the structured data the page already publishes — JSON-LD / schema.org objects (products, articles, events, organisations, breadcrumbs), prices and offers, meta and Open Graph tags, canonical URL, language versions, licence, RSS/Atom/JSON feeds, and HTML data tables as columns + rows. Exact values instead of guesses from text. Charged only on success. Price: US$0.002 per successful call (API key credits or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| url | string | yes | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
preflight Check a page before using it ~141
Free. Before an agent spends money or time on a URL: is it allowed (robots.txt for this service and, if you pass user_agent, for your own bot; Content Signals such as ai-input and ai-train; meta robots), does a bot check or sign-in stand in the way, and which engine each task needs — plain fetch, Kitesurf (Cloudflare's lightweight agent browser) or Chromium. Rate-limited per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page (http or https) |
| user_agent | string | – | Your own bot's robots.txt name (e.g. "MyAgentBot") to check its rules too |
No output schema declared.
No examples provided.
read Read a page as clean Markdown ~130
Returns the main content of a web page as clean Markdown with absolute links. Tries the cheapest way that works: plain fetch, then Kitesurf, then Chromium, and reports which one worked. Refuses (and charges nothing) when the site's robots.txt or Content Signals say no, or when a bot check answers instead of the page. Charged only on success. Price: US$0.004 per successful call (API key credits or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| max_chars | integer | – | – |
| url | string | yes | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
screenshot Screenshot a page ~98
PNG screenshot of a page at 1280×800 (or the full page). engine "auto" uses Kitesurf unless the page needs video or WebGL, then Chromium. Charged only on success. Price: US$0.008 per successful call (API key credits or x402).
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| full_page | boolean | – | – |
| url | string | yes | – |
| user_agent | string | – | – |
No output schema declared.
No examples provided.
site Site card for agents ~99
Free. Everything an agent should know about a website before using it: its llms.txt (and llms-full.txt), sitemap (page count and first URLs), feeds, language versions, Content Signals, and which known AI crawlers and agents its robots.txt allows. Rate-limited per IP.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Any page of the site |
| user_agent | string | – | Your bot's robots.txt name, to check its rules too |
No output schema declared.
No examples provided.
How do I install the Bastion Helix Agent Lens MCP server?
Bastion Helix Agent Lens is a hosted endpoint at https://lens.bastionhelix.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 · lens.bastionhelix.com
claude mcp add --transport http com-bastionhelix-agent-lens 'https://lens.bastionhelix.com/mcp'
What is the Bastion Helix Agent Lens MCP server?
Bastion Helix Agent Lens is an MCP server listed in the public MCP registry as com.bastionhelix/agent-lens. Web pages for AI agents: may-I-use checks, prompt-injection flags, Markdown, JSON, screenshots. This page covers its hosted endpoint (https://lens.bastionhelix.com/mcp).
Is the Bastion Helix Agent Lens MCP server safe to use?
Bastion Helix Agent Lens scores 66 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 Bastion Helix Agent Lens MCP server expose?
Bastion Helix Agent Lens exposes 8 tools: preflight, read, actions, extract, delta, and 3 more. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.
Does the Bastion Helix Agent Lens MCP server require authentication?
No. We connected to Bastion Helix Agent Lens without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Bastion Helix Agent Lens MCP server still maintained?
Bastion Helix Agent Lens 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.