Skip to content

life.ayushrai.site docs MCP server

site.ayushrai.life/docslife.ayushrai.sitestreamable-httpv1.0.0Scanned

Read-only index of the public documentation and section pages on life.ayushrai.site.

2 tools: 2 only read.

Tools: 0 delete, 0 irreversible, 0 write, 2 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the life.ayushrai.site docs MCP server can do

The life.ayushrai.site docs MCP server is published by life.ayushrai.site, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (list_docs and read_doc).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 18, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Only reads 2Show 2 read-only tools
  • list_docsList public documentation and section pages on life.ayushrai.site (developers, auth, OpenAPI, sandbox, jobs).Reads private dataNo findings

    Why it is in this group

    • The name "list_docs" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_docs" says "list" and "doc": it reads documents.
    Description, as the server wrote it
    List public documentation and section pages on life.ayushrai.site (developers, auth, OpenAPI, sandbox, jobs). Optional section name narrows the list.

    Annotations the server declares

    • readOnlyHint: true
  • read_docFind documentation pages on life.ayushrai.site that match a query and return titles with URLs to cite.Reads private dataNo findings

    Why it is in this group

    • The name "read_doc" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_doc" says "read" and "doc": it reads documents.
    Description, as the server wrote it
    Find documentation pages on life.ayushrai.site that match a query and return titles with URLs to cite.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://life.ayushrai.site/.well-known/oauth-protected-resource
Authorization servers
https://life.ayushrai.site
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 402 to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://life.ayushrai.site/.well-known/oauth-protected-resource
    • Authorization servers: none to https://life.ayushrai.site
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://life.ayushrai.site/.well-known/oauth-protected-resource to none
    • Authorization servers: https://life.ayushrai.site to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 402 -> 200; tools/list served without credentials: no -> yes; Protocol version: none -> 2025-06-18 (and 4 more).View diff
    • HTTP status of an anonymous initialize: 402 to 200
    • tools/list served without credentials: no to yes
    • Protocol version: none to 2025-06-18
    • RFC 9728 protected resource metadata: none to https://life.ayushrai.site/.well-known/oauth-protected-resource
    • Authorization servers: none to https://life.ayushrai.site
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Tools2 changed.~2 changedView diff
  3. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 402; tools/list served without credentials: yes -> no; Protocol version: 2025-06-18 -> none (and 4 more).View diff
    • HTTP status of an anonymous initialize: 200 to 402
    • tools/list served without credentials: yes to no
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://life.ayushrai.site/.well-known/oauth-protected-resource to none
    • Authorization servers: https://life.ayushrai.site to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http docs https://life.ayushrai.site/mcp/docs
claude mcp add --transport http docs https://life.ayushrai.site/mcp/docs

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__docs__list_docs",
      "mcp__docs__read_doc"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as docs. Review it before you use it.

Capability tags behind 2 rules
  • mcp__docs__list_docs private-data
  • mcp__docs__read_doc private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/site.ayushrai.life/docs/verify?hash=ca1d70d16121e54b7f33dce63de458feab8d380d0dd4f9f49ebacb6c91e19466" | jq -e '.changed == false'

Pinned hash ca1d70d16121, from Nov 18, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/site.ayushrai.life/docs/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for site.ayushrai.life/docs
[![Anlyon Radar](https://radar.anlyon.com/badge/site.ayushrai.life/docs.svg)](https://radar.anlyon.com/servers/site.ayushrai.life/docs)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:54 UTC.

life.ayushrai.site docs MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the life.ayushrai.site docs MCP server safe?

No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the life.ayushrai.site docs MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the life.ayushrai.site docs MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the life.ayushrai.site docs MCP server have?

2 tools: 2 read. list_docs and read_doc.

Does the life.ayushrai.site docs MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the life.ayushrai.site docs MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the life.ayushrai.site docs MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.