get_staleness_report — BioCosm MCP Tool Read-only
get_staleness_report
(get staleness report) is one of 13 tools on the
BioCosm
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_staleness_report from your client
- Claude Code BioCosm get_staleness_report run in your project directory
- Claude Desktop BioCosm get_staleness_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BioCosm get_staleness_report ~/.cursor/mcp.json
- VS Code BioCosm get_staleness_report .vscode/mcp.json
- Zed BioCosm get_staleness_report ~/.config/zed/settings.json
- Windsurf BioCosm get_staleness_report ~/.codeium/windsurf/mcp_config.json
- Cline BioCosm get_staleness_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BioCosm get_staleness_report ~/.gemini/settings.json
- Grok BioCosm get_staleness_report .mcp.json (in your project root)
- ChatGPT BioCosm get_staleness_report Settings → Connectors → Advanced → Developer mode
- Claude.ai BioCosm get_staleness_report Settings → Connectors → Add custom connector
- LangChain BioCosm get_staleness_report pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http biocosm https://biocosm-mcp.fly.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.