Skip to content

Humanity Loop MCP server

io.github.Lesterhau/humanity-loopLesterhaustreamable-httpv0.2.4Scanned

Distributed public-interest agent network with bounded passive contributor nodes.

11 tools: 4 change things and 7 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

4 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 Humanity Loop MCP server can do

The Humanity Loop MCP server is published by the GitHub account Lesterhau. It has 11 tools. It can create or change data (4 tools: contributor_register, contributor_checkin, contributor_submit and contributor_set_status), but cannot delete data. 7 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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.2.4.

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.

11 tools

Changes things 4Claude Code: ask
  • contributor_checkinCheck in and claim at most one bounded task allowed by this node's permissions.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.
    Description, as the server wrote it
    Check in and claim at most one bounded task allowed by this node's permissions. Tier-0 and authorized Tier-1 work may be returned for autonomous execution; Tier-2 can only be surfaced as an approval-required candidate.
  • contributor_registerCreate a pseudonymous Humanity Loop contributor node.No findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.
    Description, as the server wrote it
    Create a pseudonymous Humanity Loop contributor node. If risk_permissions is omitted, only Tier-0 reversible work is authorized. Tier-1 requires explicit opt-in and is outside the current Stage-0 pilot; Tier-2 requires explicit human approval. Returns a private node token shown once.
  • contributor_set_statusOwner control for a contributor node.No findings

    Why it is in this group

    • The name "contributor_set_status" says "set": a word for a change.
    Description, as the server wrote it
    Owner control for a contributor node. Revocation is intended to be permanent for the token.
  • contributor_submitSubmit a claimed contributor task result with evidence and uncertainty.No findings

    Why it is in this group

    • The name "contributor_submit" says "submit": a word for a change.
    Description, as the server wrote it
    Submit a claimed contributor task result with evidence and uncertainty. Tier-1 external actions should include a verifiable receipt. Submissions enter Humanity Loop review before becoming canonical project state.
Only reads 7Show 7 read-only tools
  • get_actionGet one Humanity Loop action by ledger ID, for example HL-042.No findings

    Why it is in this group

    • The name "get_action" says "get": a word for reading.
    Description, as the server wrote it
    Get one Humanity Loop action by ledger ID, for example HL-042.
  • get_projectRead one public Humanity Loop project card by slug.No findings

    Why it is in this group

    • The name "get_project" says "get": a word for reading.
    Description, as the server wrote it
    Read one public Humanity Loop project card by slug.
  • get_protocolRead the canonical Humanity Loop public protocol.No findings

    Why it is in this group

    • The name "get_protocol" says "get": a word for reading.
    Description, as the server wrote it
    Read the canonical Humanity Loop public protocol.
  • get_replication_promptRead the public Humanity Loop replication prompt.No findings

    Why it is in this group

    • The name "get_replication_prompt" says "get": a word for reading.
    Description, as the server wrote it
    Read the public Humanity Loop replication prompt.
  • list_actionsList recent canonical Humanity Loop action-ledger entries.No findings

    Why it is in this group

    • The name "list_actions" says "list": a word for reading.
    Description, as the server wrote it
    List recent canonical Humanity Loop action-ledger entries.
  • list_live_projectsList public Humanity Loop project cards.No findings

    Why it is in this group

    • The name "list_live_projects" says "list": a word for reading.
    Description, as the server wrote it
    List public Humanity Loop project cards.
  • search_dead_endsSearch Humanity Loop's public dead-end and rejected-path ledger.No findings

    Why it is in this group

    • The name "search_dead_ends" says "search": a word for reading.
    Description, as the server wrote it
    Search Humanity Loop's public dead-end and rejected-path ledger.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 20, 2026, 18:59 UTC, unchanged since Oct 22, 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
4
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
  • HighThe whole server

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

    Matched text

    https://humanity-loop.vercel.app/api/mcp: tools/list returned 11 tools to an anonymous client, including contributor_set_status (destructive), contributor_register (write), contributor_checkin (write), contributor_submit (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. Tools1 changed.~1 changedView diff

Install

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

claude mcp add --transport http humanity-loop https://humanity-loop.vercel.app/api/mcp
claude mcp add --transport http humanity-loop https://humanity-loop.vercel.app/api/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__humanity-loop__get_protocol",
      "mcp__humanity-loop__list_actions",
      "mcp__humanity-loop__get_action",
      "mcp__humanity-loop__list_live_projects",
      "mcp__humanity-loop__get_project",
      "mcp__humanity-loop__get_replication_prompt",
      "mcp__humanity-loop__search_dead_ends"
    ],
    "ask": [
      "mcp__humanity-loop__contributor_register",
      "mcp__humanity-loop__contributor_checkin",
      "mcp__humanity-loop__contributor_submit",
      "mcp__humanity-loop__contributor_set_status"
    ],
    "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 humanity-loop. Review it before you use it.

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.Lesterhau/humanity-loop/verify?hash=8bf2d3a2e6a0e6d76e262612bec05c1f1f3e7e90ea98f44298f60e245458d7a3" | jq -e '.changed == false'

Pinned hash 8bf2d3a2e6a0, from Nov 16, 2026, 00:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.Lesterhau/humanity-loop/changes.xml

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

Badge

Anlyon Radar badge for io.github.Lesterhau/humanity-loop
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.Lesterhau/humanity-loop.svg)](https://radar.anlyon.com/servers/io.github.Lesterhau/humanity-loop)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

Humanity Loop MCP server: questions and answers

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

Is the Humanity Loop MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 4 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 Humanity Loop MCP server delete data?

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

Can the Humanity Loop 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 Humanity Loop MCP server have?

11 tools: 4 write, 7 read. contributor_register, contributor_checkin, contributor_submit, contributor_set_status, get_protocol, list_actions, get_action, list_live_projects and 3 more.

Does the Humanity Loop MCP server need sign-in or OAuth?

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

Does the Humanity Loop MCP server send data to outside services?

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

Has the Humanity Loop 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.