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

webtoolshub

https://webtoolshub-blond.vercel.app

Registry code: 4b5809a1c771c93b

api record
endpoint
https://webtoolshub-blond.vercel.app/api/mcp
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 webtoolshub live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is webtoolshub free to use?
Yes — the hub reached it with no key and no payment.
What tools does webtoolshub have?
13 tools: check_domains_bulk, dns_lookup, trace_redirects, portfolio_expiry, idn_homograph, check_domain, ssl_check, whois_lookup, ….
Is webtoolshub 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 100%· all time 100%

latency
213ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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
1

through this hub

calls served
1

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 13 tools
13 never probed 0 of 13 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.

  • check_domains_bulk unknown 2h ago

    Check many names at once across the given TLDs. Returns availability for every name and TLD combination. Ideal for comparing brand name options. .com and .in are prioritised.

    mcp-tool

    {
      "type": "object",
      "required": [
        "names"
      ],
      "properties": {
        "tlds": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional TLD list. Defaults to ['com','in'] for bulk checks."
        },
        "names": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "List of base names without dots."
        }
      }
    }
    arguments 22 lines
  • dns_lookup unknown 2h ago

    Look up DNS records for a domain over DNS-over-HTTPS: A, AAAA, CNAME, MX, NS, TXT, SOA and CAA. Use this to find a domain's IP addresses, mail servers (MX), nameservers, TXT records (SPF, DKIM, verification), or CAA policy. Returns records grouped by type with TTLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "types": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional record types, e.g. ['A','MX','TXT']. Omit for all common types."
        },
        "domain": {
          "type": "string",
          "description": "Domain to resolve, e.g. 'github.com'."
        }
      }
    }
    arguments 19 lines
  • trace_redirects unknown never probed

    Trace a URL's HTTP redirect chain hop by hop and report each status code and Location until the final destination. Use for SEO audits, link checking, or debugging redirect loops.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target"
      ],
      "properties": {
        "target": {
          "type": "string",
          "description": "URL or hostname to start from."
        }
      }
    }
    arguments 12 lines
  • portfolio_expiry unknown never probed

    Check expiry for a list of domains at once and return each one's expiry date and days remaining, sorted soonest-first, with a summary. Use to monitor a domain portfolio for renewals.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domains"
      ],
      "properties": {
        "domains": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "List of domains to check."
        }
      }
    }
    arguments 15 lines
  • idn_homograph unknown never probed

    Convert a domain to/from punycode (xn--) and detect homograph / lookalike risk: mixed scripts and confusable characters that make a domain impersonate a brand. Use to spot phishing / spoofed domains. No network needed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain to analyze (Unicode or punycode)."
        }
      }
    }
    arguments 12 lines
  • check_domain unknown 2h ago

    Check whether a single domain name is available to register across one or more TLDs. Uses authoritative RDAP data with DNS cross-check. Returns each domain as available, taken, or unknown. .com and .in are prioritised and listed first.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Base name without a dot, e.g. 'mycoolsite'."
        },
        "tlds": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Optional TLD list, e.g. ['com','in','io']. Omit for the default ~20 common TLDs."
        }
      }
    }
    arguments 19 lines
  • ssl_check unknown never probed

    Inspect a website's SSL/TLS certificate. Connects to the host on port 443 and returns the issuer, common name, Subject Alternative Names, validity window, days remaining until expiry, the negotiated TLS version and cipher, and whether the certificate is currently valid for the host. Use this to check when a certificate expires or whether HTTPS is set up correctly.

    mcp-tool

    {
      "type": "object",
      "required": [
        "host"
      ],
      "properties": {
        "host": {
          "type": "string",
          "description": "Hostname to check, e.g. 'github.com'."
        },
        "port": {
          "type": "integer",
          "description": "Optional port. Defaults to 443."
        }
      }
    }
    arguments 16 lines
  • whois_lookup unknown never probed

    Look up the full WHOIS registration record for a domain via RDAP: registrar (name, IANA id, abuse contact), creation / update / expiry dates, EPP status codes with plain-English meanings, nameservers, DNSSEC signing state, registry domain ID, and any contact fields the registry still publishes (most are GDPR redacted). Use this to find who a domain is registered with, when it expires, or whether it is locked. For a bare name with no dot, '.com' is assumed.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Full domain including TLD, e.g. 'github.com'. A bare name assumes .com."
        },
        "include_raw": {
          "type": "boolean",
          "description": "Also include the raw registrar WHOIS text (port-43). Default false; unavailable on some hosts."
        }
      }
    }
    arguments 16 lines
  • email_auth unknown never probed

    Analyze a domain's email authentication: SPF, DMARC, DKIM (optional selector) and MX records. Returns each record parsed, a letter grade, and a list of issues such as a missing DMARC policy or a weak SPF 'all' qualifier. Use to check whether a domain can be spoofed or why its email fails delivery.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain to analyze, e.g. 'example.com'."
        },
        "dkim_selector": {
          "type": "string",
          "description": "Optional DKIM selector, e.g. 'google' or 'default'."
        }
      }
    }
    arguments 16 lines
  • who_hosts unknown never probed

    Find who hosts a domain. Resolves its IP addresses and looks each up in RDAP to reveal the hosting network, organization, ASN region and country, plus reverse DNS. Answers 'where is this site hosted / who runs it'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Domain, e.g. 'github.com'."
        }
      }
    }
    arguments 12 lines
  • dns_propagation unknown never probed

    Check DNS propagation for a record across several independent public resolvers (Google, Cloudflare, AdGuard, Quad9) at once and report whether they agree. Use after changing a DNS record to see if it has propagated everywhere.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "type": {
          "type": "string",
          "description": "Record type (A, AAAA, MX, NS, TXT, ...). Default A."
        },
        "domain": {
          "type": "string",
          "description": "Domain to check, e.g. 'github.com'."
        }
      }
    }
    arguments 16 lines
  • find_subdomains unknown never probed

    Enumerate a domain's subdomains from public Certificate Transparency logs (crt.sh). Passive, no scanning. Use for recon, asset inventory, or finding forgotten subdomains.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "description": "Root domain, e.g. 'example.com'."
        }
      }
    }
    arguments 12 lines
  • security_headers unknown never probed

    Fetch a URL and grade its HTTP security headers (HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy), flag information-leaking headers, and return a letter grade with fixes.

    mcp-tool

    {
      "type": "object",
      "required": [
        "target"
      ],
      "properties": {
        "target": {
          "type": "string",
          "description": "URL or hostname, e.g. 'example.com' or 'https://example.com/'."
        }
      }
    }
    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 4b5809a1c771c93b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4b5809a1c771c93b/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/4b5809a1c771c93b/badge.svg)](https://brick.blue/agent/4b5809a1c771c93b?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
1
ok
1
failed
0
success rate
100%
median latency
614ms
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
—

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.