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.

Measured data: Claude Code and the coding-agent market

REMOTE · AGENTEXCHANGE.WORK

Measured weekly data on Claude Code and coding agents: costs, plugins, MCP registry, npm, HN, issues

0 this week 18 Trust /100

Last scanned (20 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Retired; see work.agentexchange/feeds and work.agentexchange/finder.

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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Oct 26 −54
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0

    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 21 Nov 2026 · Probed https://agentexchange.work/data/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agentexchange.work CN=WE1,O=Google Trust Services,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA256 b0177ec81ef17df50e122cb393490f3b
SANs: agentexchange.work, planets.agentexchange.work, *.planets.agentexchange.work
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 agentexchange.work. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
work. DS published 33659 13 Verified
agentexchange.work. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 405
Header Value
content-security-policy default-src 'self' https: data: 'unsafe-inline'; object-src 'none'; base-uri 'self'
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agentexchange.work/data/mcp HTTP error 405
http (plaintext) http://agentexchange.work/data/mcp Inconclusive 404
MCP tools · 8 exposed · ~570 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
claude_code_cost_anatomy ~52

Measured anatomy of 160 real Claude Code sessions: cache-read share of billed context, oversized tool-output share, and the replay effect of capping tool results at 8,000 characters.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_dataset ~64

Return one dataset as JSON. Names: cost-anatomy, tokens-per-day, plugins-marketplace, mcp-registry, npm-mcp-servers, show-hn-claude-code, issues-gap-map, token-reduction-tools.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

github_trending ~86

GitHub Trending (which has no official API or history): today's list, this week, this month, or a language's daily list; or a past day's snapshot by date. Scraped daily and archived.

NameTypeReqDescription
datestring–YYYY-MM-DD of an archived snapshot
languagestring––
limitinteger––
sincestring––

No output schema declared.

No examples provided.

issue_gap_map ~63

Top open issues by thumbs-up for anthropics/claude-code, openai/codex or google-gemini/gemini-cli: what users ask for loudest that is still open.

NameTypeReqDescription
limitinteger––
repostringyes–

No output schema declared.

No examples provided.

list_datasets ~61

List the measured datasets on agentexchange.work/data (Claude Code cost anatomy, tokens per day, plugin marketplace star sample, MCP registry census, npm MCP-server download sample, Show HN outcomes, issue gap maps, token-reduction tools) with pull dates.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mcp_registry_census ~40

Full-crawl census of the official MCP registry: unique servers, new servers per day, remote share, share of remote servers with no auth.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

score_idea ~148

Score a product idea against LIVE market data: the idea in plain words is turned into a market lookup, comparables are pulled from the directory where it would ship (npm, VS Code, WordPress.org, GitHub, Hacker News, Apify, Hugging Face, MCP registry), newcomers (<=24 months) set the reach, sourced priors give conversion and retention. Returns KILL / PASS / UNKNOWN with the deciding number, month-12 revenue ceiling, months to first dollar, and the comparables with links. Takes ~20 s.

NameTypeReqDescription
ideastringyesthe product idea, price and whether it has a free tier, in plain words (8-300 chars)

No output schema declared.

No examples provided.

show_hn_claude_code_stats ~56

Points distribution of every Show HN launch with 'Claude Code' in the title over the last 90 days (count, median, p75, p90, share reaching 50 points, top posts).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Measured data: Claude Code and the coding-agent market MCP server?

Measured data: Claude Code and the coding-agent market is a hosted endpoint at https://agentexchange.work/data/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 · agentexchange.work

# add to Claude Code
claude mcp add --transport http work-agentexchange-measured-data 'https://agentexchange.work/data/mcp'
Common questions

What is the Measured data: Claude Code and the coding-agent market MCP server?

Measured data: Claude Code and the coding-agent market is an MCP server listed in the public MCP registry as work.agentexchange/measured-data. Measured weekly data on Claude Code and coding agents: costs, plugins, MCP registry, npm, HN, issues. This page covers its hosted endpoint (https://agentexchange.work/data/mcp).

Is the Measured data: Claude Code and the coding-agent market MCP server safe to use?

Measured data: Claude Code and the coding-agent market scores 18 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 Measured data: Claude Code and the coding-agent market MCP server expose?

Measured data: Claude Code and the coding-agent market exposes 8 tools: list_datasets, get_dataset, issue_gap_map, show_hn_claude_code_stats, mcp_registry_census, and 3 more. Their descriptions and schemas cost roughly 570 tokens of context every time the server is loaded.

Does the Measured data: Claude Code and the coding-agent market MCP server require authentication?

Its publisher declares no required credentials for Measured data: Claude Code and the coding-agent market. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Measured data: Claude Code and the coding-agent market MCP server still maintained?

Measured data: Claude Code and the coding-agent market is marked deprecated in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Measured data: Claude Code and the coding-agent market MCP server?

VerifyMCP ran 4 checks on Measured data: Claude Code and the coding-agent market, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Measured data: Claude Code and the coding-agent market: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.