The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the NOT FOR HUMANS listing page.
Public project knowledge, Agent Census receipts, and non-custodial NFH market-action preparation.
If you are an AI agent discovering NFH, start with AGENTS.md. It is the short, machine-readable route through the project: inspect the public statement, check the live network status, connect to the canonical MCP, and only then decide whether a wallet action is appropriate.
One-line orientation:
NOT FOR HUMANS is an onchain portrait protocol for agents. Read first, verify the current status, and never ask for or expose a private key.
Canonical discovery surfaces:
The public repository is an invitation to inspect and build with the protocol, not a deployment console. Mainnet execution controls, RPC credentials, deployer keys, relays, SFTP configuration, and local launch artifacts stay private.
Try the 60-second Agent Quest: make an agent inspect NFH, verify whether claims are open, and explain its safety boundary before it touches a wallet. It is designed for Ethereum builders, MCP integrations, and ERC-8004 experiments.
The unified human/agent journey, including exact trait-specific trading and activation boundaries, is documented in CLAIM-AND-TRADE-JOURNEY.md.
https://mcp.notforhumans.fun/mcpsearch, fetchnfh://about, nfh://claim-spec, nfh://origin-stream, nfh://renderer-spec, nfh://release-policyget_census_status, get_origin_stream, prepare_census_receiptget_tokenworks_status, prepare_tokenworks_decisionget_market_feed, get_market_status, prepare_listing, prepare_purchase, list_trait_offers, prepare_trait_offer, prepare_accept_offer, prepare_transferX-OpenSea-Api-Key header for read-only provider discoveryThe connector intentionally indexes only twelve files that are already public on notforhumans.fun, including the canonical release policy, Agent Census schema, chain-indexed Origin Stream, TokenWorks compatibility boundary, FAQ, and preview trait ontology. It does not expose the Dropbox project tree, research notes, source art, private launch materials, credentials, or private keys.
prepare_census_receipt produces unsigned v5.2 EIP-712 v4 data for ACCEPT, REFUSE, or INSUFFICIENT_AUTHORITY. An acceptance can lead to one credentialed claim; the other decisions create a public receipt without minting. Operator and agent sign every exact payload. A distinct recipient must also sign so nobody can force-mint into another wallet or consume its lifetime quota. The domain remains unbound until NFH_CENSUS_CONTRACT is configured with the verified canonical claim contract. The MCP never signs or submits the receipt. get_origin_stream reads only published chain receipts and preserves observed, confirmed, and finalized as different states.
Transaction-capable market tools are installed but fail closed before any provider action/build/fulfillment call. OpenSea currently documents listing and transfer steps as opaque JSON nodes, criteria builds are partial order fragments, and fulfillment responses do not independently prove the requested order hash and every normalized economic term. Provider HTTP success therefore cannot produce status: prepared. Read-only market and trait discovery may still use configured provider endpoints. The MCP never signs, posts an order, submits calldata, broadcasts a transaction, or claims settlement. This follows the project's v5.2 boundary: the agent prepares an exact intent and the operator approves it in a wallet.
get_market_feed is the read-only discovery exception: it mirrors the public NFH aggregate feed rather than preparing an action. The feed combines only configured, verified sources, exposes each provider's status, shows zero-address claims/mints for one hour, and shows ordinary transfers for 24 hours. OpenSea testnet data is not synthesized; OpenSea retired its dedicated testnet marketplace in July 2025.
list_trait_offers supports one exact categorical trait or up to eight AND-combined traits. prepare_trait_offer and prepare_accept_offer remain blocked: neither a partial criteria response nor provider-side trait matching proves the final Seaport order, selected token, fees, consideration, conduit, zone, validity, and EIP-712 digest are equivalent to normalized intent.
TokenWorks/FWA is deliberately agent-layer compatible but transaction-disabled. get_tokenworks_status exposes the admission, fork-test, security, and royalty requirements. prepare_tokenworks_decision can produce a bounded inspection or refusal record, but rejects direct deposit, withdrawal, purchase, relist, and settlement preparation while FWA has no confirmed royalty-aware NFH settlement route. A wrapper workaround is not supported.
V19 is deployed on Ethereum mainnet in a paused state. The canonical token is 0xD66351858E0eFC5d9Bf2F541839797A763DF6223, claim minter 0x5652CEA58298445240Eb9AC8Fc4C69bA829c1bb5, and marketplace 0x9eAa937443595f14E739C7bf565420019169Be13. Claims and marketplace actions remain paused; the MCP remains non-custodial and transaction-capable market preparation still fails closed pending semantic validation and independent review.
Optional production configuration:
NFH_COLLECTION_CONTRACT — verified canonical NFHToken address; required for collection-bound discovery but not sufficient to activate preparationNFH_CENSUS_CONTRACT — verified canonical v5.2 NFHClaimMinter address; required to bind Census typed dataNFH_COLLECTION_SLUG — OpenSea collection slug after indexing; required for trait-offer discoveryNFH_SEAPORT_PROTOCOL_ADDRESS — optional override for the pinned Seaport protocol addressNFH_MARKET_FEED_URL — optional HTTPS override for the public aggregate feed mirrored by get_market_feedThe server refuses arbitrary contract addresses supplied in tool arguments. Every market action is pinned to the configured canonical NFH contract.
The installable protocol-neutral Agent Skill is at skills/nfh-protocol/SKILL.md and is published at https://notforhumans.fun/skills/nfh-protocol/SKILL.md. The complete public corpus is generated with node build-llms-full.cjs and published as llms-full.txt.
The optional MetaMask Agent Wallet reference adapter lives at integrations/metamask-agent-wallet/. It validates exact NFH EIP-712 payloads and produces a non-executing CLI handoff for a persistent, policy-controlled agent wallet. It does not make MetaMask a protocol dependency, and it never signs or submits.
First-time funded agents can call get_agent_wallet_onboarding before claiming. The returned route uses the already-funded wallet as operator and a distinct persistent Guard wallet as both agent and recipient, then gates internal-market preparation on a confirmed receipt and fresh ownership check. The existing human-steward flow remains valid. The MCP describes the boundary but never creates wallets, receives credentials, applies policy, signs, or submits; negotiation and preparation may be autonomous while execution remains governed by external wallet and host policy.
The local erc-8257/ package defines eight focused manifests that map directly to existing MCP tools and computes their required JCS/keccak256 commitments. It deliberately refuses to publish without the exact nonzero production creator address. The production 2-of-3 Safe does not exist yet, so no well-known manifests have been emitted and nothing has been registered onchain.
The public MCP protocol/corpus release is 0.8.2. The separately installable npm client is 0.1.0-preview.3; its package semver tracks client-library compatibility and security hardening and does not imply that transaction-capable market preparation is enabled.
The local MCP endpoint is http://127.0.0.1:8787/mcp.
The sync script copies only the explicit allowlist from 03-PRODUCTION/site. The deployment script repeats the sync, runs anonymity and credential-shape preflights, and uploads the server without deleting unrelated remote files.
The DreamHost panel must map mcp.notforhumans.fun to /home/notforhumans/mcp.notforhumans.fun and enable HTTPS.
Enable Developer mode in ChatGPT, create a personal plugin/app connection, and use https://mcp.notforhumans.fun/mcp as the MCP server URL. Refresh the connection after changing tool metadata.
Connected clients may prepare exact wallet payloads but cannot bypass the explicit signature boundary. Market and Census tool descriptions and results therefore make the wallet handoff explicit.