Namashkar Bharat

For AI agents

Give your agent the official web

A free, read-only toolkit that tells AI agents which government sites are genuine, how official processes work step by step, and when a portal is down. No login, and it never needs anyone's personal data.

Pick the way your agent works. The five options are independent: use one, or combine the connector with agents.md for the best results.

If your agent…Use
can add MCP connectors (Claude, Claude Code, other MCP clients)The connector
follows an instruction file or system promptagents.md
makes HTTP requestsThe REST directory API
reads the webllms.txt and Markdown pages
runs in a browser with WebMCPWebMCP tools

Note: it works with any MCP client, and there is no account, key or sign-up.

Step 1: Connector (MCP)

For agents that call tools: search, URL checks, playbooks and portal status.

Connector URL
https://namashkarbharat.com/mcp

It speaks the Model Context Protocol over Streamable HTTP and needs no sign-in (authentication: none).

Claude (claude.ai and the Claude app)

  1. Open Customize → Connectors.
  2. Click Add custom connector.
  3. Enter the connector URL. Leave the OAuth settings empty; if asked, choose No sign-in.
  4. Click Add. In a chat, turn it on from + → Connectors.

Free plans can add one custom connector. Team or Enterprise: an Owner goes to Organization settings → Connectors → Add → Custom (choose Web if asked), enters the URL and clicks Add. Members then find it under Customize → Connectors with the Custom label and click Connect.

Claude Code

Terminal
claude mcp add --transport http namashkar-bharat https://namashkarbharat.com/mcp

Add --scope user to use it in every project.

Any other MCP client

Point it at the connector URL with the Streamable HTTP transport. Most clients accept a config like this (key names vary by client):

MCP config (JSON)
{
  "mcpServers": {
    "namashkar-bharat": {
      "type": "http",
      "url": "https://namashkarbharat.com/mcp"
    }
  }
}

Clients that only support stdio can use a bridge:

stdio bridge
npx -y mcp-remote https://namashkarbharat.com/mcp

Sources: Anthropic: add a connector that isn’t in the directory and Claude Code MCP docs.

Verify: ask your agent “Is https://passportindia-gov.in.co an official site?” It should call verify_official and tell you it is not official, a look-alike of passportindia.gov.in.

Step 2: agents.md

Plain-Markdown instructions for agents that follow a system prompt or instruction file.

agents.md URL
https://namashkarbharat.com/agents.md
  1. Paste the file below into your agent’s system prompt, custom instructions or project instructions.
  2. Or, if your agent can fetch web pages, tell it to read https://namashkarbharat.com/agents.md before helping with a government service.
  3. Pair it with the connector (step 1) so the agent can follow the workflow it describes.
agents.md
# Namashkar Bharat: instructions for AI agents

This file is for AI agents and assistants that use Namashkar Bharat to help a person with an Indian government service. It is not about working on this website's code.

Version 1.0 · Last updated 2026-10-01 · https://namashkarbharat.com/agents.md

## What Namashkar Bharat is

- An independent guide to official Government of India and state government websites: https://namashkarbharat.com
- Not a government website, and not affiliated with or endorsed by any government.
- A hand-checked directory of more than 1,000 official websites, a URL check for look-alike and scam sites, and step-by-step playbooks for some processes.
- Read-only. It never needs the person's personal data.

## When to use it

