what_changed_since — Seraphix Public Records MCP Tool
what_changed_since
(what changed since) is one of 20 tools on the
Seraphix Public Records
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call what_changed_since from your client
- Claude Code Seraphix Public Records what_changed_since run in your project directory
- Claude Desktop Seraphix Public Records what_changed_since ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Seraphix Public Records what_changed_since ~/.cursor/mcp.json
- VS Code Seraphix Public Records what_changed_since .vscode/mcp.json
- Zed Seraphix Public Records what_changed_since ~/.config/zed/settings.json
- Windsurf Seraphix Public Records what_changed_since ~/.codeium/windsurf/mcp_config.json
- Cline Seraphix Public Records what_changed_since ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Seraphix Public Records what_changed_since ~/.gemini/settings.json
- Grok Seraphix Public Records what_changed_since .mcp.json (in your project root)
- ChatGPT Seraphix Public Records what_changed_since Settings → Connectors → Advanced → Developer mode
- Claude.ai Seraphix Public Records what_changed_since Settings → Connectors → Add custom connector
- LangChain Seraphix Public Records what_changed_since pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http public-records https://seraphixsystems.com/mcpOther tools on this server
- search_records
- get_record
- list_companies
- get_company
- get_filings_wire
- get_coverage
- answer
- graph_neighborhood
- who_is_behind
- create_board
- pilot02_follow_the_money
- tx_site_status
- search_organizations
- get_organization_record
- screen_organizations
- get_whats_moving
- list_feed_sources
- get_feed_events
- explain_record
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.