Skip to content
Bastion Helix logo

Bastion Helix MCP server

Which MCP servers are Bastion Helix's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Bastion Helix

Whose server it is
  • Registry namecom.bastionhelix/agent-lensverified in the MCP registry

The registry name sits under bastionhelix.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools8
  • Server calls itselfbastion-helix-agent-lens
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 96 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: build custom charts and dashboards from Jira issues; track billable hours with timers and timesheets; turn incoming email into Jira issues.
  • Checked on 5 of the 7 days it takes to judge reliability.

Once connected

  • Parameters are untyped or undescribed in 5 of 8 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
  • What an agent can do with it0 of 3 use cases
  • Answeredmeasuring5 of the 7 daily checks it takes to print a share
  • Median first answer70 ms
  • Space in an agent's context≈ 1,189 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsA · 90 of 100
  • Typed results0 of 8 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 5 of 8

What an agent can do with it

  • cannot · build custom charts and dashboards from Jira issues
  • cannot · track billable hours with timers and timesheets
  • cannot · turn incoming email into Jira issues

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-29
  • preflight

    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…

  • read

    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…

  • actions

    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…

  • extract

    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…

  • delta

    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…

  • site

    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…

  • screenshot

    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).

  • credits

    Free. Credits remaining on the API key sent in the Authorization header (1 credit = US$0.001).

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "agent-lens": {
      "type": "http",
      "url": "https://lens.bastionhelix.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http bastionhelix https://lens.bastionhelix.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://lens.bastionhelix.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.