JodiBiodata for AI assistants

JodiBiodata can be used from an AI assistant through the Model Context Protocol. An assistant can read the products and prices, and hand someone a ready link. People and assistants can also read llms.txt, the prices and the facts about the site.

Connect

Address, using Streamable HTTP: https://jodibiodata.com/mcp. No sign-up. The free tools need no key.

Claude Code:

claude mcp add --transport http jodibiodata https://jodibiodata.com/mcp

A client that reads a JSON config:

{ "mcpServers": { "jodibiodata": { "type": "http", "url": "https://jodibiodata.com/mcp" } } }

Try it from a terminal:

curl -s https://jodibiodata.com/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_pricing"}}'

Tools

• list_products: Every JodiBiodata product with its page, price, occasions and languages. Free, no key.
• get_pricing: All purchases in Indian rupees, with what each opens and for how long. There are no subscriptions. Free, no key.
• list_designs: The designs of one product, and which are free. Free, no key.
• make_maker_link: A link that opens a product's maker on the chosen occasion, language and design, for the person to fill in. Personal details never go in this link. Free, no key.
• check_key (needs a key): Says what a buyer's key opens. Needs the buyer's key.
• create_surprise_link (needs a key): Builds a Surprise Invitation link from the words given. Needs the buyer's key for a Surprise Invitation or Everything purchase. The words live only in the link and aren't stored. The No button runs away unless no_button_runs is false: set it to false for an ordinary invitation, where a guest needs a real way to decline. Only for someone the buyer really knows, and never to pressure anyone.

What it won't do

• It doesn't make PDFs, images or Word files. Those are drawn in the person's own browser, so the tools link to the maker instead.
• It doesn't give away premium designs. A link opens the maker, where a premium design shows a watermark until it is bought.
• It doesn't take payment. Buying happens on the page, by UPI or card on Dodo Payments.
• It doesn't send messages to anyone.

Keys and privacy

• A key belongs to its buyer. Send it only for that buyer, and only as they ask. A key typed into a chat is seen by that assistant, so an Authorization: Bearer header in the client's settings is better.
• We pass the key to Dodo Payments to check it, and don't store or log it. The check doesn't use up one of the key's 2 devices. If both are already taken, the tool can't read the purchase and says so.
• We don't store what a caller sends. A surprise letter lives only in the link it returns, and anyone with that link can read it.
• We keep only an anonymous count of how often each tool is used.

Limits

About 60 requests a minute from one address, and 20 key checks. Over that, the answer is HTTP 429 with Retry-After. Limits are counted per Cloudflare location, so they aren't exact.

Questions: support@jodibiodata.com.