Developers / MCP Connector · OSINT Risk & Supply Chain

svEye MCP Connector

Connect Claude to svEye's OSINT intelligence: risk and opportunity events, narrative summaries, and supply chain mapping for companies, legal entities, locations, commodities, and industries — all sourced from continuously crawled open news content, refreshed on an hourly cadence.

Create a service accountFull API reference
✦
Ask Claude about this page
→
Copies a ready-made prompt · opens a new Claude chat
ILLUSTRATIVE SESSION · CLAUDE + SVEYE
CONNECTED · HOURLY REFRESH
PROMPT
Map the supply chain of Rheinmetall three tiers deep and flag any suppliers with recent sanctions or financial distress events.
TOOLS CALLED
search_brands
get_supply_chain
search_events
· 3 tiers · 84 suppliers
WHAT CAME BACK
›
Tier 1 returns 11 direct suppliers; 84 entities across all three tiers.
›
Two carry recent sanctions-related events — a Turkish component maker and a logistics provider in tier 2.
›
One tier-3 casting supplier shows financial distress signals in the last 60 days.
EVIDENCE · GROUNDED
reuters.com · 22 Jul
handelsblatt.com · 19 Jul
sanctions list · ref
+ 14 sources
DECISION ENABLED
Add flagged suppliers to watchlist → escalate for review

Illustrative session — svEye surfaces and ranks candidates with linked sources; it does not make final determinations.

Capabilities

What you can do with it

Risk

Investigate risk for a specific company or supplier

Sanctions exposure, legal trouble, financial distress, ESG violations, geopolitical exposure, cyber incidents, supply chain disruption, health and safety issues.

Opportunity

Track growth and opportunity signals

Financial performance, market expansion, innovation, ESG opportunity — not just downside risk.

Briefing

Summarize recent developments for an entity

“Summarize key supply disruption events for TSMC in Q1 2026.”

Monitoring

Monitor a watchlist

“What new high-severity events have come in since yesterday for my watchlist?”

Network

Map exposure through a supply chain

“What recent events involve [prospect’s key suppliers]?”

Events and summaries are organized under five top-level impact types — each broken into finer event categories and event types.

IMPACT TYPE 01
Business Risk
IMPACT TYPE 02
Business Growth
IMPACT TYPE 03
Business Change
IMPACT TYPE 04
Governments
IMPACT TYPE 05
World
NOT A NEWS SEARCH ENGINE

This is not a general-purpose news search engine. It isn’t built for open-ended volume questions like “how many articles mention X in the last 3 months.” It’s built for entity-centered event and risk monitoring, with sourcing you can verify.

Example prompts

Ask it like you would ask an analyst

01
What high-severity risk events involve Foxconn in the last 30 days?
✦
Open in Claude
02
Map the supply chain of Rheinmetall three tiers deep and flag any suppliers with recent sanctions or financial distress events.
✦
Open in Claude
03
Summarize ESG-related developments for my top 10 suppliers this quarter.
✦
Open in Claude
04
Which of my watchlist companies had new cyber incident events since Friday?
✦
Open in Claude
05
What events are affecting lithium as a commodity this month, and which companies are mentioned alongside them?
✦
Open in Claude
ⓘ

These prompts query your own svEye data, so they need the connector connected first. Without it, Claude will say it has no matching tool.

Data model

What data it returns

Primary unit

Summaries

An LLM-generated narrative synthesis built from a cluster of underlying articles about an entity, including a sentiment label and any other entities mentioned alongside it. This is the primary, highest-level intelligence unit.

Event unit

Events

A discrete, timestamped occurrence involving a specific entity, derived from one or more source articles and classified against a three-level taxonomy (impact type → event category → event type), with an intensity score reflecting how strongly the signal is corroborated.

Relationship unit

Supply chain edges

For a given company or legal entity, the OSINT-derived suppliers feeding into it, up to three tiers deep, each with a relationship type (e.g. component, service) and the source evidence it was inferred from.

Both Events and Summaries link back to their source articles. Coverage spans 12 languages:
Arabic
Chinese
Czech
English
French
German
Italian
Japanese
Korean
Portuguese
Russian
Spanish
Entity types supported

Five entity types you can monitor

Type
Notes
Companies / Brands
Commercial tradestyle names
Legal Entities
Registered legal entities, holding companies, subsidiaries
Locations
City/region-level granularity, not just country
Commodities
234 tracked
— agricultural goods, metals, energy, rare earths, and select cryptocurrencies
Industries
27 sector categories
(e.g. Technology, Automotive, Financial Services, Energy)
Tools

Eleven tools Claude can call

Tool
Purpose
list_entity_types
List the entity types that can be monitored. Start here.
list_languages
List supported content languages for filtering events and summaries.
get_taxonomy
Explore the event taxonomy for an entity type — impact types, event categories, event types, or the full hierarchy in one call.
list_industries
List all industries with IDs and names, for use as entity_ids in search.
list_commodities
List all commodities with IDs and names, for use as entity_ids in search.
list_locations
Paginated list of locations; filter by name prefix.
search_legal_entities
Search legal entities by name prefix.
search_brands
Search companies/brands by name prefix.
search_events
Search Events within a date range, filtered by entity and/or taxonomy.
search_summaries
Search Summaries within a date range, filtered by entity and/or taxonomy.
get_supply_chain
Return the OSINT-derived supply chain (suppliers) for a company or legal entity, up to 3 tiers deep.
Full parameter-level detail for every call is documented at
api.semantic-visions.com/docs
Getting access

Six steps to a live connection

Connecting Claude to svEye requires a service account, created from your svEye account. This is separate from your personal login — it’s a dedicated credential pair scoped to the API calls the MCP connector uses.

STEP 01
Register at sveye.semantic-visions.com.
STEP 02
Verify your account via the confirmation email, then sign in and open your account menu.
STEP 03
In the API tab, create a service account.
This account is granted access to the specific API calls the MCP connector relies on.
STEP 04
Your service account credentials are shown once.
Save them immediately to a password manager — they can’t be retrieved again after you leave the page.
STEP 05
When you add the svEye connector in Claude, you’ll be prompted for these credentials during authentication.
Enter them there.
STEP 06
Once connected, monitor your MCP usage against your plan limits.
From the same API tab where you created the service account.

If you lose your credentials, generate a new service account from the same tab rather than trying to recover the old one.

Data scope and limitations

What this data is — and isn’t

OSINT-derived coverage

Absence of an event does not confirm absence of an underlying real-world occurrence.

A monitoring feed, not an archive

Data updates on an hourly cadence — this is not a historical records database.

Research, not advice

Intended for risk monitoring and due-diligence research, not as a substitute for legal, financial, or compliance advice.

Ready to connect?

Add svEye to Claude in about five minutes.

Create your service account, add the connector, and start asking. Prefer the REST API? The same intelligence layer is available over HTTP.

Create a service accountPrefer the REST API?
sveye.semantic-visions.com