ENDPOINT 1
https://apis.farm/mcp
MCP server metadata
- Name
- apis.farm
- Version
- 0.1.0
Known tools 6
listCollectionTraceabilityLot records (FSMA-204 KDE grain; EPCIS events referenced on the rail, never re-served here) — typed OK | EMPTY | BLOCKED, branching on status/gtin; every record is labeled example data
Inferred read-onlygetLotOne TraceabilityLot by id — 200 OK envelope; an unknown id answers 404 EMPTY.
Inferred read-onlylistProductsProduct records (GTIN-identified, GS1 demo prefix 952) — filterable by ftl and category; includes sandbox-registered products
Inferred read-onlylistFacilitiesFacility records (GLN-identified, GS1 demo prefix 952) — filterable by role
Inferred read-onlylistComplianceArtifactsComplianceArtifact records — FSMA-204 deliverables (traceability plan, sortable sheet) derived from the lot chain; filterable by kind and facilityGln
Inferred read-onlyregisterProductRegister a Product via the headless master-data door — sandbox writes are ephemeral (per-isolate memory), labeled, and demand a valid demo-prefix-952 GTIN
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.apis-farm]
url = "https://apis.farm/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"apis-farm": {
"type": "http",
"url": "https://apis.farm/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: apis-farm
Remote MCP URL: https://apis.farm/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"apis-farm": {
"url": "https://apis.farm/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"apis-farm": {
"type": "http",
"url": "https://apis.farm/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "apis-farm",
"transport": "streamable-http",
"url": "https://apis.farm/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.