Skip to content

Eco Funding MCP server

io.github.jdhart81/eco-fundingjdhart81streamable-httpv0.1.1Scanned

Ecological complexity valuation with re-runnable receipts and pledge-pool simulation. Read-only.

5 tools: 3 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 3 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Eco Funding MCP server can do

The Eco Funding MCP server is published by the GitHub account jdhart81. It has 5 tools. It can create or change data (3 tools: value_site, verify_receipt and simulate_pool), but cannot delete data. 2 tools only read.

2 tools bring in text other people can write (value_site and verify_receipt).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 3Claude Code: ask
  • simulate_poolSimulate a pledge pool (schema vef-pool/0.1) under milestone and outcome-linked release rules, given dated receipts or hypothetical readings per period.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Simulate a pledge pool (schema vef-pool/0.1) under milestone and outcome-linked release rules, given dated receipts or hypothetical readings per period. Integer accounting: releases + remaining = pledges; nothing released without a met rule. SIMULATION ONLY: no funds are held or moved; any real funding pool needs legal review before money moves.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Simulate pool
  • value_siteValue a site's ecological complexity (schema vef-site/0.1: D-Score components, habitat patches and links, optional GSIP soil indicators, optional NPP and temperature).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Value a site's ecological complexity (schema vef-site/0.1: D-Score components, habitat patches and links, optional GSIP soil indicators, optional NPP and temperature). Produces a sealed, reproducible receipt in which every quantity states its formula, units, inputs and uncertainty. bind_vergecommon=true reads the named VergeCommon public project (GET only) as provenance. Intelligence-bound quantities are labelled 'conjecture'. Not a price. Free rail.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Value site
  • verify_receiptRe-run a valuation receipt offline and check its input, result and seal digests; valid only if reproduced byte for byte.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Re-run a valuation receipt offline and check its input, result and seal digests; valid only if reproduced byte for byte. refetch_source=true also reads the bound VergeCommon public record (GET only). Shows reproducibility, not truth of inputs. Free rail.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Verify receipt
Only reads 2Show 2 read-only tools
  • describe_methodDescribe the method: formulas, constants, declared defaults, statuses, the seven invariants, citations and limits.No findings

    Why it is in this group

    • The name "describe_method" says "describe": a word for reading.
    Description, as the server wrote it
    Describe the method: formulas, constants, declared defaults, statuses, the seven invariants, citations and limits. Call first. Free rail.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Describe method
  • explain_valuationExplain a valuation step by step: each quantity's formula, inputs, value, units, uncertainty and status (published method, v0.1 convention, input, or conjecture), plus limits.No findings

    Why it is in this group

    • The name "explain_valuation" says "explain": a word for reading.
    Description, as the server wrote it
    Explain a valuation step by step: each quantity's formula, inputs, value, units, uncertainty and status (published method, v0.1 convention, input, or conjecture), plus limits. Accepts a valuation (receipt.result) or raw site inputs. Free rail.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Explain valuation

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:21 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.viridisconservation.com/eco-funding/mcp: tools/list returned 5 tools to an anonymous client, including value_site (write), verify_receipt (write), simulate_pool (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools4 changed.~4 changedView diff

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http eco-funding https://mcp.viridisconservation.com/eco-funding/mcp
claude mcp add --transport http eco-funding https://mcp.viridisconservation.com/eco-funding/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__eco-funding__explain_valuation",
      "mcp__eco-funding__describe_method"
    ],
    "ask": [
      "mcp__eco-funding__value_site",
      "mcp__eco-funding__verify_receipt",
      "mcp__eco-funding__simulate_pool"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as eco-funding. Review it before you use it.

Capability tags behind 2 rules
  • mcp__eco-funding__value_site untrusted-input
  • mcp__eco-funding__verify_receipt untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.jdhart81/eco-funding/verify?hash=d14fcdfd546083d28a167eee445aada1d89326e76b0f1777a08e2bb8231d7d14" | jq -e '.changed == false'

Pinned hash d14fcdfd5460, from Nov 16, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.jdhart81/eco-funding/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.jdhart81/eco-funding
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.jdhart81/eco-funding.svg)](https://radar.anlyon.com/servers/io.github.jdhart81/eco-funding)

Source: MCP Registry · repository. Synced Nov 16, 2026, 02:17 UTC.

Eco Funding MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Eco Funding MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Eco Funding MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Eco Funding MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Eco Funding MCP server have?

5 tools: 3 write, 2 read. value_site, verify_receipt, simulate_pool, explain_valuation and describe_method.

Does the Eco Funding MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Eco Funding MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Eco Funding MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.