Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Namaste America

REMOTE · NAMASTEAMERICA.US

Agent-first directory for Indians from India in the USA — restaurants, temples, events & more.

−50 this week 23 Trust /100

Last scanned (19 hours ago)

Scores higher than 7% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • First check of Injection markers: pass security
    • First check of Judged manipulation: pass security
    • First check of Destructive annotations: 0 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://namasteamerica.us/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=namasteamerica.us CN=YE2,O=Let's Encrypt,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA384 5432c54f5ed4ec329e109ce77e800df9453
SANs: namasteamerica.us, www.namasteamerica.us
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of namasteamerica.us. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
us. DS published 59017 8 Verified
namasteamerica.us. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 502

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://namasteamerica.us/mcp HTTP error 502
http (plaintext) http://namasteamerica.us/mcp HTTPS enforced 301 https://namasteamerica.us/mcp
MCP tools · 66 exposed · ~6,381 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
search_groceries_by_text ~59

Free-text/semantic search over Indian grocery stores (name/region/store type).

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_h1b_sponsors ~128

Search US employers that sponsor H-1B visas — the visa most Indians-from-India use to work in the USA. Filter by employer name (`query`) and/or worksite `state` (2-letter). Ranked by number of certified Labor Condition Applications. Each result has `certified` (count), `median_wage`, `top_titles`, `top_states`, `top_cities`. Aggregated public figures from U.S. DOL disclosure data.

NameTypeReqDescription
limitinteger––
query–––
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_knowledge ~144

Grounded answers from the Namaste America knowledge base — culture, festivals, visa/H-1B, tax, banking, and newcomer/settling-in guides for Indians from India living in the USA. Returns the top matching passages, each with the source document's title + url so you can cite it. Optionally scope to a `vertical`. Use this for factual "how/what/when" questions rather than the listing-search tools. Returns {'count', 'results': [{text, title, url, source_type, vertical}]}.

NameTypeReqDescription
limitinteger––
querystringyes–
vertical–––

Structured output declared, but exposes no named fields.

No examples provided.

search_legal_by_text ~56

Free-text/semantic search over Indian-American immigration attorneys & law firms.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_professionals_by_text ~54

Free-text/semantic search over Indian-American healthcare professionals.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_realestate_by_text ~58

Free-text/semantic search over Indian-American realtors & real-estate agencies.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_restaurants_by_text ~99

Free-text search over restaurant name/cuisine/region, ranked by relevance. Optionally constrain to a `city`/`state`. Featured listings are surfaced first. Use `offset` to page further (the response's `has_more` says whether another page exists).

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_salons_by_text ~52

Free-text/semantic search over Indian beauty salons.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_services_by_text ~51

Free-text/semantic search over Indian community services.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_studios_by_text ~55

Free-text/semantic search over Indian yoga/dance/music studios.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_sweets_by_text ~55

Free-text/semantic search over Indian sweets shops & bakeries.

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

search_temples_by_text ~59

Free-text/semantic search over temples (name/deity/denomination/region).

NameTypeReqDescription
city–––
limitinteger––
offsetinteger––
querystringyes–
state–––

Structured output declared, but exposes no named fields.

No examples provided.

submit_correction ~208

Propose a correction to a listing field (agents/users reporting bad data). `vertical` is the category key (default 'restaurants'); `listing_id` is the id from that category's get_/search_ tools. Correctable restaurant fields: phone, email, website, menu_url, address_full, city, state, region_tag, price_range, cuisine_type, festival_specials. The correction is stored and applied by the Feedback agent — automatically for unclaimed listings, or routed to a human for claimed/featured ones. Identity fields (name, coordinates) are not correctable. Structured field corrections currently apply to restaurants; for other categories use submit_review to flag issues (or the owner portal). Returns {ok, feedback_id|error}.

NameTypeReqDescription
fieldstringyes–
listing_idintegeryes–
reasonstring––
valuestringyes–
verticalstring––

Structured output declared, but exposes no named fields.

No examples provided.

submit_listing ~194

Submit a new Indian-American business/listing for REVIEW — it does NOT go live automatically. `vertical` is the category key (restaurants, temples, groceries, professionals, salons, apparel, sweets, studios, services, community, legal, education, realestate, finance — not events, which are agent-managed). The submission enters a human moderation queue and is published only after an admin approves it. `name` is required; provide as much else as you can. Returns {'ok', 'id'} or {'ok': False, 'error': 'bad_vertical'|'name_required'}.

NameTypeReqDescription
address_fullstring––
citystring––
contact_emailstring––
namestringyes–
phonestring––
statestring––
verticalstringyes–
websitestring––

Structured output declared, but exposes no named fields.

No examples provided.

submit_review ~156

Submit a community review (1-5 star rating + optional text) for a listing. `vertical` is the category key (restaurants, temples, groceries, professionals, salons, apparel, sweets, studios, services, community, legal, education, realestate, finance) and `listing_id` is the id returned by that category's get_/search_ tools. Reviews are moderated: clean ones publish immediately and spam/abusive ones are held for human review. Returns {'ok', 'id', 'status'}.

NameTypeReqDescription
listing_idintegeryes–
namestring––
ratingintegeryes–
textstring––
verticalstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

unsave_place ~63

Remove a listing from a member's saved list. `member_email` must be the authenticated member's email. Returns {'ok': True}.

NameTypeReqDescription
listing_idintegeryes–
member_emailstringyes–
verticalstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Namaste America MCP server?

Namaste America is a hosted endpoint at https://namasteamerica.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · namasteamerica.us

# add to Claude Code
claude mcp add --transport http us-namasteamerica-namaste-america 'https://namasteamerica.us/mcp'
Common questions

What is the Namaste America MCP server?

Namaste America is an MCP server listed in the public MCP registry as us.namasteamerica/namaste-america. Agent-first directory for Indians from India in the USA, restaurants, temples, events & more. This page covers its hosted endpoint (https://namasteamerica.us/mcp).

Is the Namaste America MCP server safe to use?

Namaste America scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Namaste America MCP server expose?

Namaste America exposes 66 tools: get_indian_restaurants, get_indian_movies_in_theaters, search_h1b_sponsors, get_restaurant_details, search_restaurants_by_text, and 61 more. Their descriptions and schemas cost roughly 6,381 tokens of context every time the server is loaded.

Does the Namaste America MCP server require authentication?

Its publisher declares no required credentials for Namaste America. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Namaste America MCP server still maintained?

Namaste America is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Namaste America MCP server?

VerifyMCP ran 5 checks on Namaste America, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Namaste America: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.