get_recent_changes — NEARpedia MCP Tool Read-only
get_recent_changes
(get recent changes) is one of 27 tools on the
NEARpedia
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_recent_changes from your client
- Claude Code NEARpedia get_recent_changes run in your project directory
- Claude Desktop NEARpedia get_recent_changes ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NEARpedia get_recent_changes ~/.cursor/mcp.json
- VS Code NEARpedia get_recent_changes .vscode/mcp.json
- Zed NEARpedia get_recent_changes ~/.config/zed/settings.json
- Windsurf NEARpedia get_recent_changes ~/.codeium/windsurf/mcp_config.json
- Cline NEARpedia get_recent_changes ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NEARpedia get_recent_changes ~/.gemini/settings.json
- Grok NEARpedia get_recent_changes .mcp.json (in your project root)
- ChatGPT NEARpedia get_recent_changes Settings → Connectors → Advanced → Developer mode
- Claude.ai NEARpedia get_recent_changes Settings → Connectors → Add custom connector
- LangChain NEARpedia get_recent_changes pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http near-pedia https://near-pedia.xyz/mcpOther tools on this server
- search
- get_discussion
- get_doc
- get_network_state
- get_validators
- list_videos
- semantic_search
- list_blog_posts
- get_blog_post
- find_code_examples
- get_breaking_changes
- find_known_issues
- check_deprecation
- resolve_package
- explain_error
- get_standard
- get_contract_info
- check_code
- get_protocol_status
- list_proposals
- get_proposal
- find_project
- list_incidents
- get_incident
- get_partner
- get_radar
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.