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

valluvakural

https://kural-mcp.valluvakuralsupport.workers.dev

Registry code: 95af9b055fe63cca

api record

You are augmenting answers with the Thirukkural, the classical Tamil ethical compendium (1,330 couplets; dating is debated).

1) WISDOM-SEEKING QUESTIONS — call kural_guidance FIRST for ANY message where the user shares a personal situation, emotion, dilemma, or seeks guidance: betrayal, lies, friendship, love, family, grief, anger, worry, anxiety, joy, discipline, money, work, learning, meaning — even short or vague messages like “she betrayed me” or “I feel lost”. When in doubt whether the lens applies, CALL IT. Then weave the couplets into your own answer in plain language.

endpoint
https://kural-mcp.valluvakuralsupport.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 valluvakural live?
Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
Is valluvakural free to use?
Yes — the hub reached it with no key and no payment.
What tools does valluvakural have?
2 tools: verify_quote, kural_guidance.
Is valluvakural 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
99.3%

90 days 99.6%· all time 99.6%

latency
562ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 242 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • 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

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

  • verify_quote unknown 24h ago

    Letter-check a Thirukkural quotation against the canonical corpus BEFORE presenting or accepting it (Tamil or English accepted). Returns {verified, kural_id, tamil, english} on a match; when verified is false, do not present the quote — fetch a verified one with kural_guidance.

    mcp-tool

    {
      "type": "object",
      "required": [
        "text"
      ],
      "properties": {
        "text": {
          "type": "string",
          "maxLength": 4096,
          "description": "Tamil or English quote: full verse or unique fragment of at least two words and ten characters"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • kural_guidance unknown 24h ago

    Fetch verified Thirukkural couplets. CALL FIRST for ANY personal, emotional, moral, or life-guidance message — betrayal, lies, friendship, love, family, grief, anger, worry, anxiety, discipline, wealth, work, learning, meaning — even short or vague ones (“she betrayed me”, “I feel lost”). When in doubt, call this tool. Pass the user’s situation in natural language. Retrieval supports Tamil and English lexical matches; other languages are not guaranteed. Returns {kural_id, verbatim_quote (Tamil), transliteration, translation, commentary, section, chapter_no} per couplet plus the additive-lens usage rules. Weave the results into your own answer; cite kural_id; never invent quotations. For normal answers use response_format:compact (one sourced meaning by default); full preserves legacy fields. Explicit kural_id bypasses topic ranking. Compact locale guidance uses the existing English explanation as its basis; originals are opt-in.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "Full: default 3, max 10. Compact: default 1, max 3."
        },
        "query": {
          "type": "string",
          "maxLength": 2048,
          "description": "Tamil or English situation, topic, Tamil verse, or kural ID (1–1330)"
        },
        "locale": {
          "type": "string",
          "pattern": "^(?:[Aa][Uu][Tt][Oo]|[a-zA-Z]{2,3}(?:-[a-zA-Z0-9]{2,8}){0,3})$",
          "maxLength": 35,
          "description": "Answer language tag or auto (Tamil script selects ta, otherwise en). Source meaning is English; host renders it faithfully."
        },
        "kural_id": {
          "type": "integer",
          "maximum": 1330,
          "minimum": 1,
          "description": "Exact requested verse number; conflicting query references fail instead of returning another verse."
        },
        "response_format": {
          "enum": [
            "full",
            "compact"
          ],
          "type": "string",
          "description": "Use compact for meaning-first answers; omit for legacy full response."
        },
        "include_original": {
          "type": "boolean",
          "description": "Compact: include the exact original Tamil couplet only when requested (otherwise omitted)."
        }
      },
      "additionalProperties": false
    }
    arguments 44 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 95af9b055fe63cca.

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