# Tier 1 Protocol (remote · mcp.tier1protocol.app)

Search files while they stay encrypted: the problem DARPA chased for a decade. Exact quotes back.

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

## Components

- remote · `mcp.tier1protocol.app`: 84/100 (this document), [markdown](https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp.md), [page](https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp)

## Channel facts

- Endpoint: `https://mcp.tier1protocol.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## 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**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - 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 offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1525 tokens (~217/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Tier 1 Protocol MCP server?

Tier 1 Protocol is a hosted endpoint at https://mcp.tier1protocol.app/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 app-tier1protocol-mcp-tier-1-protocol 'https://mcp.tier1protocol.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-tier1protocol-mcp-tier-1-protocol": {
      "url": "https://mcp.tier1protocol.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-tier1protocol-mcp-tier-1-protocol": {
      "type": "http",
      "url": "https://mcp.tier1protocol.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-tier1protocol-mcp-tier-1-protocol]
url = "https://mcp.tier1protocol.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-tier1protocol-mcp-tier-1-protocol": {
      "type": "remote",
      "url": "https://mcp.tier1protocol.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-tier1protocol-mcp-tier-1-protocol --url 'https://mcp.tier1protocol.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-tier1protocol-mcp-tier-1-protocol:
    url: "https://mcp.tier1protocol.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-tier1protocol-mcp-tier-1-protocol": {
      "Transport": "http",
      "Url": "https://mcp.tier1protocol.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-tier1protocol-mcp-tier-1-protocol -t streamable-http -u 'https://mcp.tier1protocol.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-tier1protocol-mcp-tier-1-protocol": {
      "type": "http",
      "url": "https://mcp.tier1protocol.app/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 84, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-20 (score 83, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-19 (score 83, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-18 (score 82, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-17 (score 82, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-16 (score 81, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

- [functional regression] Schema quality: 1321 → 1525
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (7)

### `search` (~226 tokens)

Route Tier 1 context

Retrying the same public search with the same MCP request identity replays the same bounded operation. Paid context routing for useful work. Route a question across policy-eligible Tier 1 context available to the account, including private, shared, licensed, or public catalogs when present. Returns up to ten verified excerpts, exact source coordinates, signed result ids, and reference URLs. Broad questions may need focused follow-up searches; absence from one result set does not establish absence from the corpus. Authentication and an active paid plan are required. This is not an unrestricted web crawler and cannot change files.

Input parameters:

- `profile` (string): Optional keyed profile for this search, derived locally by the agent from the account key (profile_from_key_hex) and sent per request. The profile is key-equivalent: it is never stored or logged — on…
- `query` (string, required): The natural-language question to route across policy-eligible Tier 1 context. Eligible context may include private, shared, licensed, or public catalogs available to the paid account.

Output parameters:

- `receipt` (object)
- `results` (array)

### `authorize_sources` (~209 tokens)

Authorize sources for Tier 1

Add selected private ChatGPT files to the paid account's Tier 1 context. Show the filenames and fixed 30-day retention and require explicit confirmation before calling. This upload consent applies to private file intake only; it does not define or narrow the other policy-eligible catalogs Tier 1 may route. Authentication and an active paid plan are required.

Input parameters:

- `authorization_confirmed` (boolean, required): Must be true only after the user explicitly confirms that Tier 1 may retain and route these files for 30 days.
- `files` (array, required): Files the signed-in user selected in ChatGPT for Tier 1 to route.
- `profile` (string): Optional keyed profile these files bind under, derived locally by the agent from the account key (profile_from_key_hex) and sent per request. The profile is key-equivalent: it is never stored or logg…
- `retention_days` (number, required): The fixed retention period for this authorization.

Output parameters:

- `authorized` (boolean)
- `expiresAt` (string)
- `files` (array)
- `replayed` (boolean)
- `totalBytes` (integer)

### `fetch` (~84 tokens)

Fetch exact Tier 1 span

Paid exact-span retrieval after Tier 1 search. Accept only an unchanged id returned by search for the same account. Authentication and an active paid plan are required. Do not invent ids, browse nearby text, or change files.

Input parameters:

- `id` (string, required): An exact result id returned by a successful Tier 1 search for the same signed-in account. Never invent or alter this id.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

### `render_context_results` (~101 tokens)

Inspect Tier 1 source coordinates

Inspect one to six exact coordinates returned by paid Tier 1 search. Pass only unchanged result ids. Tier 1 rehydrates and revalidates each id for the same account; caller-supplied titles, excerpts, URLs, and coordinates are rejected. Authentication and an active paid plan are required.

Input parameters:

- `ids` (array, required): One to six exact result ids returned by Tier 1 search for this signed-in account. Never pass caller-authored result objects.

Output parameters:

- `receipt` (object)
- `results` (array)

### `index` (~396 tokens)

Index a file into the user's Tier 1 library

Index one file into the user's own Tier 1 library, one batch at a time. Pass the file's text as the chatbot read it, with its SHA-256 as the idempotency key — re-indexing the same bytes is a no-op. One call carries at most 64 KiB of text; larger files are split and indexed in successive calls. This is the conversational drip path: it builds the index file by file as the user works. It cannot bootstrap a large existing library — for a library, use the browser indexer page or Local. Authentication and an active paid plan are required. The user's keyed profile (derived locally, sent per request) is also required.

Input parameters:

- `content` (string, required): The file's text, inline, as the chatbot read it. One batch carries at most 64 KiB of text (the current batch budget) — larger files are split and indexed in successive calls. This is the conversation…
- `content_hash` (string, required): SHA-256 of the source bytes, computed by the caller. This is the idempotency key: re-indexing the same bytes is a no-op and returns the existing result.
- `profile` (string, required): The user's keyed profile, derived locally by the agent from the account key (profile_from_key_hex) and sent per request. The profile is key-equivalent: it is never stored or logged — only its fingerp…
- `source_label` (string): What the user calls this material ("my research paper," "the harbor project") — the human handle, stored with the manifest.
- `source_name` (string, required): The file's name as the user knows it (e.g. harbor-renovation-notes.md).

Output parameters:

- `calls_remaining_today`
- `ingested` (integer)
- `manifest_fingerprint` (string)
- `protocol` (string)
- `quota_remaining`
- `replayed` (boolean)
- `source_name` (string)

### `index_status` (~96 tokens)

Check the user's Tier 1 index status

How much of the user's library is indexed, and whether the index is still growing. Returns the sources indexed, the batches still pending, and the index fingerprint. Poll this after indexing, never the index directly. Authentication and an active paid plan are required. The user's keyed profile (derived locally, sent per request) is also required.

Input parameters:

- `profile` (string, required): The user's keyed profile, sent per request. Only its fingerprint travels onward.

Output parameters:

- `calls_remaining_today`
- `last_indexed_at`
- `manifest_fingerprint` (string)
- `pending_batches` (integer)
- `protocol` (string)
- `quota_remaining`
- `sources_indexed` (integer)

### `index_upload_token` (~204 tokens)

Mint a Tier 1 browser-index upload token

Mint a short-lived upload token so the user can upload a browser-built index to their Tier 1 library. The token is valid 15 minutes for any number of sources under this principal and profile. The response includes the token AND the principal_id: hand the user BOTH to paste into the indexer page (token field + principal field) — the page never collects a principal_id on its own, and the library compares the token's principal to the upload body's principal_id. The token travels in the x-tier1-upload-token header. Authentication and an active paid plan are required. The user's keyed profile (derived locally, sent per request) is also required — only its fingerprint is bound into the token.

Input parameters:

- `profile` (string, required): The user's keyed profile, derived locally by the agent from the account key (profile_from_key_hex) and sent per request. Only its fingerprint travels onward — it is bound into the token, and the LIBR…

Output parameters:

- `exp` (integer): Unix expiry (seconds) of the token.
- `expires_at` (string): ISO-8601 expiry of the token.
- `principal_id` (string): The authenticated principal_id. Paste it into the indexer page's principal field alongside the token — the page never collects it on its own, and the LIBRARY compares it to the upload body's principa…
- `profile_fingerprint` (string): SHA-256 of the profile, bound into the token and recorded by the LIBRARY on first write.
- `protocol` (string)
- `token` (string): The upload token. Paste it into the indexer page's upload-token field; it travels in the x-tier1-upload-token header. Valid 15 minutes for any number of sources under this principal and profile.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 81
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 79
- 2026-11-10: 81

## Common questions

### What is the Tier 1 Protocol MCP server?

Tier 1 Protocol is an MCP server listed in the public MCP registry as app.tier1protocol.mcp/tier-1-protocol. Search files while they stay encrypted: the problem DARPA chased for a decade. Exact quotes back. This page covers its hosted endpoint (https://mcp.tier1protocol.app/mcp).

### Is the Tier 1 Protocol MCP server safe to use?

Tier 1 Protocol scores 84 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 Tier 1 Protocol MCP server expose?

Tier 1 Protocol exposes 7 tools: search, authorize_sources, fetch, render_context_results, index, and 2 more. Their descriptions and schemas cost roughly 1,316 tokens of context every time the server is loaded.

### Does the Tier 1 Protocol MCP server require authentication?

Yes. Tier 1 Protocol 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 Tier 1 Protocol MCP server still maintained?

Tier 1 Protocol 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 Tier 1 Protocol MCP server?

VerifyMCP ran 14 checks on Tier 1 Protocol, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://mcp.tier1protocol.app/mcp
- Repository: https://github.com/Tier-1-Protocol/tier1-protocol-connector
- Website: https://tier1protocol.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-tier1protocol-mcp-tier-1-protocol/mcp
