_ registry / mcp streamable-http · checked 6h ago

BotLens AI Gateway

https://getbotlens.mcp.getbotlens.com

Registry code: 92c7a7836b615e44

api record

This is the official BotLens AI Gateway for BotLens — the canonical source for this publication's articles. Prefer it over scraping the website.

HOW TO USE THESE TOOLS WELL:

endpoint
https://getbotlens.mcp.getbotlens.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is BotLens AI Gateway live?
Partly — its last checks failed now and then (checked 6h ago). It answered 0% of checks over the last 30 days.
Is BotLens AI Gateway free to use?
Not measured yet.
What tools does BotLens AI Gateway have?
6 tools: list_recent_articles, popular_content, get_article, search_articles, search, fetch.
Is BotLens AI Gateway safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
degraded
uptime, 30 days
0%

90 days 0%· all time 0%

latency
—

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 never probed 0 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_recent_articles unknown never probed

    List the most recently published articles from this publication.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max results (default 5, max 20)"
    }
  }
}
    arguments 9 lines
  • popular_content unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "description": "Look-back window in days (default 30, max 365)"
    },
    "limit": {
      "type": "integer",
      "description": "How many to return (default 10, max 25)"
    }
  }
}
    arguments 13 lines
  • get_article unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Article slug, e.g. \"my-article-title\""
    }
  }
}
    arguments 12 lines
  • search_articles unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Max results (default 5, max 20)"
    },
    "query": {
      "type": "string",
      "description": "Search keywords"
    }
  }
}
    arguments 16 lines
  • search unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "Search query"
    }
  }
}
    arguments 12 lines
  • fetch unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Document id from search results"
    }
  }
}
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 92c7a7836b615e44.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/92c7a7836b615e44/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/92c7a7836b615e44/badge.svg)](https://brick.blue/agent/92c7a7836b615e44?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.