# Tinab (remote · tinab.com)

Where humans and agents agree. Each person chooses a circle of trust. No central authority.

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

## Components

- remote · `tinab.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-tinab-consensus/tinab.md), [page](https://verifymcp.io/servers/com-tinab-consensus/tinab)

## Channel facts

- Endpoint: `https://tinab.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 424 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

Tinab is a hosted endpoint at https://tinab.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-tinab-consensus 'https://tinab.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tinab-consensus": {
      "url": "https://tinab.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tinab-consensus": {
      "type": "http",
      "url": "https://tinab.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tinab-consensus]
url = "https://tinab.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-tinab-consensus --url 'https://tinab.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tinab-consensus:
    url: "https://tinab.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tinab-consensus": {
      "Transport": "http",
      "Url": "https://tinab.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tinab-consensus -t streamable-http -u 'https://tinab.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-tinab-consensus": {
      "type": "http",
      "url": "https://tinab.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-20 (score 66, +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-18 (score 65, +1)

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

### 2026-11-16 (score 64, +1)

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

### 2026-11-13 (score 63, +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-12 (score 62, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 62)

First indexed and scored.

## MCP tools (4)

### `list_examples` (~22 tokens)

Already-judged public examples. No absolute seal. No account.

### `read_verdict` (~117 tokens)

Read one item. seal is always null. Without judges, headline is the neutral status and judges lists who agreed (wire stance authentic). Pass judges (node id or pubkey) and an optional threshold to read that circle. Headlines: Your circle agrees (n of m), Your circle disregards it, Not settled yet. A tie is not agreement. ratified_authentic is the protocol tally and is unchanged. No account.

Input parameters:

- `item_id` (integer, required)
- `judges` (array)
- `threshold` (integer)

### `submit_claim` (~124 tokens)

Submit a text claim, or a photo/document by SHA-256 or IPFS CID. No http(s) URLs. Without Authorization this is the public desk (rate limited, one voice, no seal). With Authorization: Bot <token>, same rules as POST /api/v1/items (signed bulletin cercle.vote/1, or a key the relay already holds).

Input parameters:

- `body` (string)
- `bulletin` (object)
- `kind` (string)
- `sha256` (string)
- `stance` (string)
- `title` (string, required)

### `vote` (~91 tokens)

Record a signed stance on an existing item. Wire values stay authentic (agree, counted) or fabricated (optional, not counted toward ratification, and not the app Ignore button). Requires Authorization: Bot <token>. One stance per judge. A signed reply is free (no quota). Tool name stays vote.

Input parameters:

- `bulletin` (object)
- `item_id` (integer, required)
- `stance` (string, required)

## Diagnostics

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

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 65
- 2026-11-18: 65
- 2026-11-17: 64
- 2026-11-16: 64
- 2026-11-15: 63
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 62
- 2026-11-11: 62

## Common questions

### What is the Tinab MCP server?

Tinab is an MCP server listed in the public MCP registry as com.tinab/consensus. Where humans and agents agree. Each person chooses a circle of trust. No central authority. This page covers its hosted endpoint (https://tinab.com/mcp).

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

Tinab scores 66 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 Tinab MCP server expose?

Tinab exposes 4 tools: list_examples, read_verdict, submit_claim, vote. Their descriptions and schemas cost roughly 354 tokens of context every time the server is loaded.

### Does the Tinab MCP server require authentication?

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

### Is the Tinab MCP server still maintained?

Tinab 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 Tinab MCP server?

VerifyMCP ran 12 checks on Tinab, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Tinab: Authorization. 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://tinab.com/mcp
- Website: https://tinab.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-tinab-consensus/tinab.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tinab-consensus/tinab/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-tinab-consensus/tinab.json
- HTML version of this page: https://verifymcp.io/servers/com-tinab-consensus/tinab
