Bring Satellite Imagery
to LangChain
Learn how to connect Upstream Lens to LangChain and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Upstream Lens MCP Server?
Connect your Upstream Tech Lens account to any AI agent and simplify how you monitor conservation projects, analyze satellite imagery, and track environmental changes through natural conversation.
What you can do
- Project & Portfolio Oversight — List all environmental projects and portfolios to manage your conservation assets.
- Imagery Analysis — Query available satellite imagery layers (Sentinel, Landsat, etc.) for specific property features.
- Geospatial Insights — Fetch detailed metadata and field observations for properties to track ground-truth data.
- Environmental Monitoring — List project notes and observations to keep a record of changes over time.
- Organization Management — Retrieve Lens organization profiles and verify account configurations.
- Operational Status — Check API health and connectivity to ensure your monitoring engine is always active.
How it works
1. Subscribe to this server
2. Enter your Upstream Tech Lens API Key (found in your account dashboard)
3. Start monitoring your environmental assets from Claude, Cursor, or any MCP client
Who is this for?
- Conservation Managers — quickly retrieve field notes and check satellite imagery availability via simple AI queries.
- Environmental Analysts — monitor changes in property features and verify geospatial metadata directly from the workspace.
- Sustainability Teams — track project observations and maintain an organized portfolio of environmental monitoring sites.
Built-in capabilities (8)
Check Lens API health
Get organization metadata
Get details for a specific property feature
List all portfolios
Can be filtered by update date. List observations and notes for a project
List detailed project observations
List all environmental projects
) for a specific property. List available imagery layers for a property
Why LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Upstream Lens through native MCP adapters. Connect 8 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Upstream Lens MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Upstream Lens queries for multi-turn workflows
Upstream Lens in LangChain
Upstream Lens and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Upstream Lens to LangChain through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Upstream Lens in LangChain
The Upstream Lens MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 8 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in LangChain only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Upstream Lens for LangChain
Every tool call from LangChain to the Upstream Lens MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I see if new satellite images are available for my project?
Yes! Use the list_property_imagery tool and provide the Property ID. Your agent will retrieve all available imagery layers (Sentinel, Landsat, etc.) with their respective capture dates.
How do I retrieve field notes for a specific conservation project?
Run the list_project_notes query with your Project ID. You can also provide an optional timestamp to filter only notes updated after a specific date.
Is it possible to see the geospatial metadata for a property feature?
Absolutely. Use the get_property_details tool with the Feature ID to retrieve detailed geospatial data and metadata for any monitored property.
How does LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters