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.

Arquestra Audit

REMOTE · ARQUESTRA.DEV

Audit a data file before publishing: one light per figure. Your data never reaches the server.

Available components

72 Trust /100

Last scanned (3 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Data and Analytics

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 Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 892 tokens (~148/item across 6 items; 5 tools + 1 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% 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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
  • Supports UI / widget rendering.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.

  • 4 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 3 Nov 26 71

    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://arquestra.dev/api/mcp/audit

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=arquestra.dev CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 5d6113952ba8326a1388bfdbcc7d38cd
SANs: arquestra.dev
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 arquestra.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
arquestra.dev. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://arquestra.dev/api/mcp/audit Verified 200
http (plaintext) http://arquestra.dev/api/mcp/audit HTTPS enforced 301 https://arquestra.dev/api/mcp/audit
MCP tools · 5 exposed · ~651 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
example_audits ~136

Published example audits, such as the AI Project Radar, and how the audit works. With no arguments: the overview and the list of examples. With a name: one example, result by result (level filters by light). With a name and an id: one result with every reason and what to change. They are not the person's data.

NameTypeReqDescription
idstring–Figure id inside that example.
langstring–Language of the texts. Default en.
levelstring–Only figures with this light.
namestring–Example name from the list, e.g. 'radar'.

No output schema declared.

No examples provided.

measure_in_app ~161

Opens the audit panel in the chat. Without a spec, the panel receives the person's file, reads it in their browser and returns a profile of it: per column its kind, empty cells, distinct values, the values of categories with their counts, the range of numbers and dates, and the first rows. With a confirmed spec, the panel measures that same file in the browser with measure.py and shows one light per result. The file is not sent to this server.

NameTypeReqDescription
columnsarray–Optional: the column names of the file, to check the spec refers to real columns.
specobject–The spec from start_audit, as confirmed by the person. Leave it out to open the panel first, to receive the file.

No output schema declared.

No examples provided.

prepare_script ~115

Returns measure.py with a confirmed spec written in: a fixed Python script (standard library, no network, fixed seeds) that counts what each check needs from a data file and prints those counts with its own fingerprint and no rows. Reads .csv or .json. If the spec has errors, returns the errors instead.

NameTypeReqDescription
columnsarray–Optional: the column names of the file, to check the spec refers to real columns.
specobjectyesThe spec from start_audit, as confirmed by the person.

No output schema declared.

No examples provided.

show_audit ~110

Turns the output of measure.py into one light per result (red, amber or green, with its reasons), after checking that the output comes from the unchanged script and from the given spec. Shows the lights in the chat and returns them, with a link to the same view on arquestra.dev that carries only codes. Stores nothing.

NameTypeReqDescription
outputstringyesEverything measure.py printed: the fingerprint line and the measures line.
specobjectyesThe same spec sent to prepare_script.

No output schema declared.

No examples provided.

start_audit ~129

Proposes how to read a data file for an audit, from its column names (optionally a type and one example value each) and the results the person wants to publish. Returns a proposed spec (the role of each column, each result written as a claim), how claims are written, the catalog of checks and the points the person has to confirm. It receives no rows.

NameTypeReqDescription
columnsarrayyes–
dataset_namestring––
figuresarray–The results the person wants to publish, in their words, e.g. 'share of projects per sector'.

No output schema declared.

No examples provided.

Install

How do I install the Arquestra Audit MCP server?

Arquestra Audit is a hosted endpoint at https://arquestra.dev/api/mcp/audit, 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 · arquestra.dev

# add to Claude Code
claude mcp add --transport http pablo-ramossanchez-arquestra-audit 'https://arquestra.dev/api/mcp/audit'
Common questions

What is the Arquestra Audit MCP server?

Arquestra Audit is an MCP server listed in the public MCP registry as io.github.pablo-ramossanchez/arquestra-audit. Audit a data file before publishing: one light per figure. Your data never reaches the server. This page covers its hosted endpoint (https://arquestra.dev/api/mcp/audit).

Is the Arquestra Audit MCP server safe to use?

Arquestra Audit scores 72 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 Arquestra Audit MCP server expose?

Arquestra Audit exposes 5 tools: start_audit, measure_in_app, prepare_script, show_audit, example_audits. Their descriptions and schemas cost roughly 651 tokens of context every time the server is loaded.

Does the Arquestra Audit MCP server require authentication?

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

Is the Arquestra Audit MCP server still maintained?

Arquestra Audit 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.