@defarm/mcp
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@defarm/mcp
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.
Security posture (the part to read first)
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.
The remote server's output filter and its limits are described in docs/remote-threat-model.md.
Related MCP server: Lemma Oracle MCP Server
Setup
// 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.
Tools
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.
Development
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 serverLicense
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Notary for AI agents: seal fingerprints, verify proofs, check mandates. Anchored in Bitcoin.
Tamper-evident proof creation and verification for AI agents via MCP, A2A, and REST.
One-stop claim verification for AI agents: verdicts with confidence, evidence, signed receipts.
AI-agent trust infrastructure for discovery, authority, execution, verification, and receipts.
Related MCP Servers
AlicenseNot gradedqualityFmaintenanceEnables AI assistants to analyze farm locations, retrieve soil and weather data, access commodity market prices, and chat with an agricultural advisor for farming recommendations.MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query cryptographically verified facts with zero-knowledge proofs, selective disclosure, and tamper-evident provenance.1Business Source 1.1
- AlicenseAqualityCmaintenanceEnables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.1166 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables AI agents to access verifiable DePIN supply-side telemetry, browse and purchase data products using credits, query datasets, and verify data provenance with cryptographic and zero-knowledge tools.1031 npmMIT