# Siglata (remote · www.siglata.com)

One MCP tool per operation over OAuth: read, search and query company files, then save edits.

- Trust score: 40/100 (low)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `www.siglata.com`: 40/100 (this document), [markdown](https://verifymcp.io/servers/com-siglata-mcp/v1-mcp.md), [page](https://verifymcp.io/servers/com-siglata-mcp/v1-mcp)

## Channel facts

- Endpoint: `https://www.siglata.com/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `3.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-10-02.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

Siglata is a hosted endpoint at https://www.siglata.com/v1/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-siglata-mcp 'https://www.siglata.com/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-siglata-mcp": {
      "url": "https://www.siglata.com/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-siglata-mcp": {
      "type": "http",
      "url": "https://www.siglata.com/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-siglata-mcp]
url = "https://www.siglata.com/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-siglata-mcp": {
      "type": "remote",
      "url": "https://www.siglata.com/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-siglata-mcp --url 'https://www.siglata.com/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-siglata-mcp:
    url: "https://www.siglata.com/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-siglata-mcp": {
      "Transport": "http",
      "Url": "https://www.siglata.com/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-siglata-mcp -t streamable-http -u 'https://www.siglata.com/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-siglata-mcp": {
      "type": "http",
      "url": "https://www.siglata.com/v1/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-09-28 (score 40, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 40, +1)

- [security improvement] Authorization: partial → pass

### 2026-09-25 (score 39, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 39, −1)

- [security regression] Authorization: pass → partial

### 2026-09-19 (score 40, +20)

- [security regression] Transport: fail → unverified
- [security improvement] Authorization: unverified → pass
- [security improvement] HTTPS: unverified → pass
- [security improvement] HSTS header: fail → pass
- [security] Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- [functional] Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

### 2026-09-18 (score 20, −14)

- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-09-16 (score 34, +2)

- [security improvement] DNSSEC: fail → pass

### 2026-09-13 (score 32)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-10-02: 40
- 2026-10-01: 40
- 2026-09-30: 40
- 2026-09-29: 40
- 2026-09-28: 40
- 2026-09-27: 40
- 2026-09-26: 39
- 2026-09-25: 39
- 2026-09-24: 39
- 2026-09-23: 40
- 2026-09-22: 40
- 2026-09-21: 40
- 2026-09-20: 40
- 2026-09-19: 40
- 2026-09-18: 20
- 2026-09-17: 34
- 2026-09-16: 34
- 2026-09-15: 32
- 2026-09-14: 32
- 2026-09-13: 32

## Common questions

### What is the Siglata MCP server?

Siglata is an MCP server listed in the public MCP registry as com.siglata/mcp. One MCP tool per operation over OAuth: read, search and query company files, then save edits. This page covers its hosted endpoint (https://www.siglata.com/v1/mcp).

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

Siglata scores 40 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.

### Does the Siglata MCP server require authentication?

Yes. Siglata asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Siglata MCP server still maintained?

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

## Links

- Remote endpoint: https://www.siglata.com/v1/mcp
- Website: https://www.siglata.com/docs/agents/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-siglata-mcp/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-siglata-mcp/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-siglata-mcp/v1-mcp