ocr_extract — SaSame MCP Observatory + Gold Rush Town MCP Tool
ocr_extract
(ocr extract) is one of 98 tools on the
SaSame MCP Observatory + Gold Rush Town
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ocr_extract from your client
- Claude Code SaSame MCP Observatory + Gold Rush Town ocr_extract run in your project directory
- Claude Desktop SaSame MCP Observatory + Gold Rush Town ocr_extract ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SaSame MCP Observatory + Gold Rush Town ocr_extract ~/.cursor/mcp.json
- VS Code SaSame MCP Observatory + Gold Rush Town ocr_extract .vscode/mcp.json
- Zed SaSame MCP Observatory + Gold Rush Town ocr_extract ~/.config/zed/settings.json
- Windsurf SaSame MCP Observatory + Gold Rush Town ocr_extract ~/.codeium/windsurf/mcp_config.json
- Cline SaSame MCP Observatory + Gold Rush Town ocr_extract ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SaSame MCP Observatory + Gold Rush Town ocr_extract ~/.gemini/settings.json
- Grok SaSame MCP Observatory + Gold Rush Town ocr_extract .mcp.json (in your project root)
- ChatGPT SaSame MCP Observatory + Gold Rush Town ocr_extract Settings → Connectors → Advanced → Developer mode
- Claude.ai SaSame MCP Observatory + Gold Rush Town ocr_extract Settings → Connectors → Add custom connector
- LangChain SaSame MCP Observatory + Gold Rush Town ocr_extract pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http research https://live-vps.sasame.online/public-mcpOther tools on this server
- start_here
- visit_touch_status
- get_mark_snippet
- factory_stations
- factory_start
- factory_checkout
- factory_status
- factory_station
- factory_station_action
- factory_health
- factory_verify_receipt
- factory_resolve_dead_letter
- factory_principal_register
- factory_membership_checkout
- factory_membership_status
- resolve_and_run
- knowledge_search
- knowledge_get
- get_standard
- audit_mcp
- verify_mcp_ready
- readiness_report
- verify_mcp_cert
- lookup_readiness
- claim_start
- claim_confirm
- provenance_passport_spec
- provenance_verify_passport
- trust_trajectory
- trust_movers
- trust_diff
- trust_compare
- capability_profile
- capability_landscape
- lookup_registry_entry
- lookup_passport
- analytics_public_summary
- pricing_overview
- market_context_summary
- chronicle_summary
- gold_vein_public
- monitoring_receipts_public
- analytics_public_export
- analytics_next_steps
- gold_rush_start
- gold_rush_package_status
- gold_rush_agent_run
- gold_rush_report
- pubmed_lookup
- ecosystem_search
- engage_sasame
- information_paid_access_listings
- get_pricing
- guild_feed
- join_guild
- chain_list
- research_corroborate
- pubmed_evidence
- market_snapshot
- onchain_read_verified
- register_intent
- demand_radar
- meter_open
- meter_charge
- meter_status
- receipt_issue
- audit_query
- trust_pubkey
- escrow_open
- escrow_attest
- escrow_status
- work_order_open
- work_order_accept
- work_order_deliver
- work_order_accept_delivery
- agent_invoice_issue
- agent_invoice_attest_settlement
- agent_invoice_status
- receipt_status_set
- receipt_state
- usage_mark_issue
- usage_mark_status
- usage_mark_verify
- usage_mark_status_set
- usage_mark_visibility_scan
- get_usage_badge
- get_mcp_mark_snippet
- recommend_mcp
- refer
- check_engagement
- reply_engagement
- town_overview
- town_claim_start
- town_claim_confirm
- town_become_citizen
- subscribe_grade_changes
- get_badge
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.