mcpField
T
Tier 1 Protocol

Tier 1 Protocol

Remote
tier1protocol.networkSearch0Updated 2d ago

About Tier 1 Protocol

Tier 1 Protocol is a document-search connector for Bolt, intended for users who need verifiable retrieval. Documents are split and sealed with SHA-256 on the user's machine; fetched records are checked again against their seal.

Key features

  1. 01Search documents by record
  2. 02Fetch records by address
  3. 03Reverify seals on every fetch
  4. 04List authorized search sources
  5. 05Render results as context

Use cases

  1. 01Search document records in Bolt
  2. 02Verify passages cited by an agent
  3. 03Check whether retrieved records validate

MCP support

It exposes source authorization, search, record retrieval, and context-rendering tools through an MCP server. The connector uses HTTP transport and MCP OAuth.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.tier1protocol.app/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

Tier 1 Protocol — Connector for Bolt

Tier 1 Protocol is a library your AI searches instead of guessing from. Documents are cut into records, each one sealed with SHA-256 at its exact byte address, and served through a single MCP door: your agent asks, the door returns the exact passages — and the proof recomputes on every fetch.

Add it to Bolt (about a minute)

  1. From the Bolt homepage, click the + by the chat box → Connectors → Manage connectors → Custom MCP server.
  2. Fill in exactly:
    • Name: Tier 1 Protocol
    • URL: https://mcp.tier1protocol.app/mcp
    • Transport: HTTP
    • Authentication: MCP OAuth
  3. Click Connect and sign in with your Tier 1 account.
  4. Back in your project, toggle Tier 1 Protocol on.
  5. Ask your agent: "Using Tier 1, search the starter library: what happened in this account between 23:41 and 00:19?"

The agent should answer from the sealed records and cite record addresses. One record in the starter library — ticket-0007 — fails its verification check on purpose. That's the receipt doing its job: a record that doesn't check out gets flagged, not smoothed over.

The tools

Bolt discovers these from the server at connect time:

ToolWhat it does
authorize_sourcesLists the sources your agent may search
searchFinds the records that answer a question
fetchRetrieves a record by address and re-verifies its seal
render_context_resultsRenders search results as context your agent can use

The starter library

Every Tier 1 account begins with the same starter library: the Northpine sample — 282 records across 9 documents, sealed at revision 6bf3c9cb1af2. It's small on purpose. Ask it the 23:41 question and watch the whole loop — search, fetch, verify — run on material you can check by hand.

Your own library

Build your library in your browser at tier-1-protocol-kfn8.bolt.host — your files are cut and sealed on your machine, and the door is what you pay for:

  • $19/month for door access, or
  • a 3-day free trial, no card, if you want to watch it work first.

The paywall is the door, not the app.

Notes

  • Connectors serve Bolt build sessions — that's where the agent calls the door. A published app that needs Tier 1 at runtime calls the same endpoint from its own code, like any external service.
  • The door asks you to sign in with your Tier 1 account (MCP OAuth). Your library is fenced to your account.
  • This repository is the setup sheet only. There is no product code in it.

© 2026 Tyler Brassel · Tier 1 Protocol · tier1protocol.network

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.