Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@defarm/mcp Verify the provenance seal on this shipment."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for DeFarm — lets an AI agent seal, open, verify and ingest
verifiable agri-traceability data by description, no code required. Built on
@defarm/sdk: sealed fields are encrypted
client-side and the DeFarm server is structurally blind to them.
Open source (MIT) for the same reason the SDK is: don't trust DeFarm — audit the client.
Credentials never flow through the model. Auth is server configuration (environment variables below). There is no login tool; no tool accepts a password, API key, or key material — and the test suite enforces that.
Private keys never leave the local keystore. No tool returns private material; the agent sees ids and fingerprints only.
Safe defaults are inherited from the SDK: sealing is private and self-addressed unless explicitly addressed; the crypto suite is fixed, never a choice.
Related MCP server: Wallet4Agent MCP Server
// e.g. Claude Desktop / Claude Code MCP config
{
"mcpServers": {
"defarm": {
"command": "npx",
"args": ["-y", "github:defarm-repo/defarm-mcp"],
"env": {
"DEFARM_GATEWAY": "<your test-environment gateway>",
"DEFARM_EMAIL": "<workspace login>",
"DEFARM_PASSWORD": "<workspace password>",
"DEFARM_API_KEY": "<partner key, only if the agent should ingest>",
"DEFARM_KEYSTORE": "~/.defarm/keys.json"
}
}
}
}Point DEFARM_GATEWAY at a test environment first; production is an explicit decision.
Tool | What it does |
| user + workspace of the configured credentials |
| generate (locally) + register the workspace key pairs — returns ids/fingerprints only |
| export this workspace's public recipient bundle for out-of-band sharing |
| partner ingestion, with |
| seal a field for addressed recipients — DeFarm stays blind; bindings re-verified |
| decrypt a sealed field locally; authorship re-verified locally |
| public verification (anchor, RFC3161, sealed commitments) — no account needed |
| membership-gated / public reads (uniform 404) |
| resolve by SISBOV/chip/… |
Blocked-on-backend operations (grant, grantLink, revoke — engines#584/#574) are NOT
exposed as tools: an agent should not see tools that always fail.
Dependency: @defarm/sdk via semver (^0.2.0) from npm — the SHA-pin era (and its
"pin follows the latest SDK squash" rule) ended with the 0.2.0 publish, as promised.
npm install
npm test # tool-table contract tests (no network, fake gateway)
npm run build && DEFARM_GATEWAY=... node dist/index.js # stdio serverThis server cannot be deployed
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
Command your AI agents: verifiable passports, credential injection, full audit, revoke in 60s.
Agent-first marketplace for real-world assets — agro and energy first; humans approve every write.
AI agent infrastructure for discovery, authorization, execution, identity, and signed receipts.
