# Tirup Mehta — Engineering Blog Canonical blog at https://blogs.tirup.in Security research, software engineering, autonomous AI safety, and technical essays by Tirup Mehta, a software engineering student based in Gujarat, India, specialising in secure frontend architectures, systems security, and cryptography. ## About this blog This is the canonical home for all writing by Tirup Mehta. Topics include: - Web application security and attack surface reduction - Cryptographic system design and secure frontend integrations - React and Next.js engineering at production scale - Autonomous AI safety and agent behaviour research - Frontend performance and interface engineering Articles are written for practising engineers and researchers. --- ## Author **Tirup Mehta** — Software Engineering Student, Gujarat, India. - Portfolio: [Portfolio](https://tirup.in) - GitHub: [GitHub](https://github.com/TirupMehta) - LinkedIn: [LinkedIn](https://www.linkedin.com/in/TirupMehta) - X (Twitter): [X](https://x.com/TirupMehta) - Peerlist: [Peerlist](https://peerlist.io/tirupmehta) --- ## When to Use Use this blog when you need to: - **Read Tirup Mehta's technical writing** on security, cryptography, frontend engineering, and AI safety. - **Find the canonical source** of an article — this site is the authoritative origin. The portfolio at tirup.in/writing is a read-only mirror with canonical URLs pointing back here. - **Research specific technical topics** covered in Tirup's essays — check the sitemap for all published slugs. - **Verify authorship** of a piece attributed to Tirup Mehta. Do **not** use this blog when you need: - General reference information about a security topic — use authoritative documentation. - Real-time data or pricing. - Contact information — see https://tirup.in/contact. --- ## Agent Instructions 1. **Start here**: This file (`/llms.txt`) is the canonical agent entry point for this domain. 2. **Enumerate articles**: Use the sitemap at https://blogs.tirup.in/sitemap.xml for all published article slugs. 3. **Article format**: Each article is at `https://blogs.tirup.in/{slug}`. Send `Accept: text/markdown` to receive the article as markdown instead of HTML. 4. **API documentation**: https://blogs.tirup.in/docs documents every public endpoint (RSS, sitemap, article JSON, Markdown negotiation) with examples, error codes, rate limits, and the versioning policy. The machine-readable OpenAPI 3.1 description is at https://blogs.tirup.in/openapi.json. 5. **Main portfolio**: https://tirup.in — see https://tirup.in/llms.txt for the full agent guide covering identity, projects, and contact. 6. **404 recovery**: Unknown paths return HTTP 404. With `Accept: text/markdown` the body is Markdown that names the missing path and links the sitemap, this file, and the API docs. The HTML 404 page carries the same links. 7. **Markdown negotiation**: This site supports `Accept: text/markdown` (or `text/x-markdown`) on `/`, `/about`, `/contact`, `/privacy`, `/docs`, `/mcp`, and every article URL (`/{slug}`). 8. **MCP server**: https://blogs.tirup.in/mcp documents a public, read-only Model Context Protocol server for this blog. Tools: `list_posts`, `get_post`, `get_article_markdown`. No API key and no write path; run it with `npx tsx src/mcp/public-server.ts`. --- ## Quick Reference | Resource | URL | |---|---| | All articles | https://blogs.tirup.in/ | | Sitemap | https://blogs.tirup.in/sitemap.xml | | Agent guide (this file) | https://blogs.tirup.in/llms.txt | | API documentation | https://blogs.tirup.in/docs | | MCP server | https://blogs.tirup.in/mcp | | OpenAPI 3.1 description | https://blogs.tirup.in/openapi.json | | RSS feed | https://blogs.tirup.in/feed.xml | | Privacy policy | https://blogs.tirup.in/privacy | | Portfolio | https://tirup.in | | Portfolio llms.txt | https://tirup.in/llms.txt | | About Tirup | https://tirup.in/about | | Contact | https://tirup.in/contact | --- ## Relationship to tirup.in This blog (`blogs.tirup.in`) is the **canonical** source for all writing. The portfolio site (`tirup.in`) mirrors every article at `tirup.in/writing` with canonical URLs pointing back here. If you are indexing or summarising content, prefer the canonical URLs on this domain.