adcp-client (adcontextprotocol/adcp-client) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 2 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
9 days ago

adcp-client

A Typescript SDK for the AdCP protocol (client and server)

→ adcontextprotocol/adcp-client· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

adcontextprotocol

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: ADCP_AUTH_TOKEN, ADCP_REGISTRY_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configADCP_AGENTS_MAP
configADCP_ALLOW_INTERNAL_PROBES
configADCP_ALLOW_V2
configADCP_AUTH_SCHEME
🔐 secretADCP_AUTH_TOKEN
configADCP_AUTH_TOKEN_CROSS_TENANT
configADCP_COMPLIANCE_DIR
configADCP_DEBUG
configADCP_DECISIONING_ALLOW_INMEMORY_STATE
configADCP_DEPLOYMENT_NAMESPACE
configADCP_GRADE_INITIALIZE_AUTHORIZATION
configADCP_IDEMPOTENCY_DISABLED_ACK
configADCP_INVOKED_VIA_SHIM
🔐 secretADCP_REGISTRY_API_KEY
configADCP_REPLAY_CAP
configADCP_WEBHOOK_TUNNEL
configADCP_WEBHOOK_TUNNEL_TIMEOUT_MS
configCOLUMNS
configGITHUB_STEP_SUMMARY
configMAX_CONCURRENT
configMOCK_ALLOW_CREATIVE_ID_OVERRIDE
configPRODUCT_CATALOG_JSON
configREQUEST_TIMEOUT
configTERM
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
deployPORT
// quality suggestions

Tool annotations

3/4 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

4/4 tools missing one or more hints — foo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_task_status (missing: destructiveHint, idempotentHint, openWorldHint); list_tasks (missing: destructiveHint, idempotentHint, openWorldHint), +1 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Secrets not logged

123 secret values sent to log/error

Redact or omit secret values from log output.

Dependency freshness

1/16 production deps stale: ajv-formats@2024-03-30 (2.4y)

Domain consistency

npm scope @adcp doesn't match GitHub owner adcontextprotocol

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/adcontextprotocol/adcp-client)](https://m8ven.ai/mcp/adcontextprotocol/adcp-client)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 105ba5901c4e766fa6fe81f5f8a2528f4c6b7491
code hash: 39009505c95f209615d3833ec69612e90891a494c8aeea11660dfbb1667d6540
verified: 9/3/2026, 7:09:29 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client