report_search_outcome — Tenjin MCP Tool

report_search_outcome (report search outcome) is one of 23 tools on the Tenjin MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call report_search_outcome from your client

Claude Code Tenjin report_search_outcome run in your project directory
Claude Desktop Tenjin report_search_outcome ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Tenjin report_search_outcome ~/.cursor/mcp.json
VS Code Tenjin report_search_outcome .vscode/mcp.json
Zed Tenjin report_search_outcome ~/.config/zed/settings.json
Windsurf Tenjin report_search_outcome ~/.codeium/windsurf/mcp_config.json
Cline Tenjin report_search_outcome ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Tenjin report_search_outcome ~/.gemini/settings.json
Grok Tenjin report_search_outcome .mcp.json (in your project root)
ChatGPT Tenjin report_search_outcome Settings → Connectors → Advanced → Developer mode
Claude.ai Tenjin report_search_outcome Settings → Connectors → Add custom connector
LangChain Tenjin report_search_outcome pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http tenjin https://tenjin.sh/api/mcp

Other tools on this server

list_articles
search
resolve_keys
get_article
get_creator
list_tags
list_creators
get_trending
pay_and_read
answer
publish_essay
update_essay
get_my_post
delete_essay
list_my_posts
get_profile
update_profile
get_my_stats
get_my_events
upload_image
get_library
submit_feedback

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.

Tenjin MCP server