World Monitor
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
MCP server for SecObserve: triage findings, import scan reports and SBOMs, generate VEX.
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 13/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install Secobserve MCP. Follow https://mcp.popnx.com/i/nh4ttruong-secobserve-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 14, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
You need a Secobserve MCP key (create it on the maker’s site) · 1 setting(s) to fill in (SECOBSERVE_BASE_URL) · Install Python (uv) on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Secobserve MCP for Claude on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "secobserve": { "command": "uvx", "args": [ "secobserve-mcp" ], "env": { "SECOBSERVE_BASE_URL": "your-value", "SECOBSERVE_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Secobserve MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SECOBSERVE_BASE_URL SecObserve base URL without /api, e.g. https://secobserve.example.comDescriptions are as written by the maker.
SettingsDeveloperEdit Config
{
"mcpServers": {
"secobserve": {
"command": "uvx",
"args": [
"secobserve-mcp"
],
"env": {
"SECOBSERVE_BASE_URL": "your-value",
"SECOBSERVE_API_TOKEN": "your-value"
}
}
}
}Paste the key only into the app’s field, never into a chat or to anyone
Use Secobserve MCP and tell me what you can do for me, then show me one thing✓ If Claude says it is using Secobserve MCP or shows a Secobserve MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SECOBSERVE_READ_ONLY Set to true to refuse every write operationSECOBSERVE_ALLOW_DELETE Set to true to enable the delete tool; deletion cascades and is irreversibleDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Secobserve MCP yet
Secobserve MCP runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect Secobserve MCP
B · Others in Other that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
You need a Secobserve MCP key (create it on the maker’s site) · 1 setting(s) to fill in (SECOBSERVE_BASE_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Secobserve MCP for Claude Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user secobserve --env SECOBSERVE_BASE_URL=your-value --env SECOBSERVE_API_TOKEN=your-value -- uvx secobserve-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Secobserve MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SECOBSERVE_BASE_URL SecObserve base URL without /api, e.g. https://secobserve.example.comDescriptions are as written by the maker.
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user secobserve --env SECOBSERVE_BASE_URL=your-value --env SECOBSERVE_API_TOKEN=your-value -- uvx secobserve-mcpReplace “your-value” with your key before pressing Enter
Paste the key only into the app’s field, never into a chat or to anyone
You should see Secobserve MCP listed as connected
Use Secobserve MCP and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using Secobserve MCP or shows a Secobserve MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SECOBSERVE_READ_ONLY Set to true to refuse every write operationSECOBSERVE_ALLOW_DELETE Set to true to enable the delete tool; deletion cascades and is irreversibleDescriptions are as written by the maker.
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
You need a Secobserve MCP key (create it on the maker’s site) · 1 setting(s) to fill in (SECOBSERVE_BASE_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Secobserve MCP for Cursor on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "secobserve": { "command": "uvx", "args": [ "secobserve-mcp" ], "env": { "SECOBSERVE_BASE_URL": "your-value", "SECOBSERVE_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Secobserve MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SECOBSERVE_BASE_URL SecObserve base URL without /api, e.g. https://secobserve.example.comDescriptions are as written by the maker.
In the Secobserve MCP settings, SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Secobserve MCP and tell me what you can do for me, then show me one thing✓ If Cursor says it is using Secobserve MCP or shows a Secobserve MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SECOBSERVE_READ_ONLY Set to true to refuse every write operationSECOBSERVE_ALLOW_DELETE Set to true to enable the delete tool; deletion cascades and is irreversibleDescriptions are as written by the maker.
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
You need a Secobserve MCP key (create it on the maker’s site) · 1 setting(s) to fill in (SECOBSERVE_BASE_URL) · Install Python (uv) on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server Secobserve MCP for VS Code on this computer, in this order: 1) Check uv with uv --version. If it is missing, tell me to install it from https://docs.astral.sh/uv/getting-started/installation/; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "secobserve": { "type": "stdio", "command": "uvx", "args": [ "secobserve-mcp" ], "env": { "SECOBSERVE_BASE_URL": "your-value", "SECOBSERVE_API_TOKEN": "your-value" } } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) For SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL, leave "your-value" in place and tell me to paste the real value myself into the file or the app’s field. Never ask me to type a key in chat. 5) Do what we agreed, then check that the Secobserve MCP tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
uv --versionMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: uv has no click-through installer. Copy the one-line command for your system (macOS or Windows) from uv’s official page into Terminal · no separate Python install needed; uv downloads it when required
When it’s done, close Terminal, open it again and run the same command. You should see a version number: uv --version
Install once; it works for everything that needs uv
Open the maker’s site, sign up and create an API key for the next step. Check the maker’s site for pricing and free plans.
How to get a key is in the maker’s README below
These are program settings, not keys. No sign-up needed; fill them in as the maker describes.
SECOBSERVE_BASE_URL SecObserve base URL without /api, e.g. https://secobserve.example.comDescriptions are as written by the maker.
In the Secobserve MCP settings, SECOBSERVE_API_TOKEN, SECOBSERVE_BASE_URL is empty; add your key and save
Paste the key only into the app’s field, never into a chat or to anyone
Use Secobserve MCP and tell me what you can do for me, then show me one thing✓ If VS Code says it is using Secobserve MCP or shows a Secobserve MCP tool in the answer, you are connected
The command above works without these. Add them only if you want to change something, following the maker’s description.
SECOBSERVE_READ_ONLY Set to true to refuse every write operationSECOBSERVE_ALLOW_DELETE Set to true to enable the delete tool; deletion cascades and is irreversibleDescriptions are as written by the maker.
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.
JSON settings are under “For developers” below
Claude Code
claude mcp add --scope user secobserve --env SECOBSERVE_BASE_URL=your-value --env SECOBSERVE_API_TOKEN=your-value -- uvx secobserve-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"secobserve": {
"command": "uvx",
"args": [
"secobserve-mcp"
],
"env": {
"SECOBSERVE_BASE_URL": "your-value",
"SECOBSERVE_API_TOKEN": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"secobserve": {
"command": "uvx",
"args": [
"secobserve-mcp"
],
"env": {
"SECOBSERVE_BASE_URL": "your-value",
"SECOBSERVE_API_TOKEN": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"secobserve": {
"type": "stdio",
"command": "uvx",
"args": [
"secobserve-mcp"
],
"env": {
"SECOBSERVE_BASE_URL": "your-value",
"SECOBSERVE_API_TOKEN": "your-value"
}
}
}
}SECOBSERVE_BASE_URL required envSECOBSERVE_API_TOKEN secret required envSECOBSERVE_READ_ONLY envSECOBSERVE_ALLOW_DELETE envDescriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
The registry name was verified with the GitHub account nh4ttruong, which owns the repo
Code last changed 2 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for secobserve-mcp@1.0.0
Checks only this package version, not every dependency · checked Nov 15, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/nh4ttruong-secobserve-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: SECOBSERVE_API_TOKEN
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 months ago, and the latest version (1.0.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.
In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.
Manage monitors, status pages, incidents and maintenances in your openstatus workspace.
Validate oh-my-posh configurations and segment snippets against the official schema.
MCP server for progressive tool usage at any scale (see https://klavis.ai)
Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.
| This one Secobserve MCP | World Monitor | openstatus | Oh My Posh Validator | Strata | Jitsu | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 1/4 | 4/4 |
| License | MIT | AGPL-3.0 | AGPL-3.0 | MIT | Apache-2.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
*MCP server for SecObserve — Triage, import and administration from an agent*
Tools • Install • Configure • Register with a client • Design
secobserve-mcp exposes the SecObserve REST API to an LLM agent over the Model Context Protocol: browse and triage observations, manage products, branches and rules, import scan reports and SBOMs, run scans and background jobs, generate VEX documents. Transport is stdio by default. Listed in the official MCP Registry as io.github.nh4ttruong/secobserve-mcp.
18 tools, not one per endpoint. SecObserve has ~50 REST resources and ~40 named actions; registering a tool for each would cost more context than the data ever returns, so the API is modelled as data and the tools are the interface to it.
| Tool | Purpose |
|---|---|
secobserve_list_resources | The catalogue: every resource, its verbs, its actions. Makes no API call, so it is free to call first. |
secobserve_describe_resource | Exact filters, fields and enums, read from the running instance's OpenAPI schema. |
secobserve_list / _get | Read, with filters, sorting, pagination and projection. |
secobserve_create / _update / _delete | CRUD over any resource in the catalogue. |
secobserve_call_action | The long tail: apply_rules, copy, simulate, license_overview, exports. |
secobserve_assess_observation | Triage one finding. Writes an observation log, honours the approval workflow. |
secobserve_bulk_assess_observations | The same assessment across up to 250 findings. |
secobserve_approve_observation_log | Approve or reject pending assessments (four-eyes). |
secobserve_product_metrics | Pre-aggregated counts: current, timeline, the delta between two dates, and how stale they are. |
secobserve_upload_file | Import a scan report, SBOM or VEX document from disk. |
secobserve_api_import | Pull findings through a stored API configuration. Blocks; a timeout reports the work as still running and where to watch it land. |
secobserve_trigger_scan | Run SecObserve's built-in OSV or VulnerableCode scan. Same blocking behaviour. |
secobserve_run_periodic_task | Trigger a background job, or list the registered ones. |
secobserve_status | Version, health, public settings, queue statistics, PURL types. |
secobserve_vex_document | Generate or revise a CSAF / OpenVEX / CycloneDX document. |
Six prompts, for the work that is a sequence of calls rather than one. A prompt is fetched by name when someone picks it, so it costs nothing per session — unlike a tool schema, which is sent on every connection.
| Prompt | Purpose |
|---|---|
triage-product | Work one product's open findings, highest severity and fix_available first, assessing each with evidence. |
daily-changes | What changed since local midnight: new, parser-changed, resolved, human-assessed. |
weekly-changes | The same feed over the past 7 days, broken down by day. |
daily-report | Today's counts per product, what moved today, what is still open. |
weekly-report | The same three parts over the past 7 days, for the report someone sends on. |
monthly-report | A month's closing numbers and the month-over-month delta. |
Each one carries the caveats that decide whether the report is right: metrics cover the default branch only and answer 200 with every count at zero when the job has not run, no filter expresses a calendar month, and nothing in SecObserve is a due date or an SLA.
uvx secobserve-mcp --help
uvx downloads and runs it without installing anything permanently. In VS Code: one-click install.
To put it on your PATH instead:
uv tool install secobserve-mcp
Once you have done that, uv tool owns the name: a bare uvx secobserve-mcp runs that pinned copy forever and never notices a newer release, so keep it current with uv tool upgrade secobserve-mcp. The client configurations below therefore say uvx secobserve-mcp@latest, which revalidates against PyPI on each launch — once per client session, not once per command. --check deliberately stays on the bare name, because its job is to report on the copy your clients are actually running.
From a checkout, for development:
uv venv && uv pip install -e ".[dev]"
| Variable | Default | Notes |
|---|---|---|
SECOBSERVE_BASE_URL | http://localhost:8000 | Base URL without /api. |
SECOBSERVE_API_TOKEN | — | User or product API token. Recommended. |
SECOBSERVE_JWT | — | Alternative to an API token. |
SECOBSERVE_TIMEOUT | 60 | Seconds. SecObserve imports and scans inside the request, and a timeout does not cancel one; raise it to get the counts back from the call itself. |
SECOBSERVE_VERIFY_SSL | true | Set false only for a self-signed dev certificate. |
SECOBSERVE_READ_ONLY | false | true refuses every non-GET call. |
SECOBSERVE_ALLOW_DELETE | false | secobserve_delete is off until this is set. |
SECOBSERVE_IMPORT_DIR | working directory | Uploads may only be read from this tree. |
SECOBSERVE_EXPORT_DIR | ./secobserve-exports | Exports and VEX documents are written here. |
SECOBSERVE_AUDIT_LOG | true | One JSON line per tool call on stderr. false switches it off. |
Create a user API token:
curl -X POST "$SECOBSERVE_BASE_URL/api/authentication/create_user_api_token/" \
-H "Content-Type: application/json" \ -d '{"username": "you", "password": "...", "name": "mcp"}'
Check the wiring before handing it to a client:
uvx secobserve-mcp --check
It prints the instance version, the authenticated user, whether read-only and delete are enabled, and how this install compares to the newest release on PyPI. That last part is the only place this server calls pypi.org, it needs one short-lived request, and it degrades to a single line when the index is unreachable.
docker run --rm -p 8931:8931 \
-e SECOBSERVE_BASE_URL=https://secobserve.example.com \ -e SECOBSERVE_API_TOKEN=... \ ghcr.io/nh4ttruong/secobserve-mcp \ --transport http --host 0.0.0.0 --shared-identity
The image is built for linux/amd64 and linux/arm64, runs as a non-root user, and answers GET /healthz with its version. /healthz is liveness only and never calls SecObserve, so a backend outage does not get this server restarted.
--shared-identity is required and not in the image's default command: the token is baked into the environment, so every caller of the port acts as that one SecObserve identity, and the server refuses to start over HTTP until someone says that is intended. It then refuses every write, because an assessment made under a shared token records the wrong actor in the observation log and in four-eyes approval. Arguments to docker run replace CMD rather than extend it, which is why the transport flags are repeated above.
Keep it behind a gateway that authenticates the caller, and off any public port. For a single user, uvx over stdio is the better fit: one process, one token, writes included.
The server prints its own registration snippet, so none of the blocks below have to be copied by hand:
uvx secobserve-mcp --print-config claude # or: codex, vscode, json
It reads SECOBSERVE_BASE_URL from the environment and always leaves the token as a placeholder — the snippet is meant to be pasted somewhere, and a token should not travel with it. The hint goes to stderr, so --print-config json > mcp.json writes a clean file.
claude mcp add secobserve --env SECOBSERVE_BASE_URL=http://localhost:8000 --env SECOBSERVE_API_TOKEN=... -- uvx secobserve-mcp@latest
In ~/.codex/config.toml:
[mcp_servers.secobserve]
command = "uvx" args = ["secobserve-mcp@latest"] env = { SECOBSERVE_BASE_URL = "http://localhost:8000", SECOBSERVE_API_TOKEN = "..." }
Most clients take the same JSON shape:
{
"mcpServers": { "secobserve": { "command": "uvx", "args": ["secobserve-mcp@latest"], "env": { "SECOBSERVE_BASE_URL": "http://localhost:8000", "SECOBSERVE_API_TOKEN": "..." } } } }
For a shared deployment, run streamable HTTP with stateless JSON behind a gateway that authenticates the caller:
uvx secobserve-mcp --transport http --host 127.0.0.1 --port 8931 --shared-identity
--shared-identity is what makes this start: the transport has no authentication of its own, so every caller acts as the one identity in SECOBSERVE_API_TOKEN, and the flag accepts that and forces read-only for the process.
Three decisions worth knowing before reading the code:
Responses are projected. SecObserve's serializers return every model column; an Observation has around 100. Each resource carries a default field set, and every list result says what it dropped. Pass fields=["*"] to opt out.
Resource help comes from the instance, not from this repo. secobserve_describe_resource reads /api/oa3/schema/ on the running backend, so filter names and enums cannot drift from the deployed version. The same schema is used to reject unknown filter names before a request is sent: django-filter silently ignores parameters it does not recognise, so filters={"vulnerability_id": "CVE-2021-44228"} would otherwise return the *entire* unfiltered list and the agent would report a confident wrong answer. It now fails with the list of filters that do exist.
Validation lives in the schema wherever a rule exists. An assessment with no comment, a rejection with no remark, a bulk call over 250 ids, or a create with neither product_id nor product_name is refused by the input model before any HTTP request. Everything else is passed through, and the API's 400 body — which names the offending field — is returned verbatim.
Expected failures come back as tool *text*, not as a raised exception: MCP reports a raised exception to the client as a bare Error executing tool , which would throw away exactly the guidance the agent needs to retry correctly.
Every tool call writes one JSON line to stderr. SecObserve's own observation log records writes only, so without this a read — which is how data leaves — leaves no trace anywhere.
{"ts":"2026-09-20T19:01:06.474+00:00","tool":"secobserve_list","caller":"apitoken:82fd9d5b1ae9","claimed_username":null,"resource":"observations","outcome":"returned","ms":37.0}
{"ts":"2026-09-20T19:01:06.518+00:00","tool":"secobserve_list","caller":"jwt:09f002a0