rekor_entry — Sigstore Rekor MCP Tool
rekor_entry
(rekor entry) is one of 40 tools on the
Sigstore Rekor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call rekor_entry from your client
- Claude Code Sigstore Rekor rekor_entry run in your project directory
- Claude Desktop Sigstore Rekor rekor_entry ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Sigstore Rekor rekor_entry ~/.cursor/mcp.json
- VS Code Sigstore Rekor rekor_entry .vscode/mcp.json
- Zed Sigstore Rekor rekor_entry ~/.config/zed/settings.json
- Windsurf Sigstore Rekor rekor_entry ~/.codeium/windsurf/mcp_config.json
- Cline Sigstore Rekor rekor_entry ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Sigstore Rekor rekor_entry ~/.gemini/settings.json
- Grok Sigstore Rekor rekor_entry .mcp.json (in your project root)
- ChatGPT Sigstore Rekor rekor_entry Settings → Connectors → Advanced → Developer mode
- Claude.ai Sigstore Rekor rekor_entry Settings → Connectors → Add custom connector
- LangChain Sigstore Rekor rekor_entry pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http sigstore-rekor https://gateway.pipeworx.io/sigstore-rekor/mcpOther tools on this server
- ask_pipeworx
- ask_pipeworx_beta
- ask_pipeworx_grounded
- search_within
- deep_research
- discover_tools
- resolve_entity
- compare_entities
- subscribe
- unsubscribe
- list_subscriptions
- recent_alerts
- entity_profile
- recent_changes
- validate_claim
- company_facts
- scan_dependency
- bet_research
- polymarket_arbitrage
- polymarket_edges
- polymarket_kalshi_spread
- polymarket_fill_risk
- polymarket_edge_tracker
- kalshi_weather_edge
- resolution_audit
- resolution_diff
- release_calendar_markets
- pipeworx_trending
- suggest_questions
- generate_llms_txt
- ai_visibility_check
- scan_competitor_ai_presence
- pipeworx_feedback
- remember
- recall
- forget
- rekor_log_info
- rekor_entry_by_index
- rekor_search_by_hash
This list was read from the server itself, by connecting to it and calling tools/list on 25 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.