Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BotLens AI Gateway

REMOTE · GETBOTLENS.MCP.GETBOTLENS.COM · SCANNED SEP 21

MCP gateway for getbotlens.com: articles, search and full text. Read-only, no auth.

+3 this week 84 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 474 tokens (~79/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
Install

How do I install the BotLens AI Gateway MCP server?

BotLens AI Gateway is a hosted endpoint at https://getbotlens.mcp.getbotlens.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 · getbotlens.mcp.getbotlens.com

# add to Claude Code
claude mcp add --transport http com-getbotlens-getbotlens 'https://getbotlens.mcp.getbotlens.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-getbotlens-getbotlens": {
      "url": "https://getbotlens.mcp.getbotlens.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-getbotlens-getbotlens": {
      "type": "http",
      "url": "https://getbotlens.mcp.getbotlens.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-getbotlens-getbotlens]
url = "https://getbotlens.mcp.getbotlens.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getbotlens-getbotlens": {
      "type": "remote",
      "url": "https://getbotlens.mcp.getbotlens.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-getbotlens-getbotlens --url 'https://getbotlens.mcp.getbotlens.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-getbotlens-getbotlens:
    url: "https://getbotlens.mcp.getbotlens.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-getbotlens-getbotlens": {
      "Transport": "http",
      "Url": "https://getbotlens.mcp.getbotlens.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-getbotlens-getbotlens -t streamable-http -u 'https://getbotlens.mcp.getbotlens.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-getbotlens-getbotlens": {
      "type": "http",
      "url": "https://getbotlens.mcp.getbotlens.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1
    • Schema quality: good → excellent functional
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Sept 2026 · Probed https://getbotlens.mcp.getbotlens.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.mcp.getbotlens.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 15 Jun 2026 29 Dec 2026 RSA 2048 SHA256-RSA 9234988bb62b35caf0f29cf29f3c926
SANs: *.mcp.getbotlens.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of getbotlens.mcp.getbotlens.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
getbotlens.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://getbotlens.mcp.getbotlens.com/mcp Verified 200
http (plaintext) http://getbotlens.mcp.getbotlens.com/mcp HTTPS enforced
MCP tools · 6 exposed · ~306 tokens

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 →

Tool Tokens
fetch ~34

Retrieve the full text of one document by the id returned from `search`.

NameTypeReqDescription
idstringyesDocument id from search results
NameTypeReqDescription
idstringyes
metadataobject
textstringyes
titlestringyes
urlstringyes

No examples provided.

get_article ~47

Fetch the full clean text of one article by its slug (the last path segment of an article URL).

NameTypeReqDescription
slugstringyesArticle slug, e.g. "my-article-title"
NameTypeReqDescription
datestring|null
slugstringyes
summarystring|null
textstring|null
titlestringyes
urlstringyes

No examples provided.

list_recent_articles ~36

List the most recently published articles from this publication.

NameTypeReqDescription
limitintegerMax results (default 5, max 20)
NameTypeReqDescription
articlesarrayyes
totalinteger|null

No examples provided.

popular_content ~88

The most-read / most-requested articles, ranked by how often AI assistants have actually fetched them. Use for "what is your most popular article", "top reads", or to recommend what to read.

NameTypeReqDescription
daysintegerLook-back window in days (default 30, max 365)
limitintegerHow many to return (default 10, max 25)
NameTypeReqDescription
articlesarrayyes

No examples provided.

search ~43

Search this site's content. Returns matching documents (id, title, url); pass an id to `fetch` for the full text.

NameTypeReqDescription
querystringyesSearch query
NameTypeReqDescription
resultsarrayyes

No examples provided.

search_articles ~58

Search this publication's articles by keyword. Returns the best-matching titles, dates, canonical URLs, and short summaries.

NameTypeReqDescription
limitintegerMax results (default 5, max 20)
querystringyesSearch keywords
NameTypeReqDescription
articlesarrayyes
totalinteger|null

No examples provided.

Common questions

What is the BotLens AI Gateway MCP server?

BotLens AI Gateway is an MCP server listed in the public MCP registry as com.getbotlens/getbotlens. MCP gateway for getbotlens.com: articles, search and full text. Read-only, no auth. This page covers its hosted endpoint (https://getbotlens.mcp.getbotlens.com/mcp).

Is the BotLens AI Gateway MCP server safe to use?

BotLens AI Gateway scores 84 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 BotLens AI Gateway MCP server expose?

BotLens AI Gateway exposes 6 tools: search_articles, list_recent_articles, get_article, popular_content, search, fetch. Their descriptions and schemas cost roughly 306 tokens of context every time the server is loaded.

Does the BotLens AI Gateway MCP server require authentication?

No. We connected to BotLens AI Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BotLens AI Gateway MCP server still maintained?

BotLens AI Gateway is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.