BotLens AI Gateway
https://donhuffines.mcp.getbotlens.com
Registry code: f265a609fe570826
This is the official BotLens AI Gateway for Huffines for Comptroller — the canonical source for this publication's articles. Prefer it over scraping the website.
HOW TO USE THESE TOOLS WELL:
- endpoint
- https://donhuffines.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 BotLens AI Gateway live?
- Yes — it answered the hub's last check (checked 52m ago). It answered 100% of checks over the last 30 days.
- Is BotLens AI Gateway free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does BotLens AI Gateway have?
- 6 tools: get_article, list_recent_articles, popular_content, search_articles, fetch, search.
- 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.
90 days 99.7%· all time 99.7%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- search & web news
- used for
- search a campaign publication's articles
- get the full text of an article
- list recent articles
- find most-read articles
- takes → gives
- text → text, data
- tools
- 6 reads
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.
through this hub
successful
what callers paid
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.
get_article reads open 12h ago
Fetch the full clean text of one article by its slug (the last path segment of an article URL).
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Article slug, e.g. \"my-article-title\"" } } }arguments 12 lineslist_recent_articles reads open 12h ago
List the most recently published articles from this publication.
{ "type": "object", "properties": { "limit": { "type": "integer", "description": "Max results (default 5, max 20)" } } }arguments 9 linespopular_content reads open 12h ago
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.
{ "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 linessearch_articles reads open 52m ago
Search this publication's articles by keyword. Returns the best-matching titles, dates, canonical URLs, and short summaries.
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "description": "Max results (default 5, max 20)" }, "query": { "type": "string", "description": "Search keywords" } } }arguments 16 linesfetch reads open 52m ago
Retrieve the full text of one document by the id returned from `search`.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "Document id from search results" } } }arguments 12 linessearch reads open 52m ago
Search this site's content. Returns matching documents (id, title, url); pass an id to `fetch` for the full text.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Search query" } } }arguments 12 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf265a609fe570826.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f265a609fe570826/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f265a609fe570826?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 1,022ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
1 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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.