tf_payment_history — terminalfeed MCP Tool
tf_payment_history
(tf payment history) is one of 27 tools on the
terminalfeed
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tf_payment_history from your client
- Claude Code terminalfeed tf_payment_history run in your project directory
- Claude Desktop terminalfeed tf_payment_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor terminalfeed tf_payment_history ~/.cursor/mcp.json
- VS Code terminalfeed tf_payment_history .vscode/mcp.json
- Zed terminalfeed tf_payment_history ~/.config/zed/settings.json
- Windsurf terminalfeed tf_payment_history ~/.codeium/windsurf/mcp_config.json
- Cline terminalfeed tf_payment_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI terminalfeed tf_payment_history ~/.gemini/settings.json
- Grok terminalfeed tf_payment_history .mcp.json (in your project root)
- ChatGPT terminalfeed tf_payment_history Settings → Connectors → Advanced → Developer mode
- Claude.ai terminalfeed tf_payment_history Settings → Connectors → Add custom connector
- LangChain terminalfeed tf_payment_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http terminalfeed https://terminalfeed.io/api/mcp
Other tools on this server
- tf_briefing
- tf_btc_price
- tf_fear_greed
- tf_crypto_movers
- tf_predictions
- tf_earthquakes
- tf_climate_earthquakes
- tf_climate_weather_alerts
- tf_service_status
- tf_economic_data
- tf_forex
- tf_hf_trending
- tf_harnesses
- tf_solana_network
- tf_ai_stack_cves
- tf_premium_briefing
- tf_premium_macro
- tf_premium_github_velocity
- tf_premium_feed_reliability
- tf_premium_feed_reliability_history
- tf_premium_correlation_matrix
- tf_premium_agent_context
- tf_premium_world_deltas
- tf_payment_buy_credits
- tf_payment_confirm
- tf_payment_balance
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.