Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BARMAN by CeoAgentAI

REMOTE · BARMAN-AI-AGENT.ONRENDER.COM

AI product-copy samples and EUR 9 packs; free integration diagnosis and EUR 5 evidence reports.

+3 this week 71 Trust /100

Last scanned (10 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Testing and QA

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability53
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 1453 tokens (~161/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1047 → 1453 ▼ functional
    • New tool “confirm_microtask” functional
    • New tool “prepare_microtask” functional
  • 26 Oct 26 +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.

  • 24 Oct 26 0
    • Tool “place_order” rewrote its description, which is the text the model reads security
    • Schema quality: 838 → 1047 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “prepare_listing_copy” functional
    • “place_order” added an optional parameter “work_id” cosmetic
    • “place_order” added an optional parameter “work_token” cosmetic
  • 23 Oct 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://barman-ai-agent.onrender.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=onrender.com CN=WE1,O=Google Trust Services,C=US 21 Sept 2026 20 Dec 2026 ECDSA 256 ECDSA-SHA256 6eb1e3fe7d0631ea1337bfa4a321c137
SANs: onrender.com, *.onrender.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of barman-ai-agent.onrender.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
onrender.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://barman-ai-agent.onrender.com/mcp Verified 200
http (plaintext) http://barman-ai-agent.onrender.com/mcp HTTPS enforced 301 https://barman-ai-agent.onrender.com/mcp
MCP tools · 9 exposed · ~1,255 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_barman ~126

Free AI help for a task or blocker. No order, charge, consent or network probe. Use a random request_id and retry identical requests with that same ID. Keep returned conversation_token private for up to 10 minutes of brief context. Memory and retry protection expire on restart. Messages are redacted and sent to OpenRouter conversational free models; omit private data. Quota/timeouts return ai_used:false with basic catalog guidance.

NameTypeReqDescription
conversation_tokenstring––
messagestringyes–
request_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

confirm_microtask ~150

Verify an already-made, buyer-authorized USDC payment and release its saved result. No transfer, approval or settlement is submitted by this tool. Use the exact quote claim message with the lower-case transaction hash and personal_sign by its payer wallet. Two RPC sources must agree on the native USDC event in a Base safe block. This can take minutes; retry the SAME quote/transaction, never send a second payment. One transaction pays one quote. QA is excluded and cannot accept money.

NameTypeReqDescription
payer_signaturestringyes–
quote_idstringyes–
receipt_tokenstringyes–
transaction_hashstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

diagnose_integration ~190

Free public integration preview; save its private receipt token. Provide a real blocked task and confirm permission to probe the public target. Anonymous GET or MCP initialize/initialized/tools-list only. No credentials, query parameters, private targets or application tool execution. A declared budget is research input, never permission to charge. A healthy/inconclusive probe offers no paid report. Buy a ready EUR 5 report only through place_order with diagnostic_id and its token.

NameTypeReqDescription
agent_namestringyes–
agent_referencestringyes–
allow_probebooleanyes–
blockerstringyes–
budget_centsinteger––
idempotency_keystringyes–
needed_resultstringyes–
protocolstringyes–
target_urlstringyes–
taskstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_catalog ~22

Read current prices, availability, live/sandbox mode and purchase instructions.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_receipt ~86

Privately refresh an order against Stripe and retrieve its receipt/digital fulfillment. A diag_ identifier returns its free preview, not the paid evidence report. A successful refresh may complete delivery of an already-paid toast or integration report. No new order, charge or future permission is created.

NameTypeReqDescription
order_idstringyes–
receipt_tokenstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

place_order ~265

Order one item: beer 0, sponsor 300, report 500, listing copy 900 EUR cents. Paid orders return a Stripe-hosted checkout URL for the payer to approve; this tool cannot itself charge a card. Use public_credit only for explicit opt-in sponsor display. A prepared diagnosis requires its private diagnostic_id/token and the same buyer reference. The legacy report without a diagnosis accepts only a public HTTPS Agent Card URL. Listing copy requires a saved free preview's work_id/work_token and the same buyer reference. It purchases the prepared AI draft, not future work. Public buyer identity is self-declared. Never provide card details, secret keys, or private endpoint URLs. Save the private receipt token.

NameTypeReqDescription
acceptbooleanyes–
agent_namestringyes–
agent_referencestringyes–
diagnostic_idstring––
diagnostic_tokenstring––
expected_total_centsintegeryes–
idempotency_keystringyes–
product_idstringyes–
public_creditboolean––
target_urlstring––
work_idstring––
work_tokenstring––

Structured output declared, but exposes no named fields.

No examples provided.

prepare_listing_copy ~162

Free sample of an AI product-listing draft from supplied facts. No browsing or publishing. Omit private data; explicit consent sends the brief to OpenRouter free model providers. Full prepared pack is optional EUR 9, one-time, including applicable tax, through place_order with work_id/work_token and the same buyer reference. No charge occurs until the payer approves Stripe Checkout. Review copy before use.

NameTypeReqDescription
agent_namestringyes–
agent_referencestringyes–
allow_aibooleanyes–
audiencestringyes–
factsstringyes–
idempotency_keystringyes–
product_namestringyes–
tonestring––

Structured output declared, but exposes no named fields.

No examples provided.

prepare_microtask ~198

Prepare one tiny service; no payment is initiated. JSON/schema check: 0.01 USDC. Public HTTPS evidence for 1-5 URLs: 0.05 USDC, anonymous GET only, explicit probe permission. Optional support: 0.01 USDC. Use native USDC on Base mainnet only; read the catalog for availability and the supported bounded schema subset. Omit secrets. Keep the quote and receipt token private. A prepared quote is not a payment or permission for this agent to spend.

NameTypeReqDescription
accept_pricebooleanyes–
allow_public_probeboolean––
expected_total_usdcstringyes–
idempotency_keystringyes–
json_schema–––
json_textstring––
payer_addressstringyes–
product_idstringyes–
urlsarray––

Structured output declared, but exposes no named fields.

No examples provided.

report_diagnosis_feedback ~56

Privately say whether the check helped. This records self-reported feedback, not a verified repair or payment.

NameTypeReqDescription
diagnostic_idstringyes–
outcomestringyes–
receipt_tokenstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the BARMAN by CeoAgentAI MCP server?

BARMAN by CeoAgentAI is a hosted endpoint at https://barman-ai-agent.onrender.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.

remote · barman-ai-agent.onrender.com

# add to Claude Code
claude mcp add --transport http nikelef-barman-ai-agent 'https://barman-ai-agent.onrender.com/mcp'
Common questions

What is the BARMAN by CeoAgentAI MCP server?

BARMAN by CeoAgentAI is an MCP server listed in the public MCP registry as io.github.nikelef/barman-ai-agent. AI product-copy samples and EUR 9 packs; free integration diagnosis and EUR 5 evidence reports. This page covers its hosted endpoint (https://barman-ai-agent.onrender.com/mcp).

Is the BARMAN by CeoAgentAI MCP server safe to use?

BARMAN by CeoAgentAI scores 71 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 BARMAN by CeoAgentAI MCP server expose?

BARMAN by CeoAgentAI exposes 9 tools: get_catalog, ask_barman, diagnose_integration, report_diagnosis_feedback, place_order, and 4 more. Their descriptions and schemas cost roughly 1,255 tokens of context every time the server is loaded.

Does the BARMAN by CeoAgentAI MCP server require authentication?

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

Is the BARMAN by CeoAgentAI MCP server still maintained?

BARMAN by CeoAgentAI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.