_ registry / mcp streamable-http · checked 31m ago

agundur-mcp

https://www.agundur.de

Registry code: dbd4c0afc4803fe0

api record

Checks whether a website is readable and citable by AI systems (ChatGPT, Claude, Perplexity, etc.)

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

endpoint
https://www.agundur.de/mcp.php
protocol
streamable-http ·2024-11-05
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 agundur-mcp live?
Yes — it answered the hub's last check (checked 31m ago). It answered 100% of checks over the last 30 days.
Is agundur-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does agundur-mcp have?
2 tools: geo_scan, local_business_check.
Is agundur-mcp 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.3%· all time 99.3%

latency
94ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 293 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • check if a site is citable by ai assistants
  • check local business schema markup
takes → gives
text → data
tools
2 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

_ what it can do 2 tools
1 open 1 never probed 1 of 2 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.

  • local_business_check reads open 3h ago

    Checks a website for LocalBusiness Schema.org markup: required fields for Google Rich Results (name, image, address), recommended fields (telephone, opening hours, price range, geo coordinates, ratings), and type-correctness of nested properties (e.g. address must be a PostalAddress). Use whenever someone asks to check, audit, or improve a local business website's structured data / Rich Results eligibility.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full URL of the business website to check, including https://"
    }
  }
}
    arguments 12 lines
  • geo_scan reads unknown never probed

    Checks whether a website is readable and citable by AI systems (ChatGPT, Claude, Perplexity, Google AI Overviews). Returns a 0-100 score across checks like llms.txt, Schema.org structured data, AI bots in robots.txt, content freshness, and heading structure — each with a concrete fix. Use whenever someone asks to check, audit, or improve a website's AI/GEO visibility.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "description": "Full URL of the website to check, including https://"
    }
  }
}
    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 dbd4c0afc4803fe0.

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

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.