Home / MCP registry index / us.namasteamerica/namaste-america

Namaste America

us.namasteamerica/namaste-america in the official MCP registry. Endpoint https://namasteamerica.us/mcp. Source: github.com/manvigallc007-spec/indousmcp.

The registry describes it as: Agent-first directory for Indians from India in the USA — restaurants, temples, events & more.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http namaste-america https://namasteamerica.us/mcp

{
  "mcpServers": {
    "namaste-america": {
      "url": "https://namasteamerica.us/mcp"
    }
  }
}

code --add-mcp '{"name":"namaste-america","type":"http","url":"https://namasteamerica.us/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_indian_restaurants get_indian_movies_in_theaters search_h1b_sponsors get_restaurant_details search_restaurants_by_text submit_correction submit_review get_reviews get_indian_temples get_temple_details search_temples_by_text get_indian_groceries get_grocery_details search_groceries_by_text get_indian_professionals get_professional_details search_professionals_by_text get_indian_salons get_salon_details search_salons_by_text get_indian_events get_event_details search_events_by_text get_indian_apparel get_apparel_details search_apparel_by_text get_indian_sweets get_sweets_details search_sweets_by_text get_indian_studios get_studio_details search_studios_by_text get_indian_services get_service_details search_services_by_text get_indian_community get_community_details search_community_by_text get_indian_legal get_legal_details search_legal_by_text get_indian_education get_education_details search_education_by_text get_indian_realestate get_realestate_details search_realestate_by_text get_indian_finance get_finance_details search_finance_by_text search_all get_festival_dates search_knowledge submit_listing get_movie_details get_h1b_sponsor_details search_community_questions get_community_answers get_today_highlights get_offers and 6 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): a81d24d57c355c47. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/us-namasteamerica-namaste-america/badge.svg)](https://lazaretto.dev/mcp-registry/us-namasteamerica-namaste-america)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.