_ registry / mcp streamable-http · checked just now

top-gun-geo-lens

https://top-gun-mcp-server.vercel.app

Registry code: 54016f1dacd4ad2f

api record

Brand visibility auditing across LLMs, AI search, and answer engines with GEO reports and scores.

from a public catalogue that lists it, not from the operator

endpoint
https://top-gun-mcp-server.vercel.app/api/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 top-gun-geo-lens live?
Yes — it answered the hub's last check (checked just now). It answered 100% of checks over the last 30 days.
Is top-gun-geo-lens free to use?
Yes — the hub reached it with no key and no payment.
What tools does top-gun-geo-lens have?
3 tools: geo_quick_check, audit_brand, get_payment_info.
Is top-gun-geo-lens 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
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
931ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 315 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • audit brand visibility in ai search
  • check brand visibility score
  • get payment info for audits
takes → gives
text → data
tools
3 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • geo_quick_check reads unknown 12h ago

    Quick brand visibility snapshot across LLM-indexed sources. Returns a score (0–100), top 3 citation URLs, and 2 quick improvement tips. Single-source search (5 results). Costs $0.05 USDC. For full citations, LLM index status, and 6 GEO recommendations use audit_brand ($1.50).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Brand name, company, or product to check (e.g. 'Stripe', 'Notion', 'Acme')"
        },
        "paymentToken": {
          "type": "string",
          "description": "Stripe checkout session ID from a completed $0.05 USDC payment. If omitted, the tool returns a payment link."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • audit_brand reads unknown never probed

    Full brand visibility audit across LLM-indexed sources (Brave + Exa, 10 results). Returns a visibility score (0–100), score label, top 5 citation URLs, LLM index status, and 6 actionable GEO recommendations. Costs $1.50 USDC. For a quick snapshot at $0.05 use geo_quick_check.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Brand name, company, or product to audit (e.g. 'Anthropic', 'Linear', 'Vercel')"
        },
        "paymentToken": {
          "type": "string",
          "description": "Stripe checkout session ID from a completed $1.50 USDC payment. If omitted, the tool returns a payment link instead of audit results."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_payment_info reads unknown never probed

    Get payment URLs and USDC wallet address for both audit tiers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 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 54016f1dacd4ad2f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/54016f1dacd4ad2f/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/54016f1dacd4ad2f/badge.svg)](https://brick.blue/agent/54016f1dacd4ad2f?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
70%

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.