Is us.namasteamerica/namaste-america up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://namasteamerica.us/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://namasteamerica.us/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://namasteamerica.us with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 66 tools: ask_community_question, follow_city, get_apparel_details, get_community_answers, get_community_details, get_education_details, get_event_details, get_festival_dates, get_finance_details, get_grocery_details, get_h1b_sponsor_details, get_indian_apparel, get_indian_community, get_indian_education, get_indian_events, get_indian_finance, get_indian_groceries, get_indian_legal, get_indian_movies_in_theaters, get_indian_professionals, get_indian_realestate, get_indian_restaurants, get_indian_salons, get_indian_services, get_indian_studios, get_indian_sweets, get_indian_temples, get_legal_details, get_movie_details, get_offers, get_professional_details, get_realestate_details, get_restaurant_details, get_reviews, get_salon_details, get_service_details, get_studio_details, get_sweets_details, get_temple_details, get_today_highlights, list_follows, list_saved_places, save_place, search_all, search_apparel_by_text, search_community_by_text, search_community_questions, search_education_by_text, search_events_by_text, search_finance_by_text, search_groceries_by_text, search_h1b_sponsors, search_knowledge, search_legal_by_text, search_professionals_by_text, search_realestate_by_text, search_restaurants_by_text, search_salons_by_text, search_services_by_text, search_studios_by_text, search_sweets_by_text, search_temples_by_text, submit_correction, submit_listing, submit_review, unsave_place.
No change to its tools between 2026-09 and 2026-10.
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | us.namasteamerica/namaste-america |
|---|---|
| Endpoint | https://namasteamerica.us/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt