space_score_history — SpaceNexus space data MCP Tool
space_score_history
(space score history) is one of 14 tools on the
SpaceNexus space data
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call space_score_history from your client
- Claude Code SpaceNexus space data space_score_history run in your project directory
- Claude Desktop SpaceNexus space data space_score_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SpaceNexus space data space_score_history ~/.cursor/mcp.json
- VS Code SpaceNexus space data space_score_history .vscode/mcp.json
- Zed SpaceNexus space data space_score_history ~/.config/zed/settings.json
- Windsurf SpaceNexus space data space_score_history ~/.codeium/windsurf/mcp_config.json
- Cline SpaceNexus space data space_score_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SpaceNexus space data space_score_history ~/.gemini/settings.json
- Grok SpaceNexus space data space_score_history .mcp.json (in your project root)
- ChatGPT SpaceNexus space data space_score_history Settings → Connectors → Advanced → Developer mode
- Claude.ai SpaceNexus space data space_score_history Settings → Connectors → Add custom connector
- LangChain SpaceNexus space data space_score_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http spacenexus https://spacenexus.us/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 30 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.