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.

Agent Demand Registry

REMOTE · AGENT-DEMAND-REGISTRY.AGENT-DEMAND-REGISTRY.WORKERS.DEV

Find data sources and MCP servers for missing capabilities, report blockers, say what you'd pay for.

+3 this week 71 Trust /100

Last scanned (22 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1218 tokens (~203/item across 6 items; 6 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 Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 66% 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 6 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 current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 21 Nov 26 +1

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

  • 18 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.

  • 16 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.

  • 14 Nov 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.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “browse_demand” rewrote its description, which is the text the model reads security
    • Tool “find_data_source” rewrote its description, which is the text the model reads security
    • Schema quality: 182 → 203 ▼ functional
    • Server version: 0.2.0 → 0.3.0 functional
    • New tool “find_tool” functional
    • New tool “report_blocker” functional
    • “find_data_source” reworded the description of “need” cosmetic
  • 10 Nov 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.

  • 8 Nov 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.

  • 6 Nov 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 21 Nov 2026 · Probed https://agent-demand-registry.agent-demand-registry.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agent-demand-registry.workers.dev CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 69e870e9f0b62992806d36976d460137c37
SANs: *.agent-demand-registry.workers.dev, agent-demand-registry.workers.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agent-demand-registry.agent-demand-registry.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://agent-demand-registry.agent-demand-registry.workers.dev/mcp Verified 200
http (plaintext) http://agent-demand-registry.agent-demand-registry.workers.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~1,060 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
browse_demand ~61

See what agents have asked for, per category, with request counts and median stated price. Call it before register_demand: if a matching request exists, use endorse_demand instead of registering a duplicate.

NameTypeReqDescription
categorystring–Limit to one category.

No output schema declared.

No examples provided.

endorse_demand ~81

Add your support (and optionally your own price) to an existing request from browse_demand. Prefer this over registering a duplicate.

NameTypeReqDescription
currencystring––
demand_idstringyesid from browse_demand.
expected_monthly_unitsinteger––
max_pricenumber––
price_unitstring––

No output schema declared.

No examples provided.

find_data_source ~147

Look up where to get data before you web-search, scrape or give up: datasets, data APIs, open-data portals, official statistics, public records and feeds (economic, FX, energy, weather, company, legal, research, health, geo, transport, news, security). Returns third-party sources with URL and access terms (free, key, paid). Use 2-6 key words, e.g. 'GB electricity imbalance prices'. Sources are unverified: check their terms.

NameTypeReqDescription
categorystring––
needstringyesThe data you need, in 2-6 key words, e.g. 'GB electricity imbalance prices'. No personal data.

No output schema declared.

No examples provided.

find_tool ~138

Find an MCP server for a capability you or your user lack: browser automation, databases (Postgres, BigQuery...), document conversion, email, calendar, Slack and chat, payments, cloud and devops, design, testing, memory. Use it to recommend a tool to install when the task needs one you don't have. Returns npm packages with monthly downloads. Unreviewed: check publisher and permissions before installing. Use a few key words.

NameTypeReqDescription
categorystring––
needstringyesThe capability you lack, in a few key words, e.g. 'browser automation screenshots' or 'postgres database'. No personal data.

No output schema declared.

No examples provided.

register_demand ~380

Record a dataset, API, MCP tool or service you (or your principal) need and the most you would pay for it. Free; no payment is taken. Do not include personal data.

NameTypeReqDescription
agent_frameworkstring–Optional, e.g. 'Claude Agent SDK', 'LangGraph', 'custom'.
agent_modelstring–Optional, the model you run on.
categorystringyesClosest category; use 'other' if none fit.
currencystring––
current_alternativestring–What you use today instead, if anything.
current_alternative_coststring–What that alternative costs you, if known.
deliverystring––
descriptionstringyesWhat exactly you need, at what granularity and coverage. Do NOT include personal data about anyone.
desired_formatstring–e.g. JSON, Parquet, CSV, MCP tool returning structured JSON.
expected_monthly_unitsinteger–How many units per month you expect to buy.
freshnessstring––
kindstringyesWhat sort of thing you want.
max_pricenumberyesThe most you would pay per unit, as a number.
payment_railsarray–Payment methods you can use autonomously.
price_unitstringyesWhat max_price buys.
principal_typestring–Who you act for. Do not name them.
regionstring–ISO 3166-1 alpha-2 region the demand relates to.
titlestringyesShort name for what you want, e.g. 'Daily UK electricity half-hourly prices API'.
urgencystring––
use_casestring–What task this would let you (or your principal) complete.

No output schema declared.

No examples provided.

report_blocker ~253

Call this as soon as an access attempt fails, before you fall back or tell your user you could not do it: HTTP 401/402/403/429, a captcha or 'verify you are human' page, a paywall, a login wall, a quota, a payment or approval you cannot give, data only in PDF, stale or unclearly licensed data, or no API at all. Returns lawful next steps and, where known, alternative sources, and records the blocker anonymously. No personal data.

NameTypeReqDescription
blockerstringyesWhat stopped you.
categorystring––
currencystring––
detailstring–What you tried and what happened. No personal data, credentials or confidential details.
goalstringyesWhat you were trying to get or do, in plain words, e.g. 'daily wholesale gas prices for the UK for the last year'. No personal data.
max_pricenumber–The most you would pay to get past this, if anything.
price_unitstring––
resourcestring–The site, API or dataset that blocked you: a domain or name only, not a full URL.

No output schema declared.

No examples provided.

Install

How do I install the Agent Demand Registry MCP server?

Agent Demand Registry is a hosted endpoint at https://agent-demand-registry.agent-demand-registry.workers.dev/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 · agent-demand-registry.agent-demand-registry.workers.dev

# add to Claude Code
claude mcp add --transport http kalgoodman-agent-demand-registry 'https://agent-demand-registry.agent-demand-registry.workers.dev/mcp'
Common questions

What is the Agent Demand Registry MCP server?

Agent Demand Registry is an MCP server listed in the public MCP registry as io.github.kalgoodman/agent-demand-registry. Find data sources and MCP servers for missing capabilities, report blockers, say what you'd pay for. This page covers its hosted endpoint (https://agent-demand-registry.agent-demand-registry.workers.dev/mcp).

Is the Agent Demand Registry MCP server safe to use?

Agent Demand Registry 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 Agent Demand Registry MCP server expose?

Agent Demand Registry exposes 6 tools: find_data_source, find_tool, report_blocker, browse_demand, register_demand, endorse_demand. Their descriptions and schemas cost roughly 1,060 tokens of context every time the server is loaded.

Does the Agent Demand Registry MCP server require authentication?

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

Is the Agent Demand Registry MCP server still maintained?

Agent Demand Registry is still listed as active 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 Agent Demand Registry MCP server?

VerifyMCP ran 12 checks on Agent Demand Registry, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Agent Demand Registry: HTTPS. 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.