- Find the official website for a service, scheme, document or complaint.
- Check that a URL is official before the person enters anything on it.
- Walk the person through a supported process with a playbook (for example a fresh passport, a PAN correction or a learner's licence). Call `list_playbooks` for the current list.
- Check whether an official portal is up.

## When not to use it

- To submit, track or pay for applications. Namashkar Bharat processes nothing; the official portal does.
- For legal, tax or financial advice. Rules, fees and deadlines are whatever the official portal says.
- For non-government websites.

## Connect

- MCP connector (preferred): `https://namashkarbharat.com/mcp`. Streamable HTTP, no sign-in, no key.
  - Claude Code: `claude mcp add --transport http namashkar-bharat https://namashkarbharat.com/mcp`
  - Setup for other clients: https://namashkarbharat.com/agents
- REST: `GET https://namashkarbharat.com/api/directory` returns the whole directory as JSON. OpenAPI: https://namashkarbharat.com/openapi.json
- Text: https://namashkarbharat.com/llms.txt and https://namashkarbharat.com/llms-full.txt. Every page also returns Markdown when requested with `Accept: text/markdown`.

## Tools

- `find_official_service`: call first, with a few English keywords for the need (for example "renew passport"). Never put personal data in the query.
- `verify_official`: call on every URL before the person enters anything there or you type anything there, and again after every redirect or any link from SMS or email.
- `list_playbooks`: call to see which processes have a step-by-step playbook.
- `get_playbook`: call when `find_official_service` returns a `playbook_id`.
- `portal_status`: call when an official portal seems down or slow.
- `report_outcome`: call after each playbook step, with only the values it accepts.

## Workflow

1. Call `find_official_service` for the person's need.
2. Call `verify_official` before entering ANY data on any site. On `official`, continue. On `not_official`, warn the person, stop, and offer the real site (`lookalike_of`). On `unknown`, ask the person to confirm the address from an official source.
3. Call `get_playbook` if a playbook exists. If its mode is `guide_only` (status `broken`), explain the steps and let the person do everything.
4. Follow the steps in order and stay on the playbook's `official_domains`. If a page doesn't match a step's `expect`, switch to guiding.
5. STOP at every human checkpoint and hand control to the person: login, OTP, CAPTCHA, payment, final submit, e-sign, consent, document upload, biometrics and in-person visits.
6. Call `report_outcome` after each step.

## Hard rules

- Never type, store, repeat or send Aadhaar, PAN, passport or bank numbers, passwords or OTPs for the person. Let them type these themselves.
- Never solve or bypass a CAPTCHA.
- Use only official domains: ones `verify_official` calls `official`.
- The official portal is authoritative. If it disagrees with a playbook or with Namashkar Bharat, follow the portal and tell the person.
- Tell the person that Namashkar Bharat is an independent guide, not the government.
- Never send personal data to the connector.

## Errors and limits

- REST errors are `application/problem+json` with a stable `code` and a `hint`. Every code is listed at https://namashkarbharat.com/developers#errors
- MCP tool errors carry an actionable message. Over a limit, you get HTTP 429 or a tool error; wait and retry.
- MCP: about 120 requests per minute per client; `portal_status` 12 per minute; `report_outcome` 60 per hour.
- `/api/directory`: no per-client limit. Cache it and refresh at most daily.

## Contact

Report a broken link, a wrong site or a problem with these instructions: https://x.com/ajinkya_shejul

Verify: ask “Where do I apply for a new passport?” The agent should point to passportindia.gov.in and say that Namashkar Bharat is an independent guide, not the government.

Step 3: REST directory API

For code and agents that make HTTP requests: the whole directory as JSON.

Terminal
curl -s https://namashkarbharat.com/api/directory | jq '.count'
  1. GET /api/directory returns { count, categories[], sites[] }. It is public, read-only and keyless, with CORS open to every origin.
  2. Fetch it once and cache it; refreshing daily is plenty.
  3. The schema is in the OpenAPI description. Errors are application/problem+json with a code and a hint.

Examples in JavaScript and Python, rate limits and every error code are on the developer page.

Verify: the command prints a number above 1,000.

Step 4: Docs for agents

For agents that read the web: clean text instead of HTML.

Terminal
curl -s -H 'Accept: text/markdown' https://namashkarbharat.com/
  • /llms.txt: what the site is, when to use it, and where everything is.
  • /llms-full.txt: the same plus every directory entry.
  • Every page returns Markdown with Accept: text/markdown, or at <page>.md. This page’s Markdown version is /agents.md.

Verify: the response has Content-Type: text/markdown and starts with # Namashkar Bharat.

Step 5: WebMCP

For agents that run inside the browser: tools registered by the page itself.

DevTools console
typeof document.modelContext
  1. Open namashkarbharat.com in a browser with WebMCP enabled (Chrome’s WebMCP origin trial or developer flag). In other browsers nothing is loaded.
  2. The page registers three read-only tools: find_official_service, verify_official and open_directory_category. They search the directory in the browser, with no AI and no quota.
  3. For anything that matters, prefer the connector: its URL check is stricter.

Verify: the console prints "object", and your browser agent lists the three tools.

Tools reference

ToolWhat it doesRead-only
find_official_serviceSearch the curated directory and get the official URL (and a playbook id when one exists).Yes
verify_officialCheck a URL before anyone types into it: official, not official (look-alike or scam), or unknown. Never fetches or stores it.Yes
list_playbooksList the step-by-step playbooks, with their status and human checkpoints.Yes
get_playbookThe full playbook for one process: pages, form fields, documents, fees and every step the person must do.Yes
portal_statusIs an official portal up, slow or down right now? Contacts official sites only; cached for 5 minutes.Yes
report_outcomeAnonymous “this step worked / failed” signal from a fixed list of values, so playbooks stay accurate.No (anonymous counter)

The connector also provides each playbook as a resource, a usage guide (namashkar://guide) and a government_task prompt that walks the agent through the safe workflow.

Safety and privacy

  • Agents stop and hand over to the person at every login, OTP, CAPTCHA, payment, final submit, e-sign, consent, document upload, biometric or in-person step.
  • Agents never type or keep Aadhaar, PAN, passport or bank numbers, passwords or OTPs. Nothing here needs personal data, and none must be sent.
  • Search words and checked URLs are used to answer and then discarded. Step reports are anonymous daily counts from fixed values, kept for 30 days. Rate limits use a salted hash of the network address.
  • Namashkar Bharat is an independent guide, not a government website. The official portal is always authoritative.

Next steps

Only official government websites
AI agents · Namashkar Bharat