# obscura (remote · obscura.openmcp.logicsrc.com)

Stealth headless fetch (obscura.openmcp.logicsrc.com)

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `obscura.openmcp.logicsrc.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-profullstack-obscura/obscura.md), [page](https://verifymcp.io/servers/com-profullstack-obscura/obscura)

## Channel facts

- Endpoint: `https://obscura.openmcp.logicsrc.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 225 tokens (~225/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the obscura MCP server?

obscura is a hosted endpoint at https://obscura.openmcp.logicsrc.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-profullstack-obscura 'https://obscura.openmcp.logicsrc.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-profullstack-obscura": {
      "url": "https://obscura.openmcp.logicsrc.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-profullstack-obscura": {
      "type": "http",
      "url": "https://obscura.openmcp.logicsrc.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-profullstack-obscura]
url = "https://obscura.openmcp.logicsrc.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-profullstack-obscura": {
      "type": "remote",
      "url": "https://obscura.openmcp.logicsrc.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-profullstack-obscura --url 'https://obscura.openmcp.logicsrc.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-profullstack-obscura:
    url: "https://obscura.openmcp.logicsrc.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-profullstack-obscura": {
      "Transport": "http",
      "Url": "https://obscura.openmcp.logicsrc.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-profullstack-obscura -t streamable-http -u 'https://obscura.openmcp.logicsrc.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-profullstack-obscura": {
      "type": "http",
      "url": "https://obscura.openmcp.logicsrc.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 79, +33)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.23

### 2026-11-18 (score 46, −16)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-17 (score 62, −15)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-15 (score 77, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Authorization: pass → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-14 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 76, +72)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

## MCP tools (1)

### `fetch_page` (~193 tokens)

Fetch Web Page

Fetch a public web page through Obscura, a stealth headless browser that renders JavaScript and presents Chrome's TLS fingerprint, so pages that answer curl with 403 usually answer this. Returns the page as markdown (default), plain text, its links, the rendered HTML, or the original bytes. No credential needed.

Input parameters:

- `format` (string): markdown (default) for reading; text for a plain dump; links for every href; html for the rendered DOM (large); original for the raw response body, best for feeds and XML.
- `max_chars` (integer): Cut the answer to this many characters. Default 200000.
- `stealth` (boolean): Chrome 145 TLS fingerprint and tracker blocking. Default true.
- `timeout_seconds` (integer): Navigation timeout. Default 30, at most 60.
- `url` (string, required): The page, http or https, on a public host.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-profullstack-obscura/obscura#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 46
- 2026-11-17: 62
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 77
- 2026-11-13: 76
- 2026-11-12: 76
- 2026-11-11: 4

## Common questions

### What is the obscura MCP server?

obscura is an MCP server listed in the public MCP registry as com.profullstack/obscura. Stealth headless fetch (obscura.openmcp.logicsrc.com). This page covers its hosted endpoint (https://obscura.openmcp.logicsrc.com/mcp).

### Is the obscura MCP server safe to use?

obscura scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the obscura MCP server expose?

obscura exposes 1 tool: fetch_page. Their descriptions and schemas cost roughly 193 tokens of context every time the server is loaded.

### Does the obscura MCP server require authentication?

No. We connected to obscura without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the obscura MCP server still maintained?

obscura is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the obscura MCP server?

VerifyMCP ran 13 checks on obscura, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://obscura.openmcp.logicsrc.com/mcp
- Website: https://logicsrc.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-profullstack-obscura/obscura.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-profullstack-obscura/obscura/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-profullstack-obscura/obscura.json
- HTML version of this page: https://verifymcp.io/servers/com-profullstack-obscura/obscura
