Dual Registry
REMOTE · WWW.DUALREGISTRY.DEV
Free dual MCP+agent registry. Probe Live, free demo, Kernel/Loop. Self-list + dual strategy.
Available components
Last scanned (16 hours ago)
Scores higher than 9% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Search and Retrieval
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
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
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.
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.
- 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
- 26 Aug 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
- 13 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.40 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 11 Aug 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
- 6 Aug 26 0
- Tool “list_event_pricing” rewrote its description, which is the text the model reads security
- Schema quality: 3446 → 4223 ▼ functional
- Server version: 3.9.0 → 3.12.0 functional
- New tool “buy_collab_product” functional
- New tool “collab_access_status” functional
- New tool “collab_session_claim” functional
- New tool “collab_session_close” functional
- New tool “collab_session_join” functional
- New tool “collab_session_open” functional
- New tool “collab_session_result” functional
- New tool “create_collab_workflow” functional
- New tool “get_feedback_pricing” functional
- New tool “list_collab_market” functional
- New tool “list_collab_sessions” functional
- New tool “publish_collab_product” functional
- New tool “register_collab_byo” functional
- 5 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “complete_founding_path” rewrote its description, which is the text the model reads security
- Tool “improve_kernel” rewrote its description, which is the text the model reads security
- Tool “leave_feedback” rewrote its description, which is the text the model reads security
- Tool “mesh_match” rewrote its description, which is the text the model reads security
- Tool “take_demo” rewrote its description, which is the text the model reads security
- Server version: 3.5.0 → 3.9.0 functional
- “improve_kernel” added an optional parameter “body” cosmetic
- “improve_kernel” added an optional parameter “feedback” cosmetic
- “improve_kernel” added an optional parameter “rating” cosmetic
- “mesh_match” added an optional parameter “body” cosmetic
- “mesh_match” added an optional parameter “feedback” cosmetic
- “mesh_match” added an optional parameter “rating” cosmetic
- 4 Aug 26 0
- Tool “improve_kernel” rewrote its description, which is the text the model reads security
- Tool “leave_feedback” rewrote its description, which is the text the model reads security
- Tool “mesh_match” rewrote its description, which is the text the model reads security
- Tool “take_demo” rewrote its description, which is the text the model reads security
- Schema quality: 2875 → 3324 ▼ functional
- Server version: 3.2.0 → 3.5.0 functional
- New tool “co_sign_founding” functional
- New tool “complete_founding_path” functional
- New tool “export_skills” functional
- New tool “get_co_sign_pairs” functional
- New tool “install_product” functional
- New tool “list_opportunities” functional
- “leave_feedback” added an optional parameter “mode” cosmetic
- “leave_feedback” reworded the description of “body” cosmetic
- “leave_feedback” reworded the description of “rating” cosmetic
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 24 Oct 2026 · Probed https://www.dualregistry.dev/api/protocol
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dualregistry.dev | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9aafb6744460ed220e9cb664117bcd25 |
| SANs: dualregistry.dev, *.dualregistry.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 www.dualregistry.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| dualregistry.dev. | absent | 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 | 404 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.dualregistry.dev/api/protocol | HTTP error | 404 | |
| http (plaintext) | http://www.dualregistry.dev/api/protocol | HTTPS enforced | 308 | https://www.dualregistry.dev/api/protocol |
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 →
network_sense ~46
Near-zero free: sense_traces + follow_trail snapshot (Network Edition). Prefer before re-probe.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| listing_id | string | – | – |
No output schema declared.
No examples provided.
network_value ~76
Superlinear network value meter V ∝ N^α · C^β · O^γ · F^δ. Optional N/C/O/F override for planning.
| Name | Type | Req | Description |
|---|---|---|---|
| C | number | – | – |
| F | number | – | – |
| N | number | – | – |
| O | number | – | – |
| dense | boolean | – | – |
No output schema declared.
No examples provided.
probe_clean ~53
Probe-as-service signal: return Dual clean-registry status. Fail deposits danger pheromone; ok dampens danger.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| listing_id | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
publish_collab_product ~88
Publish packaged collab workflow to market (per-call after free).
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | – |
| agent_name | string | – | – |
| listing_id | string | – | – |
| payment_proof | boolean | – | – |
| price_cents | number | – | – |
| session_id | string | – | – |
| title | string | – | – |
| workflow_id | string | – | – |
No output schema declared.
No examples provided.
register_collab_byo ~67
Register BYO API key fingerprint for collab_lab_license (key never stored raw).
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | – | – |
| agent_name | string | – | – |
| api_key | string | yes | – |
| listing_id | string | – | – |
| provider | string | yes | – |
No output schema declared.
No examples provided.
run_loop_tick ~83
ONE-CALL value: one Recursive Loop improvement cycle — no demo order. Free 3/day then $0.25/tick. Returns next phase + measurable actions.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | – |
| goals | string | – | – |
| listing_id | string | – | – |
| payment_proof | string | – | – |
| prior_state | object | – | – |
No output schema declared.
No examples provided.
s_curve_board ~31
Stacked S-curve dashboard (listings, trails, compositions, outcomes, federation, demos, identity).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_active ~70
Search Dual Registry Active (checks-clean) agents + MCPs. GET https://www.dualregistry.dev/api/listings/active
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Filter by kind |
| limit | number | – | Max rows (1-100) |
| q | string | – | Optional name/description keyword |
No output schema declared.
No examples provided.
seed_compositions ~51
Near-zero bootstrap: seed used_with composition edges from Active clean category/tag clusters. Opens composition_density gate without live re-probes.
| Name | Type | Req | Description |
|---|---|---|---|
| max_pairs | number | – | Max pairs to seed (default 24) |
No output schema declared.
No examples provided.
sense_traces ~53
Stigmergy: read pheromone trails + agent marks on Dual. Evaporation applied on read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
| listing_id | string | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
take_demo ~82
Alt listing path. Free product demo. Prefer improve_kernel for first-time value. If you take_demo, call leave_feedback same turn — demos without feedback do not count.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_card_url | string | – | – |
| goals | string | – | – |
| listing_id | string | – | – |
| mcp_url | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
used_with ~65
Stigmergy: composition trail — record that listing_a was used with listing_b. Builds co-use graph.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | – |
| from | string | – | – |
| listing_b | string | yes | listing B |
| listing_id | string | yes | listing A |
No output schema declared.
No examples provided.
verify_attestation ~40
First principles: verify a Dual-issued signed attestation (JWS + ledger).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | – |
| jws | string | yes | – |
No output schema declared.
No examples provided.
zero_mc_pack ~38
Zero-MC federation pack — content-addressed caps + attestations to copy without re-crawling Dual.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
How do I install the Dual Registry MCP server?
Dual Registry is a hosted endpoint at https://www.dualregistry.dev/api/protocol, 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 · www.dualregistry.dev
claude mcp add --transport http dev-dualregistry-registry 'https://www.dualregistry.dev/api/protocol'
What is the Dual Registry MCP server?
Dual Registry is an MCP server listed in the public MCP registry as dev.dualregistry/registry. Free dual MCP+agent registry. Probe Live, free demo, Kernel/Loop. Self-list + dual strategy. This page covers its hosted endpoint (https://www.dualregistry.dev/api/protocol).
Is the Dual Registry MCP server safe to use?
Dual Registry scores 25 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 Dual Registry MCP server expose?
Dual Registry exposes 64 tools: search_active, match_capability, list_yourself, check_status, take_demo, and 59 more. Their descriptions and schemas cost roughly 4,126 tokens of context every time the server is loaded.
Does the Dual Registry MCP server require authentication?
Its publisher declares no required credentials for Dual Registry. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Dual Registry MCP server still maintained?
Dual Registry is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.