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.

Barmaan

REMOTE · BARMAAN.CO

Barmaan catalogue: instruments, specs, guides, certificate check, quote requests

Available components

+3 this week 77 Trust /100

Last scanned (3 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category IoT and Hardware

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 Security80
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1054 tokens (~70/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

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

  • 25 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 “get_company_info” rewrote its description, which is the text the model reads security
    • New tool “get_brochure” functional
  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
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://barmaan.co/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=barmaan.co CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 df7a5233f7fe7d7c0e7cf8fde3298f00
SANs: barmaan.co, *.barmaan.co
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 barmaan.co. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
co. present 7786 8 Verified
barmaan.co. 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
strict-transport-security max-age=15552000
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://barmaan.co/api/mcp Verified 200
http (plaintext) http://barmaan.co/api/mcp HTTPS enforced 301 https://barmaan.co/api/mcp
MCP tools · 15 exposed · ~999 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
fetch ~50

Get the full text of one item by the id returned from `search` (product:, service:, project:, resource:<kind>/<slug>, category:, certificate:, company:info).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_brochure ~70

Barmaan's public brochure (PDF, no login): download links in English, Persian, Kurdish (Sorani) and Arabic, a short summary of the content, base prices and contact details.

NameTypeReqDescription
languagestring–en, fa, ckb or ar. Omit for all languages.

No output schema declared.

No examples provided.

get_company_info ~69

Barmaan contact and company facts: use for the phone number, address, email, WhatsApp, map link, working hours, social profiles, registration details, key site pages, city pages and brochure links.

NameTypeReqDescription
localestring–Content language: en, fa, ar or ckb.

No output schema declared.

No examples provided.

get_dwg_viewer_info ~38

Information about Barmaan's free browser DWG/DXF viewer. Files cannot be uploaded through MCP; give the user the link.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_product ~71

Full public details of one product: specs, models, documents, FAQ, price/availability. Pass `slug` or the 6-digit `code`.

NameTypeReqDescription
codestring––
localestring–Content language: en, fa, ar or ckb.
slugstring––

No output schema declared.

No examples provided.

get_resource ~63

Full text of one resource (kind + slug from list_resources). Text is capped at 20,000 characters.

NameTypeReqDescription
kindstringyes–
localestring–Content language: en, fa, ar or ckb.
slugstringyes–

No output schema declared.

No examples provided.

get_service ~44

Details of one service by slug (from list_services).

NameTypeReqDescription
localestring–Content language: en, fa, ar or ckb.
slugstringyes–

No output schema declared.

No examples provided.

list_categories ~32

Product categories with product counts.

NameTypeReqDescription
localestring–Content language: en, fa, ar or ckb.

No output schema declared.

No examples provided.

list_projects ~50

Published reference projects.

NameTypeReqDescription
categorystring––
limitinteger–Max rows (1-20).
localestring–Content language: en, fa, ar or ckb.

No output schema declared.

No examples provided.

list_resources ~66

Published technical guides, standards notes, datasheets and glossary entries.

NameTypeReqDescription
kindstring––
limitinteger–Max rows (1-20).
localestring–Content language: en, fa, ar or ckb.
querystring––

No output schema declared.

No examples provided.

list_services ~45

Barmaan's engineering, calibration, inspection and software services.

NameTypeReqDescription
localestring–Content language: en, fa, ar or ckb.
querystring––

No output schema declared.

No examples provided.

request_quote ~218

Send a price/quote request to Barmaan's sales team (same inbox as the website form). Ask the user for name and phone first; never invent contact details. Call once with confirm=false to get a preview, show it to the user, then call with confirm=true only after they agree.

NameTypeReqDescription
companystring––
confirmboolean–false = preview only, nothing is sent. Set true ONLY after the user has explicitly agreed to send these exact details to Barmaan.
emailstring–Customer email (optional).
localestring–Content language: en, fa, ar or ckb.
messagestringyesWhat the customer needs: product, quantity, specs, destination.
namestringyesCustomer full name, asked from the user (never guessed).
phonestringyesCustomer phone/WhatsApp with country code, asked from the user.
product_codestring–6-digit product code or product slug, if the request is about one product.

No output schema declared.

No examples provided.

search ~41

Search all public Barmaan content (products, categories, services, projects, guides, certificates). Returns ids to pass to `fetch`.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

search_products ~106

Search the Barmaan product catalog (industrial instruments). Prices are published USD prices; price.on_request=true means ask for a quote.

NameTypeReqDescription
brandstring––
categorystring–Category key from list_categories.
conditionstring––
in_stockboolean––
limitinteger–Max rows (1-20).
localestring–Content language: en, fa, ar or ckb.
querystring––

No output schema declared.

No examples provided.

verify_certificate ~36

Check a Barmaan calibration certificate by its exact code. Returns status, equipment, manufacturer and serial only.

NameTypeReqDescription
codestringyes–

No output schema declared.

No examples provided.

Install

How do I install the Barmaan MCP server?

Barmaan is a hosted endpoint at https://barmaan.co/api/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 · barmaan.co

# add to Claude Code
claude mcp add --transport http co-barmaan-barmaan 'https://barmaan.co/api/mcp'
Common questions

What is the Barmaan MCP server?

Barmaan is an MCP server listed in the public MCP registry as co.barmaan/barmaan. Barmaan catalogue: instruments, specs, guides, certificate check, quote requests. This page covers its hosted endpoint (https://barmaan.co/api/mcp).

Is the Barmaan MCP server safe to use?

Barmaan scores 77 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 Barmaan MCP server expose?

Barmaan exposes 15 tools: fetch, get_brochure, get_company_info, get_dwg_viewer_info, get_product, and 10 more. Their descriptions and schemas cost roughly 999 tokens of context every time the server is loaded.

Does the Barmaan MCP server require authentication?

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

Is the Barmaan MCP server still maintained?

Barmaan 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.