Home / MCP registry index / io.github.aatharva16/dalalos
DalalOS
io.github.aatharva16/dalalos in the official MCP registry.
Endpoint https://mcp.dalalos.in/mcp. Source: github.com/BeyondNoww/indianstock-data-mcp.
The registry describes it as: Indian NSE/BSE research data and mechanically-computed ratios; read-only market tools.
We read its 62 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
ping get_filing_extract get_filing_extracts get_market_fii_dii_flow get_stock_fii_flow get_watchlist add_to_watchlist remove_from_watchlist search_stocks get_stock_quote get_batch_quotes get_financials get_company_profile get_company_report get_peer_comparison get_shareholding get_price_history get_valuation_history get_returns get_technical_indicators get_delivery_trends get_dividends get_brsr get_bulk_block_deals get_derivatives_positioning get_fo_participant_activity get_fno_ban_list get_corporate_actions get_stock_events search_company_disclosures get_event_context get_company_operating_metrics get_company_macro_exposures get_company_exposures get_relevant_peers list_announcement_buckets get_announcement_bucket screen_stocks screen_by_query get_sector_overview list_index_constituents list_indices get_market_heatmap get_top_movers list_preset_screens run_preset_screen get_upcoming_results get_fii_dii_flow get_index_valuation list_index_valuations get_india_vix get_market_breadth get_macro_indicators get_fx_reference_rates get_sector_fii_flow get_sector_fpi_investment get_fii_activity get_market_calendar get_ipos get_financial_trends and 2 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-github-aatharva16-dalalos)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.