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

setu

https://setu.xyz23110928.workers.dev

Registry code: f05e743ab5c0f614

api record

Deterministic data tools: Indian identifier validation (GSTIN, PAN, TAN, CIN, LLPIN, IFSC, PIN code, UPI ID, vehicle registration), AI-visibility (GEO) audits, AI crawler robots.txt matrices and llms.txt checks. Each tools/call is paid with x402 (USDC); an unpaid call returns the payment requirements as an error result.

endpoint
https://setu.xyz23110928.workers.dev/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 setu live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is setu free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does setu have?
5 tools: india_id_validate_batch, ai_crawler_matrix, geo_audit, india_id_validate, llms_txt_check.
Is setu 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
226ms

last good check

priced tools
5

of 5 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 paid 5 of 5 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.

  • india_id_validate_batch paid never probed

    Batch version of the Indian identifier validator: up to 50 values per call (GSTIN, PAN, TAN, CIN, LLPIN, IFSC, PIN code, UPI ID and vehicle registration numbers), mixed types allowed, one flat price. Returns one decoded result per item plus counts by type and validity. Use it for cleaning vendor lists, invoices or onboarding data. Batches containing Aadhaar-like numbers are rejected without charge. Price: $0.02 per call, paid with x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "items"
      ],
      "properties": {
        "type": {
          "enum": [
            "auto",
            "gstin",
            "pan",
            "tan",
            "cin",
            "llpin",
            "ifsc",
            "pincode",
            "upi",
            "vehicle"
          ],
          "type": "string",
          "description": "Default type for all items. Force a type instead of auto-detection (default auto). Case-insensitive; one of: auto, gstin, pan, tan, cin, llpin, ifsc, pincode, upi, vehicle."
        },
        "items": {
          "type": "array",
          "items": {
            "anyOf": [
              {
                "type": "string",
                "maxLength": 256
              },
              {
                "type": "object",
                "required": [
                  "value"
                ],
                "properties": {
                  "type": {
                    "enum": [
                      "auto",
                      "gstin",
                      "pan",
                      "tan",
                      "cin",
                      "llpin",
                      "ifsc",
                      "pincode",
                      "upi",
                      "vehicle"
                    ],
                    "type": "string"
                  },
                  "value": {
                    "type": "string",
                    "maxLength": 256,
                    "minLength": 1
                  }
                }
              }
            ]
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Identifiers as strings or {\"value\",\"type\"} objects (PIN codes may be JSON numbers). Blank items are skipped; a batch where every item is blank is rejected (400, not charged)."
        }
      },
      "additionalProperties": false
    }
    arguments 67 lines
  • ai_crawler_matrix 0.01 USDC paid 4h ago

    Reads a domain's robots.txt (RFC 9309 matching) and reports, for each known AI crawler and AI agent (OpenAI, Anthropic, Google, Perplexity, Apple, Meta, Amazon, Common Crawl and others), whether it may fetch the site root and up to five extra paths, with the deciding rule and any Content-Signal preferences. Use it to see whether a site is open to AI search but closed to AI training. Price: $0.01 per call, paid with x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "paths": {
          "type": "string",
          "maxLength": 600,
          "description": "Optional comma-separated extra paths to test, e.g. /blog/,/docs/"
        },
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 3,
          "description": "Domain or URL, e.g. example.com"
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • geo_audit 0.02 USDC paid 4h ago

    Audits how visible one web page is to AI search engines and AI assistants: which of the major AI crawlers robots.txt allows or blocks, llms.txt and llms-full.txt presence, sitemap, and on-page signals (title, meta, canonical, structured data, headings, content readable without JavaScript). Returns a 0-100 score, grade and prioritised recommendations. Use it to check or monitor a site for generative-engine optimisation. Price: $0.02 per call, paid with x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "maxLength": 2048,
          "minLength": 3,
          "description": "Page URL or bare domain to audit, e.g. https://example.com/pricing"
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • india_id_validate 0.005 USDC paid 4h ago

    Validates and decodes one Indian business or payment identifier offline: GSTIN, PAN, TAN, CIN, LLPIN, IFSC, PIN code, UPI ID and vehicle registration numbers. Detects the type automatically, normalises copy-paste noise, verifies check digits where the algorithm is public (GSTIN), and decodes embedded fields such as state, PAN holder type or company type. Aadhaar numbers are refused. Use it to clean or pre-check form and invoice data. Price: $0.005 per call, paid with x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "value"
      ],
      "properties": {
        "type": {
          "enum": [
            "auto",
            "gstin",
            "pan",
            "tan",
            "cin",
            "llpin",
            "ifsc",
            "pincode",
            "upi",
            "vehicle"
          ],
          "type": "string",
          "description": "Force a type instead of auto-detection (default auto). Case-insensitive; one of: auto, gstin, pan, tan, cin, llpin, ifsc, pincode, upi, vehicle."
        },
        "value": {
          "type": "string",
          "maxLength": 256,
          "minLength": 1,
          "description": "The identifier, e.g. 27AAPFU0939F1ZV. An optional \"type:\" prefix such as \"pan:\" is accepted; a PIN code may also be sent as a JSON number. Blank values are rejected (400, not charged)."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • llms_txt_check paid never probed

    Checks whether a domain publishes /llms.txt and /llms-full.txt and validates llms.txt against the llmstxt.org structure: single H1 title, blockquote summary, H2 sections with markdown link lists, soft-404 detection and size. Respects robots.txt. Use it before or after publishing an llms.txt file. Price: $0.005 per call, paid with x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "domain"
      ],
      "properties": {
        "domain": {
          "type": "string",
          "maxLength": 253,
          "minLength": 3,
          "description": "Domain or URL, e.g. example.com"
        }
      },
      "additionalProperties": false
    }
    arguments 15 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 f05e743ab5c0f614.

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

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.