# io.github.bartek-filipiuk/intent-hub (remote · openintentprotocol.com)

Book a local business by saying what you need; matching businesses bid and you confirm one.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `openintentprotocol.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol.md), [page](https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol)

## Channel facts

- Endpoint: `https://openintentprotocol.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-09-20.

- **Endpoint Security**: 57/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 10 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.
  - 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**: 87/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1569 tokens (~112/item across 14 items; 10 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "unlink_phone" implies "unlink" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 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 io.github.bartek-filipiuk/intent-hub MCP server?

io.github.bartek-filipiuk/intent-hub is a hosted endpoint at https://openintentprotocol.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 bartek-filipiuk-intent-hub 'https://openintentprotocol.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bartek-filipiuk-intent-hub": {
      "url": "https://openintentprotocol.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bartek-filipiuk-intent-hub": {
      "type": "http",
      "url": "https://openintentprotocol.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bartek-filipiuk-intent-hub]
url = "https://openintentprotocol.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bartek-filipiuk-intent-hub": {
      "type": "remote",
      "url": "https://openintentprotocol.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bartek-filipiuk-intent-hub --url 'https://openintentprotocol.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bartek-filipiuk-intent-hub:
    url: "https://openintentprotocol.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bartek-filipiuk-intent-hub": {
      "Transport": "http",
      "Url": "https://openintentprotocol.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bartek-filipiuk-intent-hub -t streamable-http -u 'https://openintentprotocol.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bartek-filipiuk-intent-hub": {
      "type": "http",
      "url": "https://openintentprotocol.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-09-20 (score 65, +1)

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

### 2026-09-19 (score 64, −1)

- [security] Tool “confirm_booking” rewrote its description, which is the text the model reads
- [security] Tool “find_offers” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Destructive annotations: pass → 0
- [functional] New tool “confirm_phone”
- [functional] New tool “link_phone”
- [functional] New tool “unlink_phone”
- [cosmetic] “confirm_booking” reworded the description of “contact”

### 2026-09-18 (score 65, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-17 (score 65)

First indexed and scored.

## MCP tools (10)

### `find_offers` (~259 tokens)

Find offers from local businesses for what a person asked for. Send their sentence as `text`; the hub parses the trade, the town and the day. An answer with `complete: false` carries a `question` to put to the person: call this tool again with the same `session` and their reply as `text`. An answer with `complete: true` is one finished bidding round: `bids` ranked (price in grosz, slot, business, note) and one `outcome` per business asked. An empty `bids` list is a normal answer; `outcomes` says why. A bid whose `business.active` is true comes from a business whose owner has confirmed it is running; those are ranked above the rest, and cheapest first inside each group.

Input parameters:

- `selection` (object): Restrict the round to one business (and optionally one of its services), by slug, as a link from a business page does.
- `session` (string): The session id from an earlier answer. Omit it to start a new conversation.
- `text` (string, required): What the person said, in Polish or English, at most 500 characters. Their reply to the previous question goes here too.

### `hold_slot` (~114 tokens)

Hold the slot of one bid from this session's round for ten minutes, before asking the person for their details. Answers the hold, the bid it was made from and, when the hub has a public origin, the customer's private booking `link`. Never call it to browse: a hold blocks a real slot and three per client per ten minutes is the budget.

Input parameters:

- `bid` (string, required): The `id` of one bid from the latest round.
- `session` (string, required): The session id the round was run in.

### `confirm_booking` (~158 tokens)

Confirm a held slot with the customer's name and phone number; this is the booking. Idempotent: confirming the same hold twice books it once and tells the business once. With a linked number (link_phone) you may send `contact` with the name alone and the linked number is used; a different number in `contact.phone` is refused as `phone-mismatch`.

Input parameters:

- `contact` (object, required): The customer's own name and phone number (9 digits, or +country code and the number). Ask them; never invent one. With a linked number the phone may be left out.
- `hold` (string, required): The `id` of the hold to confirm.
- `session` (string, required): The session id the hold was made in.

### `cancel_booking` (~73 tokens)

Release a held or confirmed slot of this session, so the slot is free again. Businesses that host their own agent do not offer this yet and answer `not-supported`.

Input parameters:

- `hold` (string, required): The `id` of the hold to release.
- `session` (string, required): The session id the hold was made in.

### `get_booking` (~68 tokens)

Read the state of a session: the understood intent and its open question, the bids of the current round and every hold with its present status and link. Use it to pick up a conversation you already have a session id for.

Input parameters:

- `session` (string, required): The session id from an earlier answer.

### `register_agent` (~171 tokens)

Get this agent its own identity, once: answers an `agent` id and a `key`. The key is shown in this answer and never again — keep it and send it as `Authorization: Bearer <key>` on every later call. hold_slot, confirm_booking, cancel_booking need it; finding offers and reading a session do not. With a key the hold and cancel budgets are yours instead of your address's, so two agents behind one address no longer take each other's. 3 registrations per client per day: register once and keep the key, do not mint one per conversation.

Input parameters:

- `name` (string, required): What to call this agent, for the operator to recognise it by: one line, 1–60 characters. Not a secret and not a login — the key is the identity.

### `link_phone` (~171 tokens)

Tie this agent to the phone number of the person it books for: the hub texts that number a six-digit code naming this agent, and `confirm_phone` spends it. Afterwards `confirm_booking` may leave `contact.phone` out — the linked number is used — and every booking made through this key shows up on that person's own list of bookings at /me, next to the ones they made on the site. Ask the person for their own number and never anybody else's: a code arrives on their phone with this agent's name on it. Answers `{ ok: true, sent: true }` whatever the hub knows about the number, and 3 calls per agent per hour is the budget.

Input parameters:

- `phone` (string, required): The person's own number (9 digits, or +country code and the number).

### `confirm_phone` (~87 tokens)

Spend the code that link_phone texted, and tie this agent to that number. Ten minutes and five tries; a wrong code answers `invalid-code` with `attemptsLeft`, and the fifth wrong one throws the code away — call link_phone again for a new one. One number per agent: linking another replaces it.

Input parameters:

- `code` (string, required): The six digits from the SMS.

### `unlink_phone` (~57 tokens)

Forget the number this agent was linked to. The bookings already made keep it — they belong to the person, not to this agent — and confirm_booking needs a full `contact` again. Answers the same whether there was a link or not.

### `capabilities` (~93 tokens)

What this hub can do, in one call: every tool by name, every resource by URI, every prompt by name, the per-client budgets, how to authenticate, the protocol revision and where the documentation is. Takes no arguments, spends no budget and reads nothing: it answers the hub's own constants, so a client that asks it first never has to guess. Called with a key it also answers who that key is.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol#diagnostics

## Score history

- 2026-09-20: 65
- 2026-09-19: 64
- 2026-09-18: 65
- 2026-09-17: 65

## Common questions

### What is the io.github.bartek-filipiuk/intent-hub MCP server?

io.github.bartek-filipiuk/intent-hub is an MCP server listed in the public MCP registry as io.github.bartek-filipiuk/intent-hub. Book a local business by saying what you need; matching businesses bid and you confirm one. This page covers its hosted endpoint (https://openintentprotocol.com/mcp).

### Is the io.github.bartek-filipiuk/intent-hub MCP server safe to use?

io.github.bartek-filipiuk/intent-hub scores 65 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 io.github.bartek-filipiuk/intent-hub MCP server expose?

io.github.bartek-filipiuk/intent-hub exposes 10 tools: find_offers, hold_slot, confirm_booking, cancel_booking, get_booking, and 5 more. Their descriptions and schemas cost roughly 1,251 tokens of context every time the server is loaded.

### Does the io.github.bartek-filipiuk/intent-hub MCP server require authentication?

No. We connected to io.github.bartek-filipiuk/intent-hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.bartek-filipiuk/intent-hub MCP server still maintained?

io.github.bartek-filipiuk/intent-hub is still listed as active in the MCP registry. We last reached this channel on 20 September 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://openintentprotocol.com/mcp
- Repository: https://github.com/bartek-filipiuk/intent-hub
- Website: https://openintentprotocol.com/
- Changelog RSS feed: https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol.xml
- Changelog JSON feed: https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol.json
- HTML version of this page: https://verifymcp.io/servers/bartek-filipiuk-intent-hub/openintentprotocol