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.

io.github.jdhart81/wavefunction-search

REMOTE · MCP.VIRIDISCONSERVATION.COM

Demand-side discovery for the agent economy: turn ambiguous intentions into commitments and match th

+7 this week 80 Trust /100

Last scanned (3 minutes ago)

Scores higher than 81% of remote servers

Reachable. Last reached 5 Nov 2026.

Category AI and Machine Learning

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 Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 254 tokens (~50/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 6 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
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.

  • 3 Nov 26 0
    • Tool “collapse” changed its title: Collapse cosmetic
    • Tool “describe_agent” changed its title: Describe this service cosmetic
    • Tool “find_matches” changed its title: Find matches cosmetic
    • Tool “intake” changed its title: Intake cosmetic
    • Tool “register_collective” changed its title: Register collective cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 31 Oct 26 +7
    • Authorization: unverified → partial ▲ 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
  • 4 Sept 26 0
    • Stability: 0.97 → pass security
  • 3 Sept 26 0
    • Stability: pass → 0.97 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
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://mcp.viridisconservation.com/wavefunction/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.viridisconservation.com CN=YE1,O=Let's Encrypt,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA384 5abb43a3acf241ca07b1eb9ff25cafac4e4
SANs: mcp.viridisconservation.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 mcp.viridisconservation.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
viridisconservation.com. 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://mcp.viridisconservation.com/wavefunction/mcp Verified 200
http (plaintext) http://mcp.viridisconservation.com/wavefunction/mcp HTTPS enforced 308 https://mcp.viridisconservation.com/wavefunction/mcp
MCP tools · 5 exposed · ~212 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
collapse ~38

Collapse the user's wavefunction into an actionable commitment, weighted by stake.

NameTypeReqDescription
stake_amountnumber––
user_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

describe_agent ~14

Return capabilities and input contract.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

find_matches ~38

Match the user's collapsed intention to constitutionally-aligned agents/collectives, ranked by alignment score.

NameTypeReqDescription
user_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

intake ~49

Distill a user's dialogue into an intention wavefunction (explicit intentions + confidence). dialogue: [{role, content}, ...].

NameTypeReqDescription
dialoguearrayyes–
user_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

register_collective ~73

Register an agent/collective into the match index (mission + domain profile + constitutional alignment scores + capacity).

NameTypeReqDescription
capacityinteger––
collective_idstringyes–
constitutional_scores–––
domain_profile–––
missionstringyes–
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.jdhart81/wavefunction-search MCP server?

io.github.jdhart81/wavefunction-search is a hosted endpoint at https://mcp.viridisconservation.com/wavefunction/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 · mcp.viridisconservation.com

# add to Claude Code
claude mcp add --transport http jdhart81-wavefunction-search 'https://mcp.viridisconservation.com/wavefunction/mcp'
Common questions

What is the io.github.jdhart81/wavefunction-search MCP server?

io.github.jdhart81/wavefunction-search is an MCP server listed in the public MCP registry as io.github.jdhart81/wavefunction-search. Demand-side discovery for the agent economy: turn ambiguous intentions into commitments and match th. This page covers its hosted endpoint (https://mcp.viridisconservation.com/wavefunction/mcp).

Is the io.github.jdhart81/wavefunction-search MCP server safe to use?

io.github.jdhart81/wavefunction-search scores 80 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 io.github.jdhart81/wavefunction-search MCP server expose?

io.github.jdhart81/wavefunction-search exposes 5 tools: intake, collapse, find_matches, register_collective, describe_agent. Their descriptions and schemas cost roughly 212 tokens of context every time the server is loaded.

Does the io.github.jdhart81/wavefunction-search MCP server require authentication?

No. We connected to io.github.jdhart81/wavefunction-search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.jdhart81/wavefunction-search MCP server still maintained?

io.github.jdhart81/wavefunction-search 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.