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

pocket-pothi

https://pocketpothi.com

Registry code: a22bae97281d76dd

api record

Pocket Pothi has verified texts of Hindu prayers (stotras, aartis, chalisas, shlokas, Bhagavad Gita chapters, Manache Shlok) in Devanagari with simple Roman spelling. Use search to find a text by name, first line, deity or type; get_text or fetch for the full text. Quote verses exactly as returned — never rewrite or complete them from memory. Link the text page (url) when you quote. To give someone a daily order of prayers they can open in one tap, call make_pothi_link with the ids in order.

endpoint
https://pocketpothi.com/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 pocket-pothi live?
Yes — it answered the hub's last check (checked 3m ago). It answered 100% of checks over the last 30 days.
Is pocket-pothi free to use?
Yes — the hub reached it with no key and no payment.
What tools does pocket-pothi have?
5 tools: search, make_pothi_link, fetch, get_text, list_texts.
Is pocket-pothi 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
284ms

last good check

priced tools
0

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
1 open 4 never probed 1 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.

  • list_texts open 3m ago

    List the catalog, optionally filtered by deity or type. Returns ids, titles, type, language, verse count and links (no full text).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "type": {
      "enum": [
        "aarti",
        "ashtakam",
        "stotra",
        "gita-adhyaya",
        "shloka",
        "suktam",
        "mantra",
        "bhajan",
        "chalisa",
        "sahasranama"
      ],
      "type": "string"
    },
    "deity": {
      "enum": [
        "agni",
        "amba",
        "ayyappa",
        "bhairava",
        "brahman",
        "dattatreya",
        "durga",
        "ganesha",
        "guru",
        "hanuman",
        "krishna",
        "lakshmi",
        "lalita",
        "navagraha",
        "rama",
        "sai-baba",
        "saraswati",
        "savitr",
        "shiva",
        "surya",
        "venkateshwara",
        "vishnu",
        "vishvatmaka",
        "vitthala"
      ],
      "type": "string"
    },
    "include_book_chapters": {
      "type": "boolean",
      "description": "Include the 18 Bhagavad Gita chapters (default false)"
    }
  }
}
    arguments 53 lines
  • search unknown never probed

    Search Pocket Pothi's verified Hindu prayer texts by name, alias, first line or a phrase (Devanagari or English letters), deity or type. Returns ids, titles and page URLs; use fetch or get_text for the full text.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "e.g. \"hanuman chalisa\", \"shubham karoti\", \"जय गणेश\", \"aarti for Shiva\", \"Gita chapter 12\""
    }
  }
}
    arguments 12 lines
  • make_pothi_link unknown never probed

    Build a short pocketpothi.com link that opens several prayers in the given order, to read in one scroll or send to family (e.g. on WhatsApp). Nothing is saved; the link encodes the order.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 40,
      "minItems": 1,
      "description": "Text ids in reading order"
    },
    "from_name": {
      "type": "string",
      "description": "Optional sender name shown on the link, e.g. \"Aai\""
    }
  }
}
    arguments 21 lines
  • fetch unknown 3m ago

    Get the full verified text of one prayer by id (from search): every verse in Devanagari with simple Roman spelling. Quote it exactly.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Text id from search, e.g. \"hanuman-chalisa\""
    }
  }
}
    arguments 12 lines
  • get_text unknown 3m ago

    Full verified text of one prayer, in Devanagari, simple Roman (English letters), or both. Use for recitation help or when the user reads only one script.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    },
    "script": {
      "enum": [
        "both",
        "devanagari",
        "roman"
      ],
      "type": "string",
      "default": "both"
    }
  }
}
    arguments 20 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 a22bae97281d76dd.

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