Skip to content

Curbi MCP server

io.github.Curbi-Inc/curbiCurbi-Incstreamable-httpv0.1.0Scanned

Check agent replies, lint policies, export regression tests and verify caller-trusted proof bundles.

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Curbi MCP server can do

The Curbi MCP server is published by the GitHub account Curbi-Inc. It has 6 tools. It can create or change data (3 tools: policy_check, export_regression and verify_bundle), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • export_regressionRun policy_check with caller-supplied records (no receipts or required-signature mode) and return it as a CI regression: curbi.regression JSON with each reply's expected verdict an…1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "export_regression" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run policy_check with caller-supplied records (no receipts or required-signature mode) and return it as a CI regression: curbi.regression JSON with each reply's expected verdict and rules, plus a dependency-free node:test file that replays it against the Check API. Expectations come from the checker, never from the caller. Nothing is stored. A pass grants no execution authority.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • policy_checkCheck one reply or up to 50 replies against explicit prices, forbidden phrases and supplied outcome records.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check one reply or up to 50 replies against explicit prices, forbidden phrases and supplied outcome records. Deterministic, no model calls. Caller records are unverified; receipt verification is unavailable here. A pass grants no execution authority.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • verify_bundleRun the open Curbi Proof verifier (curbi.proof/0.1) on a bundle with the public keys you choose: signatures, key windows, RFC 9162 inclusion under the signed log head, attestation …1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "verify_bundle" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run the open Curbi Proof verifier (curbi.proof/0.1) on a bundle with the public keys you choose: signatures, key windows, RFC 9162 inclusion under the signed log head, attestation binding and history consistency. Keys are required and are the trust anchor; keys inside the bundle are never trusted here. Test keys verify only with allowTest. Also accepts bounded TEST browser gate proofs with separately pinned request/trust and archival time. Pure computation: no network, nothing stored. A verified bundle shows what a trusted key signed and logged; it does not show that the provider action happened, and grants no authority.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • fetchFetch the first-party catalog summary for an id returned by search.No findings

    Why it is in this group

    • The name "fetch" says "fetch": a word for reading.
    Description, as the server wrote it
    Fetch the first-party catalog summary for an id returned by search. Returns a canonical URL and a link to full documentation; does not retrieve caller URLs.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • validate_policyCheck a policy against the same schema rules as policy_check, then lint it: no rules at all, duplicate or overlapping price items, duplicate forbid ids or phrases, prices that cann…No findings

    Why it is in this group

    • The name "validate_policy" says "validate": a word for reading.
    Description, as the server wrote it
    Check a policy against the same schema rules as policy_check, then lint it: no rules at all, duplicate or overlapping price items, duplicate forbid ids or phrases, prices that cannot be stated in cents, and rules the checker never fires on (probed with the shipped checker). Returns valid, errors and warnings. Nothing is stored. A valid policy is not a complete one, and grants no execution authority.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:22 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.curbi.io/mcp: tools/list returned 6 tools to an anonymous client, including policy_check (write), export_regression (write), verify_bundle (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "export_regression" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "verify_bundle" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http curbi https://api.curbi.io/mcp
claude mcp add --transport http curbi https://api.curbi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__curbi__validate_policy",
      "mcp__curbi__search",
      "mcp__curbi__fetch"
    ],
    "ask": [
      "mcp__curbi__policy_check",
      "mcp__curbi__export_regression",
      "mcp__curbi__verify_bundle"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as curbi. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Curbi-Inc/curbi/verify?hash=135a11c66d0750ab3e1445fd6a408c8e380e27349b84d169161d609d90c8bbef" | jq -e '.changed == false'

Pinned hash 135a11c66d07, from Nov 20, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.Curbi-Inc/curbi/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.Curbi-Inc/curbi
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Curbi-Inc/curbi.svg)](https://radar.anlyon.com/servers/io.github.Curbi-Inc/curbi)

Source: MCP Registry. Synced Nov 6, 2026, 01:17 UTC.

Curbi MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Curbi MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Curbi MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Curbi MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Curbi MCP server have?

6 tools: 3 write, 3 read. policy_check, export_regression, verify_bundle, validate_policy, search and fetch.

Does the Curbi MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Curbi MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Curbi MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.